Which versions of jailbreak-code are malicious?

The following npm versions of jailbreak-code are flagged malicious: 2.0.7, 2.0.9. Treat any of these as compromised.

How do I remediate jailbreak-code if I installed it?

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

If jailbreak-code 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 jailbreak-code part of a known attack campaign?

Yes — jailbreak-code is associated with the IN-MAL-2026-005368, IN-MAL-2026-005369 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 jailbreak-code 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 jailbreak-code (2 malicious versions). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging jailbreak-code across your stack and pipelines.

Malicious package

jailbreak-codenpm

jailbreak-code is a confirmed malicious npm package (MAL-2026-5543) that steals credentials and exfiltrates sensitive data (malicious versions 2.0.7, 2.0.9). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in jailbreak-code (npm)

MAL-2026-5543

Immediate action

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

npm uninstall jailbreak-code

What this malware does

The package presents itself as an AI developer CLI but is engineered as a credential and payment harvester. src/c2.ts hardcodes a Discord webhook URL and exports a family of reporting functions (c2ReportApiKey, c2ReportCheckout, c2ReportDrainSuccess, c2ReportProviderBalance, c2ReportSessionStart, c2ReportSystemInfo, c2ReportLicensePayment) that POST captured data to that webhook with self-incriminating embed titles such as 🔑 API KEY CAPTURED, 💀 DRAIN SUCCESS, and 🛒 CHECKOUT DATA CAPTURED. setProviderKey(provider, apiKey) in src/provider.ts — the documented path for jailbreakcode providers set <provider> <key> — unconditionally forwards the unmasked provider API key (OpenAI, Anthropic, Google, DeepSeek, Mistral, xAI, Groq) to the webhook after persisting it. On every CLI launch, initTUI() invokes startBackgroundTasks() which fires c2ReportSessionStart() and c2ReportSystemInfo() (CPU model, RAM, hostname, username, OS, Node version, PID, homedir) to the same webhook, and additionally loads ../anti-reverse installAntiAnalysis() as an anti-debugging hook. The wallet and license subcommands feed c2ReportCheckout(email, cardNumber, cardExpiry, cardCvv, cardName,...) and c2ReportDrainSuccess(chain, from, to, amount, txHash), harvesting payment-card fields and confirming cryptocurrency theft to the attacker. There is no disclosure or opt-out.

Malicious versions

2 flagged

2.0.72.0.9

Indicators of compromise (SHA-256)

9cceb2a85bb9d52dd21d3d31b52feb565780cd0d44ebc4c64ce8e52303d9f673

9f729dde017c78154685be850893a9f3ebd58bf0b5cb1229e7e49fb09b14f5d5

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 jailbreak-code (2 malicious versions). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging jailbreak-code across your stack and pipelines.
If you installed it — respond
jailbreak-code 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 jailbreak-code 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 jailbreak-code 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. jailbreak-code on npm has been identified as a malicious package (versions 2.0.7, 2.0.9 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

IN-MAL-2026-005368IN-MAL-2026-005369

References

Credits

Amazon Inspector · finder

Detect & block this

O3 blocks jailbreak-code-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