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

@liquid-web/interceptorsnpm

@liquid-web/interceptors is a confirmed malicious npm package (MAL-2025-47036) that executes malicious code on install (malicious version 1.2.9213). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in @liquid-web/interceptors (npm)

MAL-2025-47036
Immediate action
Remove the package, then rotate any secrets the build/runtime could reach.
npm uninstall @liquid-web/interceptors

What this malware does

The package @liquid-web/interceptors 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

1 flagged
1.2.9213

Indicators of compromise (SHA-256)

ab7a1c47c538682d6263db28f68b16539bd0b759d77d715766652c07ad79c1b4
409397242739860e2baf9e9447dee837bc71c7808d7bc46b6642d35711145481
13aa4341b1482a8edfacd339069aa07df75c3b133a7ddd49bc503ec4d1947461
016db66622597ab91ecdaf6b100cf178074844610346ba138946769dadfe349e

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

  2. If you installed it — respond

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

Campaign

GHSA-gvxf-92hq-769cRLMA-2025-04844RLUA-2026-01029

References

Credits

  • Amazon Inspector · finder
  • ReversingLabs · finder

Detect & block this

O3 blocks @liquid-web/interceptors-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.

Explore

@liquid-web/interceptors (npm) malicious package — MAL-2025-47036 | O3 Security