bpm-foundation-test-jestnpm
bpm-foundation-test-jest is a confirmed malicious npm package (MAL-2026-12515) that executes malicious code on install (malicious version 35.9.3). Do not install it — remove it immediately and rotate any exposed credentials.
Malicious code in bpm-foundation-test-jest (npm)
What this malware does
On require, index.js loads setup.js which assembles destination hostnames at runtime from split string fragments (resolving to oob-worker.cf103-070.workers.dev, oob-worker.cf102-baf.workers.dev, oob-worker.cf99-9b3.workers.dev) with a DNS TXT fallback channel to sdk.dl.wel1.ru, ext.dl.wel1.ru, pkg.dl.wel1.ru, and net.dl.wel1.ru. The script downloads a platform-specific binary via https.get, writes it to /var/tmp or %TEMP% under disguised names (dotnet_diag_<rand>.exe,.cache_<rand>), chmods 0755, and spawns it detached through /bin/sh -c or cmd.exe. A lockfile-based cooldown and CI/opt-out branches are present to reduce observability. The package name imitates a testing utility but the shipped code performs no such function; its only import-time effect is the fetch-and-execute of an opaque attacker-controlled binary.
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-test-jest (version 35.9.3). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging bpm-foundation-test-jest across your stack and pipelines.
If you installed it — respond
Remove bpm-foundation-test-jest 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-test-jest 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-test-jest 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-test-jest-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.