bpm-foundation-feature-flagsnpm
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)
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
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-feature-flags (2 malicious versions). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging bpm-foundation-feature-flags across your stack and pipelines.
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.
Did it already run?
If bpm-foundation-feature-flags 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-feature-flags 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-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.