Your RSA-2048 keys break in 2030. Find every one of them before attackers do.
Malicious package

bpm-renovate-renovate-confignpm

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

Malicious code in bpm-renovate-renovate-config (npm)

MAL-2026-12517
Immediate action
Remove the package, then rotate any secrets the build/runtime could reach.
npm uninstall bpm-renovate-renovate-config

What this malware does

On require, index.js loads setup.js which downloads a platform-specific binary over HTTPS from one of four string-concatenation-obfuscated .workers.dev hosts (oob-worker.cf100-416.workers.dev, cf101-adf.workers.dev, cf102-baf.workers.dev, cf99-9b3.workers.dev), with a DNS-TXT-record base64 fallback channel via subdomains of dl.wel1.ru. The fetched payload is written to /tmp or %TEMP% under decoy names (e.g. dotnet_diag_.exe,.cache_*), chmod 0755 on Unix, and spawned detached via /bin/sh -c or cmd.exe. Hostnames are constructed by joining short substrings at runtime to evade static URL scanning. A companion module lib/telemetry.js contains the same fetch-decode-chmod-spawn pattern using property-name concatenation (fs['chmod'+'Sync'], require('child_'+'process')) and base64 buffer construction. This is a supply-chain dropper delivering arbitrary attacker-controlled native code to any host that installs or requires the package.

Malicious versions

1 flagged
35.9.2

Indicators of compromise (SHA-256)

3b2fc5b92d1c0023e38459ab9285d928b6fbe3124bfda9d4d6b055dd1fe0bf4e

Detection & response playbook

Malicious package

  1. Find it

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

  2. If you installed it — respond

    Remove bpm-renovate-renovate-config 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.

  3. Did it already run?

    If bpm-renovate-renovate-config 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.

  4. How O3 protects you

    O3 blocks bpm-renovate-renovate-config 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-renovate-renovate-config on npm has been identified as a malicious package (version 35.9.2 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

IN-MAL-2026-015251

References

Credits

  • Amazon Inspector · finder

Detect & block this

O3 blocks bpm-renovate-renovate-config-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
bpm-renovate-renovate-config (npm) malicious package — MAL-2026-12517 | O3 Security