The only scanner that goes this deep. Bundles, insiders, fresh wallets, cross-funding. 7 chains. Check before you ape. by @dexbuilds https://xitter.cf/t.co/WLqf48uLGH

London, England
Joined February 2026
We've spent the past year building DeFade, shipping new features and improving it every single day. We did it for one reason: to make the trencher safe. Today it's the first scanner with all these modules in one scan. Nobody else puts this much in one place, and nobody else goes this deep. We were also the first to detect Proxima and Sumo, the launch-bundling tools behind a lot of the coordinated launches that get people farmed. When a wallet ran one of them on a token, DeFade names the tool right next to the wallet. One scan shows you the bundles, including delayed sweeps and the real peak exposure. It shows the snipers and sybil bands, meaning wallets funded by the same hand. It traces funding origin across multiple hops, so a rotated wallet still gets caught, and it catches wallets running the same bot config through their fee fingerprints. It pulls the dev wallet and deployer history, so you know if this person has rugged before. And it flags the fresh and virgin wallets farming the chart. It runs on Solana, ETH, Base, BSC, Robinhood, Arc, HyperEVM and more to come, on the web, in a Chrome extension, on mobile and in a Telegram bot. We also built MCP connectors, so you can plug DeFade straight into Claude or ChatGPT and run a full scan from inside the conversation. Ask your AI about a contract and get the real answer, backed by the same scan. And yes, we're launching a token. We waited on purpose. Most projects launch a token first and build something around it later. We did it the other way around: a year of building, a working product people already use, and only now the token. It never made sense to us to ask for your trust before there was something to trust. We're in the trenches too, and we were tired of watching people get rugged by wallets that were obvious in hindsight. Rugs keep evolving, so we keep shipping. Paste a contract. Get the truth. Defade.org
11
3
4
29
3,789
Great response. This is how you handle a security incident. Some others should take notes 👏
Official Statement | Security Incident Update TL;DR: No private keys were compromised, unaffected wallets are safe, and all affected users will be fully reimbursed by Bloom. Following our investigation, we have identified the exact attack vector and confirmed the scope of the incident. The attack exploited a third-party module through a complex Remote Code Execution (RCE) vulnerability. No private keys were accessed or compromised, and we have ruled out broader exposure of users' wallets. Incident Overview Affected: 49 wallet addresses belonging to 9 users. • Total losses: Approximately 9,408 SOL ($947,000). • Root cause: Exploited third-party module enabling an RCE vulnerability. • Refunds: Bloom will fully reimburse 100% of the stolen funds directly to secure wallets designated by the affected users. • We are also working to trace the stolen funds, explore recovery and freezing options, and identify the attacker. Our team has been developing software since 2018 and operating in crypto since 2021. We are an established team, committed to building for the long term and protecting the trust of our users. Security threats are an unfortunate reality of this industry, even with extensive precautions in place. Our commitment to user safety, transparency, and business continuity remains unchanged. The Bloom Team
6
474
DeFade saved people from aping into $carti - playboicarti H5UCZUqCsuTQijwNLBX2KjwP7XJaMaESBSDzQytypump The wallet that launched $carti had never launched a coin before. But DeFade traced its funding wallet and uncovered 8 previous launches. All the history was there. Same hands. Same playbook. Different coin. DeFade flagged $carti at 96% EXTREME RISK before it rugged. The deployer might be new. The money behind them isn’t. Always scan before you ape.
9
846
DeFade retweeted
$Kimchi and @Pumpfun getting ready for a second extraction
1
1
8
358
Scanned it with DeFade and a few other scanners. It came back clean on all of them except DeFade.
$PUMPKINBOT - Pumpkin Bot 
5QREAgtfP1NkuymRaFdHxr5QNF2Yry9M1YCyaompump Scanned with @DeFade_ 13 bundles across 67 wallets bought 84.5% and dumped it all for 669 SOL. Bundled now 24.69%. 95.1 SOL of the exit got recycled into fresh wallets. 99 fresh wallets hold 20.8%, 89 of 99 are bundle linked, 86 under 24h I scanned this with a few other scanners, and it came back clean.
2
2
11
777
DeFade retweeted
$PUMPKINBOT - Pumpkin Bot 
5QREAgtfP1NkuymRaFdHxr5QNF2Yry9M1YCyaompump Scanned with @DeFade_ 13 bundles across 67 wallets bought 84.5% and dumped it all for 669 SOL. Bundled now 24.69%. 95.1 SOL of the exit got recycled into fresh wallets. 99 fresh wallets hold 20.8%, 89 of 99 are bundle linked, 86 under 24h I scanned this with a few other scanners, and it came back clean.
2
1
1
5
722
Same hands, 7 earlier launches. 4 of them went -90%. Their usual run: top out around $413K about an hour in, then -93%. The deployer has 294 launches and only 3 ever reached a market. This one is on day 4 at $6.9M. That's 16x their usual peak. So who's still in it: - The bundles: 0% left. - 23 snipers bought at a $109K mcap. They're sitting at 63x and still holding. - $413K of liquidity under all of it. We ran a $500 buy through the pool. If the snipers sell first, it comes back as $319. That's -36%. The largest buy that still gets out within 10% if they do: none. The bundles are gone. The snipers aren't. Ape it or DeFade it? defade.org
2
1
11
697
“KOL is in” means nothing. Bought or received? DeFade tells you.
2
13
708
$CATTLEAXE H7VZNCBynDK5ikBS9krDJ2Tx8CUr1wxedV19ZgkWpump
9
703
solana:3SVjZ7BfT9FxiR49nZc7UdBmLgzRLJY7XBZDKhEFpump 3SVjZ7BfT9FxiR49nZc7UdBmLgzRLJY7XBZDKhEFpump
1
11
758
We keep building what no other scanner has ever done. Exit Playbook Same hands, same script. We replay the earlier launches by this dev and their crew: where they topped, how fast, and how many went -90% after. Then we show you exactly where this one sits on that chart. Insider Profit Pressure What the bundles and snipers actually paid vs the market cap right now. Their multiple, and what they walk away with if they dump this second. When they're sitting on 20x, you know who's selling. Position Stress Test Punch in your bag size. See what you'd actually get out with if the dev, the bundles or the snipers dump first. Plus the biggest size you can ape and still get out within 10% if the top holder sells first. Crew Radar on Telegram Ruggers don't get a fresh start. As soon as hands we've seen before launch again (a creator or funder with rugs on record, an operator band, a serial launcher) you get pinged. Solana: @Pumpfun @bonkfun @JupiterExchange EVM: @fourdotmemezh @flapdotsh @clanker_world @zora @ponsdotfamily @peachlfg @circlewarp across BSC, Base, Ethereum, Robinhood and Arc Every alert: chain, launchpad, full CA, and where that crew usually tops. Hit /top <address> and we ping you as it nears their usual peak, and again at the minute they usually topped. Also live: all three tools on the DeFade API (30 endpoints) and the Exit Playbook line right on the Chrome extension badge. Stop being their exit liquidity. defade.org
1
3
17
881
We showed what DeFade checks on a bundle. Here's what runs on top of it. Cross-funding graph We map the funding of the top 100 holders, whenever they bought, and group them into bands that trace back to shared private funders. When more than 50 of the top 100 sit in those bands, that alone is scored critical. That's one operator's wallets, however the supply is split, even if none of them bought at launch. Bundler memory Every wallet caught bundling is remembered. When it shows up on a new launch, it's flagged, and flagged harder when half or more of its earlier launches rugged. Deployer funder memory A fresh dev wallet doesn't wipe the slate. If its funder launched tokens that rugged, the new dev carries that history. Launch tool fingerprint The card names the launch or bundling tool behind a token, and flags wallets seen in other launches made with the same tool. Disguised handoffs On EVM chains, supply sold and bought back in the same transaction is caught as a transfer dressed up as trading. No inflated numbers Bot pairs with the same gas price to the wei and arbitrage traffic are shown but never counted as a bundle. A busy block isn't a bundle. Most scanners stop at who bought first. We follow who funded them, what they did before, and where the supply went. Paste any token: defade.org
11
754
"Bundled" is one word on a scanner. Behind it, DeFade runs a dozen separate checks on every Solana and EVM token. Most bundle checks stop at the launch block: who bought in it, and what they hold now. That misses the bundles that wait, the ones funded two hops back, and the supply moved to fresh wallets so it looks sold. DeFade checks all three. Who counts as a bundle - One transaction delivering to 2+ wallets - One wallet paying for buys that land in 3+ others - Same-slot buys that tipped Jito - Buyers sharing a funder, traced up to 2 hops back (exchange hot wallets never count) - One launch buy sprayed across fresh wallets - 4+ wallets created within 24h of launch - Identical buy sizes within seconds - Matching exchange withdrawals in the same half hour - Wallets already caught bundling other launches If the dev paid for the bundle, the card says so. When we look Bundlers know scanners check the first minutes, so many wait. We check three windows: the launch, the first 24 hours (bursts and buy ladders), and late cohorts found by walking back from today's holders. What they can still dump on you Buying is half the story. We also track: - What the bundle wallets still hold - Supply moved to other wallets and never sold - Exits with no visible sale - Sale proceeds recycled into fresh wallets that bought back in Moving tokens isn't closing a position. Red flags in how it was built - Wallets funded in the same minute - Wallets prepared days before launch - Buys on a steady bot clock - Throwaway relay wallets - Wallets seen in other launches from the same launch tool How it's rated A bundle that has mostly left is rated lower than one still sitting on supply. Every bundle figure on DeFade comes from one source, so the verdict, the rug score and the card never disagree. No other scanner goes this deep. Paste any token: defade.org
1
14
1,398
Just a reminder that @coldtrz and @nexocooker are scammers. $MOON was launched with Proxima, and DeFade flagged it at launch.
unavailable
2
3
12
1,160
We launched infrastructure. 
API since February. 60 builders. 7 chains. Build rug-check bots, trading bots, AI agents and wallet trackers on DeFade.
1
9
685
We've been here a while.
1M+ rug operators wallets. 7 chains. Every rug in our database. Over 63K Proxima and Sumo wallets. Every dev. Their entire history. If a dev spins up a fresh wallet, we trace who’s behind it, who funded it, and what that funder launched before. No other scanner has our database. No other scanner covers 30+ launchpads. And we built all of this before anyone else. They can copy @DeFade_ they can’t compete.
10
686
$PRIVACY 2ZTZPzwUH2fFBVy6rDSidVtq6hXVeZPZmxUSLqd7pump Privacy coin but the bundles aren’t private.
3
1
14
1,056
🥱🥱🥱
It’s nice to see so many scanners taking inspiration from DeFade. We saw a gap in the memecoin space and built what traders were missing: one place with all the intel they need. Now everyone wants to recreate what we built. Taking inspiration is easy. Being DeFade is a different story. 🥱
3
1
10
863
$KIMCHI $MOON $LAPTOP all flagged at launch, all in the DeFade rug database. Which one got you? DeFade’s got your back.
6
1
14
1,257
DeFade retweeted
4,760 commits so you don’t buy the rug. defade.org
1
5
184