Blender MCP maintainer loses repo to account takeover

An attacker compromised Siddharth Ahuja's GitHub account on August 9, stripping his ownership of Blender MCP and Ableton MCP, Ahuja said.

Blender MCP carries 25,000 stars, Ableton MCP has 2,600. Both install straight from GitHub, so every user who trusted the repo inherited the attacker's access the moment ownership flipped.

GitHub suspended the account during a review, and the attacker kept pushing commits in that window, per Ahuja's account. Two CVEs now track the incident, CVE-2026-10661 and CVE-2026-10662.

Ahuja's fix for other maintainers: pin MCP servers to commit SHAs, not branches. A branch reference lets whoever controls the repo push new code that every downstream install picks up automatically. A SHA pin freezes the exact commit a user installed, so a hijacked branch can't silently swap in malicious code.

The incident is sourced only to Ahuja's own posts, with no independent word yet from GitHub or outside researchers on how the account was breached.

MCP's install model trusts whoever controls the repo at fetch time, not who wrote the code. A 25,000-star project didn't stop this from happening to Blender MCP, and nothing about branch-based installs stops it from happening to the next popular server, until SHA pinning becomes the default install instruction instead of an afterthought.