Your RSA-2048 keys break in 2030. Find every one of them before attackers do.
Malicious package

bpm-foundation-test-jasminenpm

bpm-foundation-test-jasmine is a confirmed malicious npm package (MAL-2026-13121) that executes malicious code on install (malicious version 35.7.9). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in bpm-foundation-test-jasmine (npm)

MAL-2026-13121
Immediate action
Remove the package, then rotate any secrets the build/runtime could reach.
npm uninstall bpm-foundation-test-jasmine

What this malware does

On require() of the package, index.js loads bridge.js, which reconstructs Cloudflare Workers hostnames from split string fragments (oob-worker.cf100-416/cf101-adf/cf102-baf.workers.dev) with a DNS TXT chunked base64 fallback via *.dl.wel1.ru, downloads a platform-specific executable, writes it to a hidden temp path (/var/tmp/.cache<hex> on Unix, %TEMP%/dotnet_diag_<hex>.exe on Windows) chosen to imitate benign OS artifacts, chmods it 0755 on Unix, and detach-spawns it via spawn("/bin/sh",["-c", fp+" &"], {detached:true}) or cmd.exe /c start /b. A DISABLE_TELEMETRY-style env gate is used as cover. The package is named as a test harness but the fetched binary is opaque, purpose-mismatched, and executed unconditionally on import.

Malicious versions

1 flagged
35.7.9

Indicators of compromise (SHA-256)

e9fd53d190d78da3b8aef57cfd6df656093743bc766ecb0f212c464c74b88319

Detection & response playbook

Malicious package
  1. Find it

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

  2. If you installed it — respond

    Remove bpm-foundation-test-jasmine from your project and lockfile, then assume any secrets accessible to the build or runtime were exposed: rotate API keys, tokens, and credentials, and audit for unexpected outbound activity or persistence.

  3. Did it already run?

    If bpm-foundation-test-jasmine 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.

  4. How O3 protects you

    O3 blocks bpm-foundation-test-jasmine 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. bpm-foundation-test-jasmine on npm has been identified as a malicious package (version 35.7.9 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

IN-MAL-2026-015258

References

Credits

  • Amazon Inspector · finder

Detect & block this

O3 blocks bpm-foundation-test-jasmine-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.

Explore

bpm-foundation-test-jasmine (npm) malicious package — MAL-2026-13121 | O3 Security