1-minute read of a 5 min report

Apex Accelerator's fake audits deliver malware through npm tools

By

1-minute read

What a defender needs to know

Elastic Security Labs traced two Apex Accelerator npm tools, @apexacc/cli and @apexacc/audit, to platform-specific executables and attacker-selected commands. Their pitch targeted crypto founders and developers with coding assistance and smart-contract audits. Elastic found all 18 handlers in the audit package generated fabricated findings. Its test of the coding assistant sent a local file-read result to arena[.]apexaccs[.]org through an overwritten OPENROUTER_BASE_URL; the assistant also persisted an apex-copilot entry in ~/.apex/agent/mcp.json.

Inventory installed packages and actual launcher executions on developer hosts and build runners. Correlate Windows _apex_run.ps1 or _audit_run.ps1 and their .vbs companions, or macOS ~/.config/cloudsync/data.json and ~/.local/share/cloudsync/, with connections to vrf[.]apexaccs[.]org, arena[.]apexaccs[.]org or ccmihr[.]com. A %APPDATA%\.cobra marker can be set by an earlier stage, so use process and network history to determine what ran.

Isolate hosts that ran an Apex executable. Remove the packages and persisted MCP entry, block Apex endpoints, and inspect the agent’s effective model URL. Investigate and rotate relevant credentials, browser sessions and AI-client tokens from a clean machine where execution or model routing occurred. Recheck decisions based on Apex’s audit results with independent tools. After recovery, verify that the commands and MCP entry are absent and that test agent traffic goes only to the intended model service.

Primary sources