litespeed-cache
This report shows the evidence for litespeed-cache@1.1.2. 3 of 3 known versions are blocked or flagged. See all versions.
OpenSSF/OSV Malicious Advisory
imported 3mo ago · by OpenSSF/OSVOpenSSF/OSV advisory MAL-2026-11193 confirms this npm version as malicious.
Advisory
MAL-2026-11193
Source
OpenSSF Malicious Packages via OSV
Summary
Malicious code in litespeed-cache (npm)
Details
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.
## Source: ghsa-malware (30b539f8867796f9cc7c4d94a80524212c3873c85d15c5294d4bb144d2c1b177) 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.
References
Source & flagged code
0 flagged · loading sourceNo flagged code excerpts are attached to this scan.
Findings
1 High
HighOsv Malicious Advisory
Affected versions and remediation
This report applies to litespeed-cache@1.1.2.
The same advisory and Firewall decision cover 3 recorded versions
1.1.2, 1.0.0, 1.1.1
The versions list below shows the verdict for each recorded version.
- Avoid installing litespeed-cache@1.1.2. Remove it from direct dependencies and check your lockfile for transitive copies.
- Choose an independently verified alternative or release. This report does not establish that other versions are safe.
- If this version ran, investigate the affected machine and build environment. Rotate credentials it could access and rebuild from a trusted environment.
Evidence last updated: .
Source advisory published: .
This report uses published external intelligence. The advisory does not provide a separate source-code analysis for each listed version.
Think this verdict is wrong? Dispute it on GitHub or read how reports are produced.