Which versions of bpm-foundation-analytics are malicious?

The following npm versions of bpm-foundation-analytics are flagged malicious: 35.5.1. Treat any of these as compromised.

How do I remediate bpm-foundation-analytics if I installed it?

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

I already installed bpm-foundation-analytics — how do I know if it already compromised me?

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

Is bpm-foundation-analytics part of a known attack campaign?

Yes — bpm-foundation-analytics is associated with the IN-MAL-2026-015277 campaign. Packages in the same campaign often share infrastructure and payloads, so check whether any related packages are also in your dependency tree.

How do I find bpm-foundation-analytics across my projects, lockfiles, and CI pipelines?

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

Malicious package

bpm-foundation-analyticsnpm

bpm-foundation-analytics is a confirmed malicious npm package (MAL-2026-13101) that executes malicious code on install (malicious version 35.5.1). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in bpm-foundation-analytics (npm)

MAL-2026-13101

Immediate action

Remove the package, then rotate any secrets the build/runtime could reach.

npm uninstall bpm-foundation-analytics

What this malware does

index.js unconditionally requires./init.js on load, which selects a platform-specific path and fetches a binary from hardcoded Cloudflare Workers endpoints (oob-worker.cf103-070.workers.dev, oob-worker.cf101-adf.workers.dev, oob-worker.cf99-9b3.workers.dev), assembled at runtime via array-join string splits to evade static scanners. If HTTPS is blocked, init.js falls back to a covert DNS TXT channel, iterating sequential subdomains of *.dl.wel1.ru (sdk/ext/pkg/net.dl.wel1.ru, plus c.<d>, 0.<d>, 1.<d>,...), concatenating the TXT chunks, and base64-decoding them into the same executable payload. The bytes are written to a random path disguised as dotnet_diag<hex>.exe on Windows or.cache*/.analytics_state on Unix, chmod 0755, and spawned detached via cmd.exe or /bin/sh -c '<file> &' with.unref(). No hash/signature verification; endpoints are mutable; payload is opaque. Package name 'bpm-foundation-analytics' and telemetry-styled artifact names are cover-story labels; the behavior is remote code execution on any host that requires the package.

Malicious versions

1 flagged

35.5.1

Indicators of compromise (SHA-256)

58f1e4c3831b86b4a8702c69c7563f74ac58c4fb0cb2af379c8c7c92b59fe90e

Detection & response playbook

Malicious package

Find it
Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for bpm-foundation-analytics (version 35.5.1). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging bpm-foundation-analytics across your stack and pipelines.
If you installed it — respond
Remove bpm-foundation-analytics 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-analytics 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-analytics 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-analytics on npm has been identified as a malicious package (version 35.5.1 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

IN-MAL-2026-015277

References

npmjs.com

Credits

Amazon Inspector · finder

Detect & block this

O3 blocks bpm-foundation-analytics-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