Clawdbot: How a 10‑Second Mistake Turned Into a $16M Rug Pull

The Clawdbot story is a near‑perfect case study in how brand hijacking, AI hype, and classic DeFi fraud combined into a 16‑million‑dollar disaster. [incrypted]

1. The Setup: A Viral AI Agent Becomes a Target

Clawdbot (later renamed Moltbot) was an open‑source AI agent that ran locally, with deep system access and integrations into apps like WhatsApp and Telegram. [finance.yahoo] It went viral among developers, gaining tens of thousands of followers and massive visibility on GitHub and X (Twitter). [youtube]

Then came a trademark conflict: Anthropic argued “Clawdbot/Clawd” was too close to “Claude” and pressured the project to rebrand, pushing the creator, Peter Steinberger, to change the name to Moltbot. [linkedin]

To rebrand on GitHub and X, he had to release the old handle (@clawdbot) before claiming the new one—creating a critical, exploitable gap. [linkedin]

2. The 10‑Second Window: Identity Hijacked

In the seconds between releasing the @clawdbot handle and trying to secure the new identity, automated scripts were already watching. [linkedin]

• Bots instantly grabbed the freed @clawdbot accounts on GitHub and X. [astrix]
• These accounts still had the original project’s followers and credibility—tens of thousands of people who believed they were following the real Clawdbot. [astrix]

This wasn’t a deep technical hack; it was opportunistic “handle sniping” at machine speed, exploiting platform design and rebrand timing. [astrix]

3. The Scam: Fake $CLAWD Token to $16M and Back to Zero

With the hijacked accounts in hand, scammers immediately launched a fake Solana token called $CLAWD, presenting it as the “official” Clawdbot/Moltbot token. [clawdhost]

• They used the stolen @clawdbot profiles to announce a token launch and framed it as the natural next step for the viral AI project. [incrypted]
• Followers and meme‑coin traders rushed in, assuming the token was endorsed by the real founder. [incrypted]
• Within hours, $CLAWD’s market cap surged to around $16 million as speculation and FOMO kicked in. [clawdhost]

Once the price peaked, the scammers executed their exit:

• They dumped their holdings / drained liquidity in a short window, causing the token to crash by about 90% and wiping out late buyers. [unaaldia.hispasec]
• On‑chain watchers and scam‑tracking accounts flagged it as a “huge rug.” [unaaldia.hispasec]

Peter Steinberger then publicly clarified that he had no connection to any token and would “never do a coin,” but by then thousands of traders had already been hit. [bitrue]

4. What Type of Scam Was This?

At its core, this was a fake‑project rug pull with heavy brand‑impersonation:

• Rug pull: The scammers launched a token, pumped it using stolen reputational assets (the @clawdbot accounts), then rapidly exited, collapsing the price and walking away with funds. [finance.yahoo]
• Not an “official” project failure: The legitimate Clawdbot/Moltbot project never created a token; the entire crypto side was an unauthorized impostor piggy‑backing on the brand. [cyberunit]
• Pump‑and‑dump mechanics: Hype, rapid speculative inflows, a sharp top, then a brutal dump fit the classic pump‑and‑dump pattern embedded inside a rug pull. [youtube]

There’s no strong evidence that $CLAWD itself was a technical honeypot (i.e., blocking all sells); the losses mainly came from a liquidity exit and price collapse, not from code that prevented selling. [youtube]

5. Why It Happened: The Deeper Causes

Several structural and human factors made the Clawdbot scam possible:

• Handle‑release design on platforms: GitHub and X do not provide a protected “grace period” when a high‑value handle is released during a rebrand, letting bots snipe identities in seconds. [linkedin]
• Pre‑positioned scammers and scripts: Attackers monitored valuable accounts and were ready with automation to instantly claim any released identity and push pre‑packaged scams. [linkedin]
• Hype and trust: Clawdbot’s virality meant users were primed to believe in a token launch, and they trusted the brand enough not to question legitimacy before buying. [youtube]
• Speed‑over‑verification culture: Traders rushed in to avoid “missing the next big AI token,” prioritizing early entry over basic due diligence such as confirming the token with the founder or official channels. [bitrue]

In short, this wasn’t just a coding exploit; it was an ecosystem failure: platform design, rebrand process, trader behavior, and scam tooling all aligned in the attackers’ favor. [linkedin]

6. How to Spot (and Avoid) the Next Clawdbot‑Style Scam

Here’s how to recognize similar setups before your money is exposed:

A. Verify the Project’s Relationship to the Token

• Check official statements: search the founder’s personal accounts, GitHub repo, and official website for explicit confirmation of any token launch; in Clawdbot’s case, the founder repeatedly said he would never launch a coin. [bitrue]
• Be suspicious if the only promotion comes from a single handle that has just been renamed or looks freshly created.

B. Look for Identity Hijacking and Brand Mismatch

• Watch out for rebrands and handle changes: a sudden shift from “tool / open‑source project” to “token launch” via the same name can signal that the handle, not the project, controls the narrative. [astrix]
• Compare timestamps: if the token launch appears immediately after an account rename or controversy, treat it as high‑risk and assume impersonation is possible. [youtube]

C. Analyze the Token and Trading Pattern

• Sudden launch, instant hype: meme‑like tokens that jump to multi‑million market caps within hours, purely on social hype, are classic rug‑pull candidates. [finance.yahoo]
• Short‑lived liquidity: tokens whose liquidity and volume spike and then evaporate shortly after launch often signal a pre‑planned exit. [unaaldia.hispasec]

You can cross‑check with on‑chain or scanner tools (rug‑check platforms, contract analyzers) to see who holds liquidity and whether there are suspicious privileges. [snyk]

D. Check Team Identity and Consistency

• Confirm the dev’s stance: if the purported founder is denying involvement while a token is pumping in their name, assume the token is fake—there is no “maybe.” [incrypted]
• Look for credible, consistent communication: real teams issue coordinated announcements across multiple owned channels; scammers usually control only one or two hijacked fronts.

E. Slow Down and Use Test Size

• Pause before committing size: in Clawdbot’s case, the entire $16M run‑up and crash happened in a very short window; simply waiting 24–48 hours and observing would have saved most victims. [finance.yahoo]
• If you still want exposure, start with very small amounts and be ready to walk away if anything—liquidity, messaging, contract details—looks off.

7. The Takeaway

The Clawdbot scam wasn’t a bug in the AI project; it was a rug pull built on stolen identity and narrative arbitrage. Scammers weaponized a rebrand window, hijacked trust at machine speed, and used a fake token to vacuum $16M from traders chasing AI‑themed gains. [linkedin]

Spotting the next one means paying more attention to who is speaking, how they got that megaphone, and whether the real builders behind a project have ever endorsed any token at all.