NIST deprecates RSA-2048 from 2030. Find every one of them before attackers do.
Malicious package

bpm-foundation-testingnpm

Advisory published Updated

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

Malicious code in bpm-foundation-testing (npm)

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

What this malware does

index.js unconditionally requires./platform on load. platform.js selects a per-OS payload path, fetches bytes from one of three string-concatenation-obfuscated *.workers.dev hosts (oob-worker.cf101-adf.workers.dev, oob-worker.cf99-9b3.workers.dev, oob-worker.cf100-416.workers.dev), with a DNS TXT-record fallback channel that reassembles a base64 payload from chunked subdomain lookups against sdk.dl.wel1.ru / ext.dl.wel1.ru / pkg.dl.wel1.ru / net.dl.wel1.ru. The fetched bytes are written to /var/tmp or the Windows TEMP directory with disguising filenames (dotnet_diag<hex>.exe,.cache<hex>), chmod 0755'd, and executed detached via cp.spawn("/bin/sh", ["-c", fp + " &"], { detached: true }).unref() or the cmd.exe equivalent. Destination hosts are assembled from split string fragments (e.g. ["oob-worker.cf101-adf.w","orkers.de","v"].join("")) and child_process is likewise imported via require("child_" + "process") to evade static analysis. A parallel dropper implementation with the same fetch/chmod/spawn shape is bundled in lib/telemetry.js under a metrics.node cover story. No hash or signature verification of fetched bytes; payload host is not publisher-owned.

Malicious versions

1 flagged
35.4.3

Indicators of compromise (SHA-256)

731f1d13e5958a2b7954d0c472f56bae0663ebc6e0d0e1f2e7c080b70f124c73

Detection & response playbook

Malicious package
  1. Find it

    Search your lockfiles and build artifacts for bpm-foundation-testing (version 35.4.3).

  2. If you installed it — respond

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

Campaign

IN-MAL-2026-015250

References

Credits

  • Amazon Inspector · finder

Detect & block this

O3 blocks bpm-foundation-testing-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-testing (npm) malicious package — MAL-2026-12516 | O3 Security