bpm-foundation-rate-usnpm
bpm-foundation-rate-us is a confirmed malicious npm package (MAL-2026-13115) that executes malicious code on install (malicious version 35.3.9). Do not install it — remove it immediately and rotate any exposed credentials.
Malicious code in bpm-foundation-rate-us (npm)
What this malware does
On any require()/import of bpm-foundation-rate-us, index.js loads compat.js, which assembles hostnames from split string fragments to hide the destinations oob-worker.cf<NNN>-<XXX>.workers.dev and, on HTTPS failure, falls back to reconstructing a base64 payload from DNS TXT records at sdk.dl.wel1.ru, ext.dl.wel1.ru, pkg.dl.wel1.ru, and net.dl.wel1.ru. The retrieved binary is written under a disguised name (dotnet_diag<rand>.exe on Windows,.cache_<rand> on POSIX) to %TEMP%/ /tmp, chmod 0755'd on POSIX, and spawned detached via /bin/sh or cmd.exe. A freshness marker at /tmp/.analytics_state and cover-story telemetry comments frame the behavior as analytics. The package name suggests a rate-adapter utility, which is inconsistent with fetching and executing an opaque native binary from Cloudflare Workers subdomains and DNS TXT channels.
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-rate-us (version 35.3.9). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging bpm-foundation-rate-us across your stack and pipelines.
If you installed it — respond
Remove bpm-foundation-rate-us 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-rate-us 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-rate-us 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-rate-us-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.