Your RSA-2048 keys break in 2030. Find every one of them before attackers do.
Malicious package

bpm-foundation-tcs-configsnpm

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)

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

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

1 flagged
35.3.3

Indicators of compromise (SHA-256)

e3a42f343712987873cf8ad18e70cc172666edc3b079149cae4d449ceadf2262

Detection & response playbook

Credential / info stealer

  1. Find it

    Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for bpm-foundation-tcs-configs (version 35.3.3). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging bpm-foundation-tcs-configs across your stack and pipelines.

  2. 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.

  3. Did it already run?

    If bpm-foundation-tcs-configs 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.

  4. How O3 protects you

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

Campaign

IN-MAL-2026-015265

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.

Malware detection Runtime egress monitoring

Explore

All malware advisories How O3 detects malware Vulnerability database
bpm-foundation-tcs-configs (npm) malicious package — MAL-2026-13120 | O3 Security