bpm-foundation-date-rangenpm
bpm-foundation-date-range is a confirmed malicious npm package (MAL-2026-13108) that executes malicious code on install (malicious version 35.4.2). Do not install it — remove it immediately and rotate any exposed credentials.
Malicious code in bpm-foundation-date-range (npm)
What this malware does
Requiring the package's main entry triggers polyfill.js, which selects a platform-specific endpoint and downloads a native binary over HTTPS from hostnames assembled by Array.join from split string fragments (Cloudflare Workers mirrors such as oob-worker.cf*-*.workers.de). If HTTPS mirrors fail, a covert DNS-TXT retrieval channel keyed by platform (sdk.dl.wel1.ru, ext.dl.wel1.ru, pkg.dl.wel1.ru, net.dl.wel1.ru) reconstructs the binary from base64-chunked TXT records. The downloaded bytes are written to /tmp or %TEMP% under disguised names (dotnet_diag<hex>.exe,.cache_<hex>), chmodded 0755 on POSIX, and spawned detached via /bin/sh -c "<path> &" or cmd.exe /c start. No hash or signature is verified, the payload host is not the package publisher, and the package's advertised purpose (a date-range utility) has no legitimate need to fetch or run a native 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-date-range (version 35.4.2). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging bpm-foundation-date-range across your stack and pipelines.
If you installed it — respond
Remove bpm-foundation-date-range 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-date-range 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-date-range 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-date-range-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.