# MAL-2026-5543: Malicious code in jailbreak-code (npm)


- **Type:** Malicious package
- **Package:** `jailbreak-code` (npm)
- **Published:** 11 Jun 2026

## What is MAL-2026-5543?

MAL-2026-5543 is a malicious package in jailbreak-code, published on 11 Jun 2026. 

### Official description

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.

## What should I do about MAL-2026-5543?

Remove the package from your dependencies and lockfiles, then rotate any secrets on machines where it was installed.

## Fix prompt for AI coding agents

```text
MAL-2026-5543 is a malicious package: jailbreak-code (npm). Every version was published to cause harm.

Task:
1. Search this repository's dependency manifests and lockfiles for the package, including transitive dependencies.
2. If it is present, remove it, regenerate the lockfile with the project's package manager, and replace whatever it was used for.
3. List any CI runners, developer machines or containers that installed it, so their secrets can be rotated.
4. If the package is not used anywhere, say so and change nothing.

Reference: https://insights.sbomify.com/MAL-2026-5543/ (Markdown: https://insights.sbomify.com/MAL-2026-5543/index.md)
```

## Sources

- OSV: https://osv.dev/vulnerability/MAL-2026-5543

---
From sbomify Insights: https://insights.sbomify.com/MAL-2026-5543/
Summaries are generated and may contain mistakes; the official description above is the record.