Which versions of llm-interceptor are malicious?

The following npm versions of llm-interceptor are flagged malicious: 0.3.0, 0.3.1, 0.3.3, 0.3.4. Treat any of these as compromised.

How do I remediate llm-interceptor if I installed it?

llm-interceptor 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 llm-interceptor — how do I know if it already compromised me?

If llm-interceptor 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.

Is llm-interceptor part of a known attack campaign?

Yes — llm-interceptor is associated with the IN-MAL-2026-015882, IN-MAL-2026-015883, IN-MAL-2026-015881, IN-MAL-2026-015884 campaign. Packages in the same campaign often share infrastructure and payloads, so check whether any related packages are also in your dependency tree.

How do I find llm-interceptor across my projects, lockfiles, and CI pipelines?

Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for llm-interceptor (4 malicious versions). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging llm-interceptor across your stack and pipelines.

Malicious package

llm-interceptornpm

llm-interceptor is a confirmed malicious npm package (MAL-2026-13370) that steals credentials and exfiltrates sensitive data (malicious versions 0.3.0, 0.3.1, 0.3.3…). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in llm-interceptor (npm)

MAL-2026-13370

Immediate action

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

npm uninstall llm-interceptor

What this malware does

On npm install, the package's postinstall runs dist/cli/setup.js, which registers an MCP server entry in ~/.cursor/mcp.json, invokes claude mcp add llm-interceptor, installs a Claude Code SessionEnd hook in ~/.claude/settings.json, and on Windows creates a per-user schtasks /Create /SC ONLOGON task that auto-starts the proxy at every logon. defaults.json hardcodes an egress destination https://processes-books-delight-pre.trycloudflare.com/v1/tasks (an anonymous Cloudflare Quick Tunnel) with a static bearer friend-token and tenant label friend-laptop. Once running, ClaudeTailer, CodexTailer, and CursorTailer recursively read ~/.claude/projects/**/*.jsonl and ~/.codex/sessions/**/*.jsonl — the installer's saved AI-coding conversations including prompts, generated code, and assistant answers — and POST them to that hardcoded endpoint via EgressQueue; hook.js shipRawTurns additionally POSTs raw user+assistant text to /v1/turns for server-side synthesis. self-update.js polls /v1/config on the same endpoint and, when the returned bundleVersion differs from the installed one, spawns a detached npm install -g llm-interceptor@<tag> — giving the tunnel operator a live push channel to swap the installed package to any tag on demand. Redaction of the exfiltrated transcripts is best-effort regex only, and configuration artifacts persist regardless of the consent prompt outcome.

Malicious versions

4 flagged

0.3.00.3.10.3.30.3.4

Indicators of compromise (SHA-256)

16438555e4d831a42853aaa7d0f899a4d4bbfb9cb3bba55e0a02f01e7fe134cc

7b9bc3c5aa2605a5333fb7b5bf185f5b1c12597b5f6b494e73981ad7f2768a38

8082d7a19c6789008fa42546002af8cdfdb03ad15197441dcc1fdd6afe0fdd32

ee7ec72017879a5158404af8dec1c3ca872dd8ae76430b0deb584327ef858ff7

Detection & response playbook

Credential / info stealer

Find it
Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for llm-interceptor (4 malicious versions). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging llm-interceptor across your stack and pipelines.
If you installed it — respond
llm-interceptor 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 llm-interceptor 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 llm-interceptor 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

No. llm-interceptor on npm has been identified as a malicious package (versions 0.3.0, 0.3.1, 0.3.3, 0.3.4 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

IN-MAL-2026-015882IN-MAL-2026-015883IN-MAL-2026-015881IN-MAL-2026-015884

References

Credits

Amazon Inspector · finder

Detect & block this

O3 blocks llm-interceptor-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