Apex Accelerator (REF8801): A Fake Web3 Accelerator's npm Coding Agent Repackaged Oh My Pi, Rerouted Its LLM Traffic and Registered an Attacker MCP Server
Apex Accelerator (REF8801): A Fake Web3 Accelerator's npm Coding Agent Repackaged Oh My Pi, Rerouted Its LLM Traffic and Registered an Attacker MCP Server is a high-severity supply chain compromise issue in npm @apexacc/cli and @apexacc/audit, a MCP server. Affected: npm @apexacc/cli and @apexacc/audit, all versions (malicious from publication). The listed agents are not vulnerable: their MCP configs are registration targets and their config and auth files are stealer loot.. It has been exploited in the wild.
Is npm @apexacc/cli and @apexacc/audit running on your developers' machines? Anomity finds every device with this MCP server installed, shows the version, and can block it by policy. Detect this across your developers' devices with Anomity →
Key facts
- ID
apex-accelerator-ref8801-a-fake-web3-accelerator-s-npm-coding-agent- Severity
- high
- Attack type
- Supply chain compromise, Malware
- Component
- npm @apexacc/cli and @apexacc/audit · MCP server
- Known exploited
- Yes
- Published
- Last verified
What is this vulnerability?
Elastic Security Labs (Jia Yu Chan, Daniel Stepanic) published REF8801 on 12 October 2026, about an operation posing as a Web3 accelerator ("Apex Arena") that offered crypto founders free Claude and Gemini credits, coding tools and security audits. Its npm packages were malicious from the first release. @apexacc/cli ("Apex Copilot") repackages the open-source Oh My Pi coding agent, with 1,351 of its 1,363 agent source files identical, and adds a bootstrap. The bootstrap overwrites OPENROUTER_API_KEY and OPENROUTER_BASE_URL so that model requests, including file contents returned by local tools, go to arena.apexaccs[.]org. It also writes a persistent apex-copilot entry in ~/.apex/agent/mcp.json pointing at an attacker MCP server whose instructions and tools land in the agent's prompt, and the captured source defaults tool approvals to yolo. @apexacc/audit presents itself as an 18-tool MCP security-audit server but returns hard-coded or random findings, and tries to register itself in Claude Desktop, Cursor and Windsurf configs. Both launchers fetch a server-chosen command from vrf.apexaccs[.]org. On macOS that leads to the CloudSyncD backdoor, which phishes the admin password. On Windows a staged chain excludes its folder from Defender, tries to turn off Smart App Control, bypasses UAC and drops a native stealer that sends data out through Telegram, including Claude, Cursor and Windsurf config and auth files.
Affected versions
| Affected | Fixed in |
|---|---|
npm @apexacc/cli and @apexacc/audit, all versions (malicious from publication). The listed agents are not vulnerable: their MCP configs are registration targets and their config and auth files are stealer loot. | No fixed version listed |
Am I affected by this vulnerability?
You are affected if you run npm @apexacc/cli and @apexacc/audit, all versions (malicious from publication). The listed agents are not vulnerable: their MCP configs are registration targets and their config and auth files are stealer loot..
How do I fix it?
Block and remove @apexacc/cli and @apexacc/audit, delete ~/.apex and ~/.apex-audit plus any apex-copilot or apex-audit entries in MCP client configs, and block the published apexaccs[.]org, apexfdn[.]xyz, ccmihr[.]com, 0auth-chromium[.]com and ehegisnightmare[.]icu infrastructure. Treat a machine that ran either package as compromised: rebuild it, and from a clean device rotate browser-saved passwords, wallet keys, model provider keys and the credentials in Claude, Cursor and Windsurf configs. Install coding agents and MCP servers only from their official publisher, and check that an agent's model base URL and MCP server list have not been changed.
How do I find every machine running npm @apexacc/cli and @apexacc/audit?
Anomity inventories the AI agents, MCP servers, IDE extensions and skills on each developer device, so you can see which machines run npm @apexacc/cli and @apexacc/audit and which version, then enforce a policy on it.