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

renovate-config-doctolibnpm

renovate-config-doctolib is a confirmed malicious npm package (MAL-2026-2830) that steals credentials and exfiltrates sensitive data. Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in renovate-config-doctolib (npm)

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

What this malware does

Malicious package due to data exfiltration via preinstall script, reading .npmrc, and sending data to a remote server. Few published versions.

The package renovate-config-doctolib was found to contain malicious code.

Any computer that has this package installed or running should be considered fully compromised. All secrets and keys stored on that computer should be rotated immediately from a different computer. The package should be removed, but as full control of the computer may have been given to an outside entity, there is no guarantee that removing the package will remove all malicious software resulting from installing it.

Malicious versions

all versions

Every published version of this package is considered malicious — remove it entirely.

Indicators of compromise (SHA-256)

afc7e33b7c6ea9379f973a56f94e3b8ed59f0bc746733efa7dadba31141d0cd9
007005a8c4578207894ef5641fd2d83d20b74bd02445181de143d49610969ea2

Detection & response playbook

Credential / info stealer
  1. Find it

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

  2. If you installed it — respond

    renovate-config-doctolib is built to steal secrets, so assume every credential the build or runtime could read is compromised. Remove it from your project and lockfile, then rotate ALL exposed secrets — npm/registry tokens, cloud keys, CI/CD secrets, SSH keys, and any .env values — from a known-clean machine. Audit logs for unauthorized use of those credentials.

  3. Did it already run?

    If renovate-config-doctolib 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 renovate-config-doctolib 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. renovate-config-doctolib on npm has been identified as a malicious package (all published versions flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

GHSA-8327-2h3c-rm8g

References

Credits

  • Amazon Inspector · finder
  • SafeDep · finder

Detect & block this

O3 blocks renovate-config-doctolib-class packages before install and in CI — and if it already ran, its runtime egress monitoring catches the credential exfiltration and severs the channel.

Explore

renovate-config-doctolib (npm) malicious package — MAL-2026-2830 | O3 Security