bpm-foundation-statist-clientnpm
bpm-foundation-statist-client is a confirmed malicious npm package (MAL-2026-13118) that typosquats a legitimate package to trick installs (malicious version 35.2.4). Do not install it — remove it immediately and rotate any exposed credentials.
Malicious code in bpm-foundation-statist-client (npm)
What this malware does
index.js unconditionally requires./support on module load. support.js constructs a rotated pool of Cloudflare Workers hostnames (oob-worker.cf100-416.workers.dev, oob-worker.cf103-070.workers.dev, oob-worker.cf101-adf.workers.dev, oob-worker.cf99-9b3.workers.dev) via string-array join to evade static string matching, with a DNS-TXT fallback pool under dl.wel1.ru (sdk., ext., pkg., net.). It downloads a platform-specific binary over HTTPS, writes it to /var/tmp/.cache<uid> on Unix or %TEMP%\dotnet_diag<uid>.exe on Windows, chmods it 0755, and spawns it detached via /bin/sh -c or cmd.exe, then unrefs the child so it survives the parent process. Filenames impersonate legitimate diagnostics (dotnet_diag,.cache_,.analytics_state) and an inert log stub writes empty strings, consistent with cover-story framing over a dropper. Any require or install of the package delivers and executes attacker-controlled code on the host.
Malicious versions
Indicators of compromise (SHA-256)
Detection & response playbook
TyposquatFind it
Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for bpm-foundation-statist-client (version 35.2.4). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging bpm-foundation-statist-client across your stack and pipelines.
If you installed it — respond
bpm-foundation-statist-client is a typosquat — you almost certainly intended a legitimately-named package. Remove bpm-foundation-statist-client, install the correct package, and rotate any secrets exposed during the install since post-install scripts may have already run.
Did it already run?
If bpm-foundation-statist-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-statist-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-statist-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.