At 10:32 p.m. on August 9 (Korea time), Siddharth Ahuja (@sidahuj), creator of the open-source project Blender MCP, which has more than 25,000 stars, posted an urgent message on X: "My GitHub account was hacked and all my ownership was stripped. I lost my personal projects, including Blender MCP (25K stars) and Ableton MCP (2.6K stars). Anyone at GitHub who can help?" The post had 630,000 views and 1,700 likes at the time we checked, and spread quickly through the AI developer community. This article focuses on how far Ahuja's own account can be cross-verified using GitHub's public data.
Look at the GitHub Record, Not the Talk
Ahuja's X post alone can't tell us whether this is a hack or an ownership dispute. So we queried GitHub's public API and repository pages directly. The result technically confirms that the blender-mcp and ableton-mcp repositories, which were originally under his account (github.com/ahujasid), have indeed been transferred to a different owner. Both repository URLs permanently redirect (301) to an organization called "MCPBlender," and that organization was created on August 8, 2026, one day before Ahuja's report post. Yet the redirected repository pages (MCPBlender/blender-mcp, MCPBlender/ableton-mcp) return "Not Found (404)" at the time we checked, so access from outside is blocked.
| Item checked | Details | How checked |
|---|---|---|
| Original repository owner | github.com/ahujasid (blender-mcp, ableton-mcp) | GitHub profile |
| Current redirect target | github.com/MCPBlender/blender-mcp, /ableton-mcp | Direct lookup of GitHub repository URLs |
| MCPBlender organization creation date | 2026-08-08 (one day before the report) | Organization profile |
| Star count at transfer | blender-mcp 25,701 / ableton-mcp 2,895 | GitHub organization repository list |
| Currently accessible? | Individual repository pages return 404 (presumed switched to private or access restricted) | Direct lookup |
In short, the fact that the repositories left the original owner's account and moved to an unfamiliar organization can be reconfirmed by a third party through GitHub's own systems. However, the "MCPBlender" organization's profile lists the blog address Ahuja himself ran (blendermcp.org) and his X handle (@sidahuj) as-is, so it's hard to say from public information whether an attacker simply reused his identity details to boost credibility or whether there's another explanation. We can also confirm through searches that Ahuja contacted GitHub support and was asked for a ticket number, but we found no evidence that GitHub has issued an official statement or completed a restoration as of the time we checked. So it's most accurate to treat it as unresolved.
Why Are Blender MCP and Ableton MCP Famous?
Blender MCP is an open-source bridge that connects the 3D modeling tool Blender to Anthropic's Model Context Protocol (MCP), letting AI agents like Claude create and modify 3D scenes from natural-language prompts alone. In early 2025, Ahuja drew attention with a demo video making a "low-poly dragon guarding treasure" scene in a few sentences, and it has since been cited in many developer community posts as a leading example of "the evolution of AI-powered Blender modeling." Ableton MCP likewise connects the music production tool Ableton Live to AI agents so that track creation, clip editing, and composition are handled by prompts. The two projects are even listed in MCP server registries like PulseMCP, counted as early reference projects that effectively pioneered the trend of "connecting creative tools to AI through MCP." Apart from the star counts (about 25,000 for Blender and about 2,600 for Ableton), the many follow-on forks and derivative projects (such as unreal-blender-mcp and blender-mcp-vxai) that took these two repositories as their model show their influence in the community.
What Gets Risky When Ownership Is Shaken
An MCP server typically serves as the "hands and feet" with which an AI agent runs code. In fact, blender-mcp has an execute_blender_code feature that runs Python code generated by an LLM as-is through the exec() function, with no separate validation or sandbox, which is already documented in a GitHub issue, a security advisory (CVE-2026-10661), and CVE-2026-10662. In a structure like this, if someone can take over a repository's ownership wholesale, they can swap in code while wearing the label users trust: "a verified 25,000-star project." Users often run pip install or git clone based only on star counts and commit history, and the problem is that "who maintains this code," the basis of that trust, has changed while the outward appearance stays the same. In the open-source MCP ecosystem, then, an ownership takeover isn't just account theft. It can become a supply chain attack path for injecting malicious code into automation pipelines that already have broad execution privileges. This incident exposes that numbers the community has treated as trust indicators, such as stars, forks, and downloads, can't guarantee "who is writing this code right now."
Why Did the Repositories Change Hands?
This account is reconstructed, as of the time we checked (2026-08-10), from Ahuja's own statements and GitHub's public data, and we found no separate reporting by major security outlets such as TechCrunch, BleepingComputer, or The Hacker News. So the following can't be settled from public information: (1) whether this is pure account takeover (phishing, credential leaks, and so on) or a dispute over an organization-to-organization ownership transfer process; (2) who currently controls the MCPBlender organization; and (3) why the repositories show 404 to outsiders right now (an action by GitHub, or the attacker switching them to private). We also couldn't confirm whether GitHub has returned the account and repositories to the original owner. Based on search results, it's most accurate to treat it as unresolved. When citing or sharing this story, it's necessary to be precise: not "confirmed as a hack," but "he claimed a hack, and the fact of the repository transfer itself is reconfirmed by GitHub data."