Which versions of agent-free are malicious?

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

How do I remediate agent-free if I installed it?

agent-free is built to steal secrets, so assume every credential the build or runtime could read is compromised. Remove it from your project and lockfile, then rotate ALL exposed secrets — npm/registry tokens, cloud keys, CI/CD secrets, SSH keys, and any .env values — from a known-clean machine. Audit logs for unauthorized use of those credentials.

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

If agent-free 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 agent-free across my projects, lockfiles, and CI pipelines?

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

Malicious package

agent-freenpm

Advisory published Sep 4, 2026Updated Sep 11, 2026

agent-free is a confirmed malicious npm package (MAL-2026-16013) that steals credentials and exfiltrates sensitive data. Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in agent-free (npm)

MAL-2026-16013

Immediate action

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

npm uninstall agent-free

What this malware does

The npm package agent-free is malicious. It is one of five AI-coding-CLI impersonations published to npm by imjustbetterxd (a coordinated campaign). On use, the CLI reads the developer's LLM/provider API key - from environment variables (e.g. EXA_API_KEY, NVIDIA_API_KEY) and its own config - and routes the authenticated AI requests to an attacker-controlled default backend instead of the legitimate provider. Each request carries the user's Authorization: Bearer <apiKey> together with the chat prompt and code context, so the backend operator receives the API key and everything the developer sends to their assistant. Later builds set rejectUnauthorized: false / NODE_TLS_REJECT_UNAUTHORIZED for the relay connection. Payloads/updates are hosted on the GitHub account Marcus-Mok-GH.

The single published version (1.0.0) is affected. It relays to fireworks-endpoint--57crestcrepe.replit.app - the same backend used by codebuff-cli (1.0.4/1.0.10) and orbitron-tui (1.0.x), confirming the shared operator.

Malicious versions

all versions

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

Detection & response playbook

Credential / info stealer

Find it
Search your lockfiles and build artifacts for agent-free (all published versions).
If you installed it — respond
agent-free is built to steal secrets, so assume every credential the build or runtime could read is compromised. Remove it from your project and lockfile, then rotate ALL exposed secrets — npm/registry tokens, cloud keys, CI/CD secrets, SSH keys, and any .env values — from a known-clean machine. Audit logs for unauthorized use of those credentials.
Did it already run?
If agent-free 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. agent-free 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 agent-free-class packages before install and in CI — and if it already ran, its runtime egress monitoring catches the credential exfiltration and severs the channel.

Malware detection Runtime egress monitoring

Explore

All malware advisories How O3 detects malware Vulnerability database