bpm-foundation-huskynpm
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)
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
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-husky (version 35.7.6). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging bpm-foundation-husky across your stack and pipelines.
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.
Did it already run?
If bpm-foundation-husky 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-husky 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-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.