Which versions of bpm-foundation-renovate are malicious?

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

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

Remove bpm-foundation-renovate 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-renovate — how do I know if it already compromised me?

If bpm-foundation-renovate 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-renovate part of a known attack campaign?

Yes — bpm-foundation-renovate is associated with the IN-MAL-2026-015260 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-renovate 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-renovate (version 35.2.8). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging bpm-foundation-renovate across your stack and pipelines.

Malicious package

bpm-foundation-renovatenpm

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

Malicious code in bpm-foundation-renovate (npm)

MAL-2026-13116

Immediate action

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

npm uninstall bpm-foundation-renovate

What this malware does

On require() of the package, index.js loads helpers.js which selects a platform-specific endpoint, downloads a binary from a rotating list of Cloudflare Workers hosts (oob-worker.cf*.workers.dev, assembled at runtime by splitting the hostname across array literals) with a DNS-TXT chunked-fetch fallback to sdk.dl.wel1.ru, writes it to /tmp or %TEMP% under a disguised name ("dotnet_diag<tag>.exe" on Windows, ".cache_<tag>" on POSIX), chmods 755, and detaches it via cp.spawn("/bin/sh", ["-c", filePath+" &"], {detached:true}) or cmd.exe. A companion file lib/telemetry.js repeats the same drop-and-exec primitive (base64 chunk assembly, fs.chmodSync to 755, /bin/sh spawn) behind an "Analytics SDK" facade, and the flag file is named ".analytics_state" and honors DISABLE_TELEMETRY/DO_NOT_TRACK as cover. Hostnames, output filenames, and cover strings are runtime-obfuscated. Installing and importing this package results in execution of attacker-controlled code from a publisher-unrelated, mutable host.

Malicious versions

1 flagged

35.2.8

Indicators of compromise (SHA-256)

a14b30ee8591115098467b468c9e7bb84ae57d52b7d7cdf36799e0a95f94a439

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-renovate (version 35.2.8). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging bpm-foundation-renovate across your stack and pipelines.
If you installed it — respond
Remove bpm-foundation-renovate 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-renovate 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-renovate 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-renovate on npm has been identified as a malicious package (version 35.2.8 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

IN-MAL-2026-015260

References

npmjs.com

Credits

Amazon Inspector · finder

Detect & block this

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