Clawdbot Becomes Moltbot: Trademark Rename and Impersonation

A trademark complaint, not a lawsuit

Clawdbot was Peter Steinberger's open source personal agent, released two months earlier, with a mascot named Clawd and a name derived from Claude. Anthropic asked the project to move away from that name over trademark concerns, and on January 27, 2026 the project announced a full switch: Clawdbot became Moltbot, and the mascot Clawd became Molty. [1]

The project framed the change with a biology metaphor rather than resistance, writing that lobsters molt to grow and so does good software, and summarizing the switch in the post's own words: "Same lobster soul, new shell." The rename covered the product name, the mascot, the X handle, now at moltbot, and the website, now at molt.bot. The team described no change to the underlying product, tooling, or goals, only to the branding and the handles that carried the old name. [1]

Atlas interpretation: A rename triggered by a request rather than a design decision or a court filing is a reminder of how far a trademark holder's reach extends into a nickname built to echo a brand. Clawd sitting one letter off Claude was apparently close enough for Anthropic to ask, and the available reporting describes only a request, not litigation. [1]

The freed handles did not stay empty

Renaming a fast growing open source project means abandoning its old identifiers. During the changeover, the Clawdbot GitHub organization and its X handle were briefly released before the team could reclaim them, and the gap was enough for opportunists to move in. [2]

Within that window, someone registered a cluster of typosquat domains, including moltbot.you, clawbot.ai and clawdbot.you, and cloned the project's GitHub repository as github.com/gstarwd/clawbot. The clone reused the real repository's schema.org metadata to falsely attribute itself to Steinberger and displayed the original project's star count, more than 61,500 at the time, as if it were its own. [2]

The impersonating site was built to pass casual inspection: a professional design, canonical tags, and Open Graph metadata, all pointed at the unauthorized repository rather than the real one. [2]

Clean code today, a plan for later

Malwarebytes found no malware in the cloned repository's code itself. Its assessment was that the clone's purpose was reputational: get a look alike project trusted and installed, with real API keys and messaging credentials attached, before shipping anything harmful. [2]

Atlas interpretation: That is the setup for a supply chain attack, not the attack itself. Clawdbot's product connects to a user's Anthropic or OpenAI keys and their WhatsApp, Telegram, or Discord accounts to carry out tasks, which is exactly the credential set a poisoned update to a trusted looking clone could later try to harvest. Malwarebytes stated the incentive directly: clean code today lowers suspicion tomorrow. [2]