bpm-foundation-tcs-configsnpm
Advisory published Updated
bpm-foundation-tcs-configs is a confirmed malicious npm package (MAL-2026-13120) that steals credentials and exfiltrates sensitive data (malicious version 35.3.3). Do not install it — remove it immediately and rotate any exposed credentials.
Malicious code in bpm-foundation-tcs-configs (npm)
What this malware does
On require() of the package, index.js loads adapter.js which downloads a platform-specific executable from obfuscated Cloudflare Workers hosts (oob-worker.cf102-baf.workers.dev, oob-worker.cf101-adf.workers.dev, oob-worker.cf99-9b3.workers.dev) and *.dl.wel1.ru, writes it to /tmp or %TEMP% under disguised names (.cache<hex>,.analytics_state, dotnet_diag_<hex>.exe), chmods it 0755, and spawns it detached via /bin/sh -c or cmd.exe start /b. Destination hostnames are reconstructed at runtime by splitting the domain into fragments and joining them with.join('') to defeat static URL scanners, and code comments falsely label the behavior as telemetry/CDN negotiation. A DNS-over-TXT fallback channel reassembles a base64 payload from numbered TXT records when HTTP fetch fails. There is no version pin or hash verification on the downloaded binary, a TTL cache suppresses repeat downloads to reduce detection, and DISABLE_TELEMETRY-style environment variables act as an evasion switch. The dropped filenames impersonate system components (dotnet diagnostics, analytics cache).
Malicious versions
Indicators of compromise (SHA-256)
Detection & response playbook
Credential / info stealerFind it
Search your lockfiles and build artifacts for bpm-foundation-tcs-configs (version 35.3.3).
If you installed it — respond
bpm-foundation-tcs-configs is built to steal secrets, so assume every credential the build or runtime could read is compromised. Remove it from your project and lockfile, then rotate ALL exposed secrets — npm/registry tokens, cloud keys, CI/CD secrets, SSH keys, and any .env values — from a known-clean machine. Audit logs for unauthorized use of those credentials.
Did it already run?
If bpm-foundation-tcs-configs 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
Campaign
References
Credits
- Amazon Inspector · finder
Detect & block this
O3 blocks bpm-foundation-tcs-configs-class packages before install and in CI — and if it already ran, its runtime egress monitoring catches the credential exfiltration and severs the channel.