What does the bpm-foundation-storage malware do?

On require, index.js loads _ext.js, which selects a platform-specific path, fetches an executable over HTTPS from string-concatenation-obfuscated hosts on the *.workers.dev and *.dl.wel1.ru namespaces (with a DNS TXT-record fallback that base64-decodes concatenated chunks into a binary), writes it to a temp directory under a masquerading name such as dotnet_diag_ .exe on Windows or.cache_ on POSIX, chmods 0755, and spawns it detached via /bin/sh -c or cmd.exe /c start /b. There is no hash or signature verification, destinations are reconstructed at runtime from split substring arrays, and a secondary DNS-over-TXT loader provides resilience against domain blocking. Any consumer that

Which versions of bpm-foundation-storage are malicious?

The following npm versions of bpm-foundation-storage are flagged malicious: 35.8.1. Treat any of these as compromised.

How do I remediate bpm-foundation-storage if I installed it?

Remove bpm-foundation-storage 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.

I already installed bpm-foundation-storage — how do I know if it already compromised me?

If bpm-foundation-storage 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.

Is bpm-foundation-storage part of a known attack campaign?

Yes — bpm-foundation-storage is associated with the IN-MAL-2026-015270 campaign. Packages in the same campaign often share infrastructure and payloads, so check whether any related packages are also in your dependency tree.

How do I find bpm-foundation-storage across my projects, lockfiles, and CI pipelines?

Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for bpm-foundation-storage (version 35.8.1). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging bpm-foundation-storage across your stack and pipelines.

Malicious package

bpm-foundation-storagenpm

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

Malicious code in bpm-foundation-storage (npm)

MAL-2026-13119

Immediate action

Remove the package, then rotate any secrets the build/runtime could reach.

npm uninstall bpm-foundation-storage

What this malware does

On require, index.js loads ext.js, which selects a platform-specific path, fetches an executable over HTTPS from string-concatenation-obfuscated hosts on the *.workers.dev and *.dl.wel1.ru namespaces (with a DNS TXT-record fallback that base64-decodes concatenated chunks into a binary), writes it to a temp directory under a masquerading name such as dotnet_diag<hex>.exe on Windows or.cache_<hex> on POSIX, chmods 0755, and spawns it detached via /bin/sh -c or cmd.exe /c start /b. There is no hash or signature verification, destinations are reconstructed at runtime from split substring arrays, and a secondary DNS-over-TXT loader provides resilience against domain blocking. Any consumer that require()s bpm-foundation-storage triggers execution of attacker-controlled code on the installer's host. The package's declared purpose is a storage library; none of the observed behavior is consistent with that purpose.

Malicious versions

1 flagged

35.8.1

Indicators of compromise (SHA-256)

9e1e2729c7a957ee4366b693a24d178137743df7bf2ee5d65d3cecf3c8cfdc5f

Detection & response playbook

Malicious package

Find it
Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for bpm-foundation-storage (version 35.8.1). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging bpm-foundation-storage across your stack and pipelines.
If you installed it — respond
Remove bpm-foundation-storage 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-storage 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-storage 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

No. bpm-foundation-storage on npm has been identified as a malicious package (version 35.8.1 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

IN-MAL-2026-015270

References

npmjs.com

Credits

Amazon Inspector · finder

Detect & block this

O3 blocks bpm-foundation-storage-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.

Malware detection Runtime egress monitoring

Explore

All malware advisories How O3 detects malware Vulnerability database