Which versions of prime-coding-agent are malicious?

Every published version of prime-coding-agent on npm is considered malicious. Remove the package entirely.

How do I remediate prime-coding-agent if I installed it?

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.

I already installed prime-coding-agent — how do I know if it already compromised me?

If prime-coding-agent was installed, its post-install payload may already have run. Removing the package does not undo that — check outbound connections and credential use from the install window onward.

How do I find prime-coding-agent across my projects, lockfiles, and CI pipelines?

Search your lockfiles and build artifacts for prime-coding-agent (all published versions).

Malicious package

prime-coding-agentnpm

Advisory published Sep 4, 2026Updated Sep 11, 2026

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)

MAL-2026-16014

Immediate action

Remove the package, then rotate any secrets the build/runtime could reach.

npm uninstall prime-coding-agent

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.

Malicious versions

all versions

Every published version of this package is considered malicious — remove it entirely.

Detection & response playbook

Typosquat

Find it
Search your lockfiles and build artifacts for prime-coding-agent (all published versions).
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 installed, its post-install payload may already have run. Removing the package does not undo that — check outbound connections and credential use from the install window onward.

Frequently asked questions

No. prime-coding-agent on npm has been identified as a malicious package (all published versions flagged). It should be removed immediately — do not install or keep it in your dependency tree.

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.

Malware detection Runtime egress monitoring

Explore

All malware advisories How O3 detects malware Vulnerability database