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

bpm-foundation-huskynpm

Advisory published Updated

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

Malicious code in bpm-foundation-husky (npm)

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

What this malware does

index.js unconditionally requires runtime.js on module load. runtime.js selects a platform-specific endpoint (/pkg/package, /pkg/package-arm64, /pkg/loader_mac, /pkg/package.exe), fetches a binary over HTTPS from one of four hardcoded *.workers.dev hosts whose names are assembled at runtime via string-split-and-join (e.g. ["oob-worker.cf99-9b3.worke","rs.de","v"].join("")), with a DNS TXT-record fallback channel to *.dl.wel1.ru that pulls a base64-encoded payload in chunks and reassembles it. The fetched bytes are written to /var/tmp/.cache<rand> on Unix or %TEMP%\dotnet_diag<rand>.exe on Windows, chmod 0755'd, and spawned detached via /bin/sh -c or cmd.exe. No hash or signature verification is performed; the destinations are anonymous Cloudflare Workers subdomains unrelated to any documented purpose of the package. A once-per-~6h marker file limits re-execution to evade detection. The hostname obfuscation, hidden-dotfile / dotnet_diag masquerade staging paths, and DNS covert-channel fallback confirm intentional evasion rather than any legitimate install behavior.

Malicious versions

1 flagged
35.7.6

Indicators of compromise (SHA-256)

21475dd98fee2f2d3e7494802e5ae0a3b1db091e1abeb496d71091bbd73e7956

Detection & response playbook

Malicious package
  1. Find it

    Search your lockfiles and build artifacts for bpm-foundation-husky (version 35.7.6).

  2. If you installed it — respond

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

Campaign

IN-MAL-2026-015262

References

Credits

  • Amazon Inspector · finder

Detect & block this

O3 blocks bpm-foundation-husky-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-husky (npm) malicious package — MAL-2026-13111 | O3 Security