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

sanitize-urlnpm

Malicious code in sanitize-url (npm) Remove it immediately and rotate any exposed credentials.

MAL-2026-2701
Immediate action
Remove the package, then rotate any secrets the build/runtime could reach.
npm uninstall sanitize-url

What this malware does

The package sanitize-url was found to contain malicious code.

The OpenSSF Package Analysis project identified 'sanitize-url' @ 8.9.9 (npm) as malicious.

It is considered malicious because:

  • The package communicates with a domain associated with malicious activity.

  • The package executes one or more commands associated with malicious behavior.

Malicious versions

1 flagged
8.9.9

Indicators of compromise (SHA-256)

0614e2498dbee5c3133dc2dff5457f14cd9f7cd1ec54ac26a035f895c396bbfa
36f98260cc1b910a8921671795398ad7f986f02b0b7bc8efef18a4df09b87d51

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 sanitize-url (version 8.9.9). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging sanitize-url across your stack and pipelines.

  2. If you installed it — respond

    Remove sanitize-url 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 sanitize-url 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 sanitize-url 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. sanitize-url on npm has been identified as a malicious package (version 8.9.9 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Credits

  • Amazon Inspector · finder
  • OpenSSF: Package Analysis · finder

Detect & block this

O3 blocks sanitize-url-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.

sanitize-url (npm) malicious package — MAL-2026-2701 | O3 Security