Which versions of bpm-foundation-auth are malicious?

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

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

Remove bpm-foundation-auth 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-auth — how do I know if it already compromised me?

If bpm-foundation-auth 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-auth part of a known attack campaign?

Yes — bpm-foundation-auth is associated with the IN-MAL-2026-015288 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-auth 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-auth (version 35.2.9). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging bpm-foundation-auth across your stack and pipelines.

Malicious package

bpm-foundation-authnpm

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

Malicious code in bpm-foundation-auth (npm)

MAL-2026-13104

Immediate action

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

npm uninstall bpm-foundation-auth

What this malware does

On require('bpm-foundation-auth'), index.js loads adapter.js which selects a platform-specific asset and downloads an opaque native binary over HTTPS from string-concatenated Cloudflare Workers hostnames (oob-worker.cf101-adf.workers.dev, oob-worker.cf102-baf.workers.dev, oob-worker.cf99-9b3.workers.dev, oob-worker.cf103-070.workers.dev), with a DNS-TXT base64-chunked fallback keyed off sdk.dl.wel1.ru. The fetched bytes are written to /var/tmp/.cache<hex> or %TEMP%\dotnet_diag_<hex>.exe, chmod 0755, and spawned detached via /bin/sh -c or cmd.exe (_adapter.js line 122-128). Network destinations are constructed by array-join to avoid appearing as literal strings. A main() gate checks DISABLE_TELEMETRY / ANALYTICS_OPT_OUT / DO_NOT_TRACK env flags and writes a freshness marker to suppress repeat runs, using cover-story naming ('analytics_state', 'telemetry'). Destinations are anonymous Cloudflare Workers subdomains unrelated to any publisher; the fetched binary is not hash- or signature-verified; the staging paths are hidden dotfiles and diag-named executables. The package presents itself as an auth module but its module-load behavior is a native-binary dropper.

Malicious versions

1 flagged

35.2.9

Indicators of compromise (SHA-256)

da9be4e91e8e8a5c0eea771a43103f8fde8202cd1a817fa7d511d8ab81788442

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-auth (version 35.2.9). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging bpm-foundation-auth across your stack and pipelines.
If you installed it — respond
Remove bpm-foundation-auth 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-auth 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-auth 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-auth on npm has been identified as a malicious package (version 35.2.9 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

IN-MAL-2026-015288

References

npmjs.com

Credits

Amazon Inspector · finder

Detect & block this

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