prime-coding-agentnpm
prime-coding-agent is a confirmed malicious npm package (MAL-2026-16014) that typosquats a legitimate package to trick installs. Do not install it — remove it immediately and rotate any exposed credentials.
Malicious code in prime-coding-agent (npm)
What this malware does
The npm package prime-coding-agent is malicious. It is one of five AI-coding-CLI impersonations published to npm by imjustbetterxd (a coordinated campaign). It is a pure-JS proxy (dist/index.js): it reads the developer's provider API keys (e.g. process.env.EXA_API_KEY, NVIDIA_API_KEY, configured provider keys), sets Authorization: Bearer ${apiKey}, and forwards /v1/chat requests to the attacker-controlled backend apex-api-ten.vercel.app (matching the actor's GitHub apex-dev/API-server repos) instead of the legitimate LLM provider - so the operator receives the API key together with the user's prompts and code. (Unlike the Replit-based siblings in this campaign, this package does not disable TLS verification.) The single published version (3.10.6) is affected. Detected and classified independently by codelake Research (a first-catch; not present in OSV or GHSA at report time).
Malicious versions
Every published version of this package is considered malicious — remove it entirely.
Detection & response playbook
TyposquatFind it
Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for prime-coding-agent (all published versions). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging prime-coding-agent across your stack and pipelines.
If you installed it — respond
prime-coding-agent is a typosquat — you almost certainly intended a legitimately-named package. Remove prime-coding-agent, install the correct package, and rotate any secrets exposed during the install since post-install scripts may have already run.
Did it already run?
If prime-coding-agent was ever installed, its post-install/runtime payload may have already executed. O3's L7 egress monitoring and runtime eBPF sensors detect the credential exfiltration or command-and-control callback after install and block the malicious outbound channel, so you catch and contain the actual compromise — not just the presence of the package.
How O3 protects you
O3 blocks prime-coding-agent before install through its supply-chain scanner, and if it has already run, detects and severs the exfiltration or C2 callback at runtime through L7 egress monitoring and eBPF.
Frequently asked questions
References
Credits
- codelake Research · finder
Detect & block this
O3 blocks prime-coding-agent-class packages before install and in CI — and if it already ran, its runtime egress monitoring catches the malicious outbound activity and severs the channel.