Which versions of litespeed-cache are malicious?

The following npm versions of litespeed-cache are flagged malicious: 1.0.0, 1.1.1, 1.1.2. Treat any of these as compromised.

How do I remediate litespeed-cache if I installed it?

litespeed-cache establishes remote access, so treat any host that installed it as fully compromised. Isolate the machine, remove the package, rotate all credentials it could reach, and rebuild from a trusted image rather than cleaning in place — a backdoor may have planted additional persistence.

I already installed litespeed-cache — how do I know if it already compromised me?

If litespeed-cache 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 litespeed-cache part of a known attack campaign?

Yes — litespeed-cache is associated with the GHSA-vxgg-x9mm-892p, IN-MAL-2026-011241, IN-MAL-2026-013198, IN-MAL-2026-013194 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 litespeed-cache 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 litespeed-cache (3 malicious versions). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging litespeed-cache across your stack and pipelines.

Malicious package

litespeed-cachenpm

litespeed-cache is a confirmed malicious npm package (MAL-2026-11193) that opens a backdoor for remote access (malicious versions 1.0.0, 1.1.1, 1.1.2). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in litespeed-cache (npm)

MAL-2026-11193

Immediate action

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

npm uninstall litespeed-cache

What this malware does

This npm package (a name resemblance to the WordPress LiteSpeed Cache plugin, which is not an npm module) ships a preinstall script and a top-level index.js that both collect os.hostname() and os.userInfo().username and issue an HTTPS request to a hardcoded webhook.site endpoint (https://webhook.site/c72c8172-a424-4a19-91b4-28f40cae3c83). The beacon fires automatically on npm install via the preinstall lifecycle hook, and is repeated at module load so that any consumer that require()s or imports the package also transmits host identifiers, bypassing --ignore-scripts. webhook.site is an anonymous third-party request-inspection collector; there is no functional package behavior beyond the beacon.

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

3 flagged

1.0.01.1.11.1.2

Indicators of compromise (SHA-256)

30b539f8867796f9cc7c4d94a80524212c3873c85d15c5294d4bb144d2c1b177

6f3af61c30e0a85b26bb59e521eb02a26c0b7071446d99d03cdf6b07f790b1f8

5b6b6bed16c1254cb34cd26300a78da4e8bfe074f1fea9e6dd61df60713ac09d

5a641538fc2c01413851b80004408e7ef2187bbe0663b503ae29e26a24d3aff5

Detection & response playbook

Backdoor / remote access

Find it
Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for litespeed-cache (3 malicious versions). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging litespeed-cache across your stack and pipelines.
If you installed it — respond
litespeed-cache establishes remote access, so treat any host that installed it as fully compromised. Isolate the machine, remove the package, rotate all credentials it could reach, and rebuild from a trusted image rather than cleaning in place — a backdoor may have planted additional persistence.
Did it already run?
If litespeed-cache 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 litespeed-cache 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. litespeed-cache on npm has been identified as a malicious package (versions 1.0.0, 1.1.1, 1.1.2 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

GHSA-vxgg-x9mm-892pIN-MAL-2026-011241IN-MAL-2026-013198IN-MAL-2026-013194

References

Credits

Amazon Inspector · finder

Detect & block this

O3 blocks litespeed-cache-class packages before install and in CI — and if it already ran, its runtime egress monitoring catches the C2 callback and severs the channel.

Malware detection Runtime egress monitoring

Explore

All malware advisories How O3 detects malware Vulnerability database