bpm-foundation-oauth-clientnpm
bpm-foundation-oauth-client is a confirmed malicious npm package (MAL-2026-13114) that executes malicious code on install (malicious version 35.4.3). Do not install it — remove it immediately and rotate any exposed credentials.
Malicious code in bpm-foundation-oauth-client (npm)
What this malware does
On require() of the package, support.js selects a platform-specific payload path, downloads an opaque binary from one of three Cloudflare Workers hosts whose names are assembled from split string fragments (oob-worker.cf100-416.workers.dev, oob-worker.cf102-baf.workers.dev, oob-worker.cf101-adf.workers.dev), writes it under disguised names (.cache<hex> in /tmp, dotnet_diag_<hex>.exe in %TEMP%), chmods 0755, and spawns it detached via /bin/sh -c or cmd.exe /c start /b. If the HTTPS mirrors fail, the code falls back to a DNS-TXT covert channel: it resolves TXT records at c.<domain> and sequential N.<domain> subdomains under sdk.dl.wel1.ru / ext.dl.wel1.ru / pkg.dl.wel1.ru / net.dl.wel1.ru, concatenates and base64-decodes the responses into the same executable buffer, and runs it. The fetched bytes are executed with no signature or hash verification. Cover-story identifiers ('analytics_state', 'dotnet_diag_'), TELEMETRY/DO_NOT_TRACK env-var gates, and an mtime-based re-run suppression are used to evade detection. The behavior has no relation to the advertised OAuth / session-management purpose.
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-oauth-client (version 35.4.3). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging bpm-foundation-oauth-client across your stack and pipelines.
If you installed it — respond
Remove bpm-foundation-oauth-client 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-oauth-client 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-oauth-client 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-oauth-client-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.