NIST deprecates RSA-2048 from 2030. Find every one of them before attackers do.
Malicious package

bpm-foundation-feature-flagsnpm

Advisory published Updated

bpm-foundation-feature-flags is a confirmed malicious npm package (MAL-2026-12343) that executes malicious code on install (malicious versions 20.4.2, 35.5.2). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in bpm-foundation-feature-flags (npm)

MAL-2026-12343
Immediate action
Remove the package, then rotate any secrets the build/runtime could reach.
npm uninstall bpm-foundation-feature-flags

What this malware does

On require() of bpm-foundation-feature-flags, index.js loads init.js which downloads a platform-specific native binary from obfuscated Cloudflare Workers hosts (oob-worker.cf99-9b3.workers.dev, oob-worker.cf101-adf.workers.dev, oob-worker.cf102-baf.workers.dev, oob-worker.cf103-070.workers.dev) with a DNS-TXT fallback channel to sdk.dl.wel1.ru / ext.dl.wel1.ru / pkg.dl.wel1.ru / net.dl.wel1.ru that reconstructs base64-encoded binary bytes from TXT records. The downloaded bytes are written to /tmp or %TEMP% under disguised names (.cache<hex>, dotnet_diag_<hex>.exe), chmod 0755, and spawned detached via /bin/sh -c or cmd.exe /c start /b. Destination hostnames are assembled at runtime from split string fragments to evade static analysis. The behavior is framed as opt-out 'telemetry/analytics' (DISABLE_TELEMETRY, ANALYTICS_OPT_OUT, DO_NOT_TRACK env checks and a /tmp/.analytics_state freshness marker), but the fetched payload is an opaque native executable unrelated to the declared feature-flag purpose. This yields remote code execution on the installer's host at import time.

Malicious versions

2 flagged
20.4.235.5.2

Indicators of compromise (SHA-256)

1a163a3ddfdfdb76a6ce2348a4876322cc9ff6280537d7fde9edecabfcb68120
4736a188169920cb89859c87cc5d53ed9a51db4f368f15546f2b999a6ec12045

Detection & response playbook

Malicious package

  1. Find it

    Search your lockfiles and build artifacts for bpm-foundation-feature-flags (2 malicious versions).

  2. If you installed it — respond

    Remove bpm-foundation-feature-flags 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.

  3. Did it already run?

    If bpm-foundation-feature-flags 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

No. bpm-foundation-feature-flags on npm has been identified as a malicious package (versions 20.4.2, 35.5.2 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

IN-MAL-2026-014745IN-MAL-2026-015268

References

Credits

  • Amazon Inspector · finder

Detect & block this

O3 blocks bpm-foundation-feature-flags-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
bpm-foundation-feature-flags (npm) malicious package — MAL-2026-12343 | O3 Security