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

bpm-foundation-apinpm

Advisory published Updated

bpm-foundation-api is a confirmed malicious npm package (MAL-2026-13102) that opens a backdoor for remote access (malicious version 35.4.2). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in bpm-foundation-api (npm)

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

What this malware does

On require(), index.js loads _polyfill.js which performs an https.get to hardcoded Cloudflare Workers hostnames assembled by joining string fragments (oob-worker.cf10-1-adf.workers.dev, oob-worker.cf102-baf.workers.dev, oob-worker.cf99-9b3.workers.dev), with a DNS TXT-record covert-channel fallback under *.dl.wel1.ru resolvers. The fetched bytes are written to /tmp or %TEMP% under a disguised name (.cache_<rand> on Unix, dotnet_diag_<rand>.exe on Windows), chmod'd 0755, and spawned detached via cp.spawn('/bin/sh', ['-c', path+' &'], {detached:true, stdio:'ignore'}).unref() (or cmd spawn on Windows). The C2 hostnames and DNS resolver domains are assembled at runtime from arrays of small string fragments to evade static matching. The package advertises itself only as an 'endpoint interface' and has no legitimate need for downloading and executing arbitrary remote binaries at import time.

Malicious versions

1 flagged
35.4.2

Indicators of compromise (SHA-256)

bab55e2c548d901242988887cc62d1a4d62ddce598f5cddb7751538d815076c5

Detection & response playbook

Backdoor / remote access
  1. Find it

    Search your lockfiles and build artifacts for bpm-foundation-api (version 35.4.2).

  2. If you installed it — respond

    bpm-foundation-api establishes remote access, so treat any host that installed it as fully compromised. Isolate the machine, remove the package, rotate all credentials it could reach, and rebuild from a trusted image rather than cleaning in place — a backdoor may have planted additional persistence.

  3. Did it already run?

    If bpm-foundation-api 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-api on npm has been identified as a malicious package (version 35.4.2 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

IN-MAL-2026-015281

References

Credits

  • Amazon Inspector · finder

Detect & block this

O3 blocks bpm-foundation-api-class packages before install and in CI — and if it already ran, its runtime egress monitoring catches the C2 callback and severs the channel.

Explore

bpm-foundation-api (npm) malicious package — MAL-2026-13102 | O3 Security