Every rug pull detection tool on the market — Rugrat, ChainAware, Token Sniffer, Needle — focuses on-chain. They scan smart contracts, check liquidity locks, analyze bytecode. And they're useful. But they all miss the earliest signal: what the dev does on Twitter/X before they pull the rug.
In the 24-48 hours before a rug pull, dev accounts frequently change their Twitter/X profile. They remove their bio, change their display name, delete their avatar, unfollow their own project accounts, or unpin their launch tweet. These are human signals — panic moves that happen before the on-chain rug.
No existing tool monitors for this. Until now.
The 5 Twitter/X Rug Pull Warning Signs
Based on patterns observed across hundreds of Solana and EVM rug pulls, these are the most reliable Twitter/X signals:
1. Bio Cleared or Changed
The dev's bio goes from "Building the future of DeFi | @ProjectName" to blank, or changes to something unrelated. This is often the first move — they're distancing themselves from the project before dumping.
Detection
Xanguard's Profile Watch detects bio changes in under 500 milliseconds. You get an alert showing the old bio and new bio side by side.
2. Avatar Removed or Changed
The dev's profile picture changes from a branded project image to a default avatar or something generic. A clear sign they're abandoning the project identity.
3. Display Name Changed
The display name changes from "ProjectName Dev" to a random name or blank. Often combined with bio and avatar changes in rapid succession.
4. Pinned Tweet Unpinned
The pinned tweet — usually the launch announcement or CA — gets unpinned or replaced with something unrelated. If the dev no longer wants their token visible on their profile, something is wrong.
5. Unfollows Project Accounts
The dev unfollows the project's other accounts, team members, or partner projects. When someone starts cutting ties, it's a signal.
Why On-Chain Detection Misses This
On-chain rug pull detectors analyze smart contracts and liquidity. They catch:
- Unlocked liquidity pools
- Malicious contract functions (hidden mint, pausable transfers)
- Suspicious token distribution
- Sudden large sells from dev wallets
But by the time these on-chain signals appear, the rug is usually in progress. The Twitter/X signals happen hours or days earlier — when the dev is still planning the exit.
| Signal Type | When It Appears | Tools That Detect It |
|---|---|---|
| Twitter/X bio cleared | 24-48 hours before rug | Xanguard Profile Watch |
| Twitter/X avatar removed | 12-24 hours before rug | Xanguard Profile Watch |
| Dev unfollows project accounts | 12-48 hours before rug | Xanguard Follow Tracker |
| Pinned tweet removed | 6-24 hours before rug | Xanguard Profile Watch |
| Liquidity removed on-chain | During the rug | Rugrat, ChainAware, Token Sniffer |
| Large dev wallet sell | During the rug | Whale alert tools |
How to Set Up Rug Pull Detection with Xanguard
For Telegram Users
- Open @Xanguard_bot
- Add the dev accounts you want to monitor:
/add @dev_handle - Enable Profile Watch in settings
- You'll get instant alerts for any bio, name, avatar, or pinned tweet changes
For Developers (API / Trading Bots)
Connect to Xanguard's B2B Realtime WebSocket to receive profile change events programmatically:
// Listen for profile changes that signal a rug pull
ws.onmessage = (event) => {
const msg = JSON.parse(event.data);
if (msg.op === 0 && msg.d.event === 'twitter.profile.update') {
const { handle } = msg.d.task_info;
const { field, prev, updated } = msg.d.data;
// Check for rug pull patterns
if (field === 'description' && updated === '') {
alert(WARNING: @${handle} cleared their bio!);
}
if (field === 'avatar' && updated === '') {
alert(WARNING: @${handle} removed their avatar!);
}
if (field === 'name' && prev !== updated) {
alert(WARNING: @${handle} changed name: ${prev} → ${updated});
}
}
};
Combine with Follow Detection
For maximum coverage, also monitor follow/unfollow events:
// Dev unfollowed project-related accounts
if (msg.d.event === 'twitter.following.removed') {
alert(`WARNING: @${handle} unfollowed @${msg.d.data.handle}`);
}The Xanguard Advantage for Rug Pull Detection
- Profile changes detected in under 500ms — faster than any on-chain scanner
- Follow/unfollow detection in 30-60 seconds — know when devs cut ties
- Community monitoring in 3-5 seconds — detect when devs leave their own community
- 4 signal types combined: bio + avatar + name + pinned tweet + follows + community membership
- Automated via API — build rug pull detection into your trading bot
Existing Rug Pull Tools (Complementary)
Xanguard is not a replacement for on-chain rug pull detectors — it's a complement. Use both layers for maximum protection:
| Tool | What It Checks | When It Catches Rugs |
|---|---|---|
| Xanguard | Twitter/X profile, follows, communities | Hours to days before |
| Rugrat | EVM bytecode analysis | At deploy time |
| ChainAware.ai | AI contract risk scoring | At deploy time |
| Token Sniffer | Contract audit + social score | After launch |
| Needle.app | Multi-source risk scanning | After launch |
Pricing
- Profile Watch (Telegram): Included in Tweet Alert plans from $19/mo
- Follow Detection (Telegram): Included in Community Watch from $100/mo
- B2B API (all modules): From $49/mo via @B2B_Xanguard_bot
Get Started
- @Xanguard_bot — Tweet alerts + profile change detection
- @F_xanguard_bot — Community Watch + follow detection
- @B2B_Xanguard_bot — Full API access to all modules
- docs.xanguard.tech — API documentation