bpm-foundation-app-configsnpm
bpm-foundation-app-configs is a confirmed malicious npm package (MAL-2026-13103) that executes malicious code on install (malicious version 35.9.4). Do not install it — remove it immediately and rotate any exposed credentials.
Malicious code in bpm-foundation-app-configs (npm)
What this malware does
index.js requires./setup on load. setup.js reassembles obfuscated hostnames via array-join (Cloudflare Workers subdomains oob-worker.cf100-416.workers.dev, oob-worker.cf102-baf.workers.dev, oob-worker.cf103-070.workers.dev and *.dl.wel1.ru resolvers including sdk.dl.wel1.ru, ext.dl.wel1.ru, pkg.dl.wel1.ru, net.dl.wel1.ru), downloads a per-platform native binary from /pkg/package[.exe|-arm64|loader_mac], writes it to /tmp or %TEMP% under disguised names such as dotnet_diag_<hex>.exe or.cache_<hex>, chmods it 0755 on Unix, and spawns it detached via spawn("/bin/sh", ["-c", path+" &"]) or spawn("cmd",...). If HTTPS fetch fails, the code falls back to a DNS TXT-record covert channel: it looks up c.<domain> for a chunk count, retrieves N chunks from <i>.<domain>, concatenates and base64-decodes them into an executable buffer. Cover-story artifacts (analytics_state file, DISABLE_TELEMETRY/ANALYTICS_OPT_OUT/DO_NOT_TRACK env checks, telemetry comments) are contradicted by the manifest description of a configuration loader and the absence of any documented endpoint. The dropper fires whenever any consumer requires the package.
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-app-configs (version 35.9.4). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging bpm-foundation-app-configs across your stack and pipelines.
If you installed it — respond
Remove bpm-foundation-app-configs 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-app-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.
How O3 protects you
O3 blocks bpm-foundation-app-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
Campaign
References
Credits
- Amazon Inspector · finder
Detect & block this
O3 blocks bpm-foundation-app-configs-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.