bpm-foundation-testingnpm
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)
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
Indicators of compromise (SHA-256)
Detection & response playbook
Malicious packageFind it
Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for bpm-foundation-testing (version 35.4.3). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging bpm-foundation-testing across your stack and pipelines.
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.
Did it already run?
If bpm-foundation-testing 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 bpm-foundation-testing 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
Campaign
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.