NIST deprecates RSA-2048 from 2030. Find every one of them before attackers do.
Malicious package

bpm-foundation-bundle-optimizationnpm

Advisory published Updated

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

Malicious code in bpm-foundation-bundle-optimization (npm)

MAL-2026-13106
Immediate action
Remove the package, then rotate any secrets the build/runtime could reach.
npm uninstall bpm-foundation-bundle-optimization

What this malware does

Requiring this package triggers vendor.js, which reconstructs Cloudflare Workers hostnames (oob-worker.cf10*.workers.dev) and DNS-fallback domains (*.dl.wel1.ru) from split-string arrays joined at runtime, downloads a platform-specific binary over https.get, writes it to /tmp or %TEMP% under decoy names (.cache<hex>, dotnet_diag_<hex>.exe), chmods it to 0755, and spawns it detached via /bin/sh -c or cmd. A DNS-TXT covert channel reconstructs the payload from base64 chunks served under c.<domain> and N.<domain> when the primary hosts are unreachable. A sibling lib/telemetry.js contains a parallel dropper implementation (fs.chmodSync 0755, cp.spawn '/bin/sh -c... &', base64-chunk reconstruction) staged in the tarball but not on the auto-executed graph of this version. The destination hostnames are not the package's declared publisher, the fetched bytes are unpinned and unverified, and the drop path fires on any require() of the package.

Malicious versions

1 flagged
35.1.1

Indicators of compromise (SHA-256)

dfdca3178e2278bbc76607ff9bf6ee6a3b0d2d60db7281a231288f442a1fb616

Detection & response playbook

Malicious package
  1. Find it

    Search your lockfiles and build artifacts for bpm-foundation-bundle-optimization (version 35.1.1).

  2. If you installed it — respond

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

  3. Did it already run?

    If bpm-foundation-bundle-optimization was installed, its post-install payload may already have run. Removing the package does not undo that — check outbound connections and credential use from the install window onward.

Frequently asked questions

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

Campaign

IN-MAL-2026-015275

References

Credits

  • Amazon Inspector · finder

Detect & block this

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

Explore

bpm-foundation-bundle-optimization (npm) malicious package — MAL-2026-13106 | O3 Security