cspell-esm
This report shows the evidence for cspell-esm@99.9.1. 1 of 2 known versions is blocked or flagged. The newest version, 0.0.1-security, is allowed. See all versions.
This package appears in our research on the dependency confusion probes at version 99 and above, with how it works, the full package list and what to do if you installed it.
OpenSSF/OSV Malicious Advisory
imported 2mo ago · by OpenSSF/OSVOpenSSF/OSV advisory MAL-2026-13977 confirms this npm version as malicious.
Independent LPM AI assessment
CleanIndependent AI assessment: clean. LPM AI assessed this version as clean; the assessments disagree.
Direct inspection found no lifecycle execution or runtime capability beyond an empty export. The remote dependency URL is a supply-chain concern but is not proof that this package is malicious.
Independent scan evidence
public snapshot- package.json pins its only dependency to a remote Google Cloud Storage tarball, creating an external supply-chain dependency.
- No preinstall, install, or postinstall lifecycle hook is declared.
- The sole runtime entrypoint exports an empty object and contains no execution, file, network, or child-process behavior.
- No concrete malicious behavior is present in the inspected package source.
Source & flagged code
2 flagged · loading sourcepackage.json pins its only dependency to a remote Google Cloud Storage tarball, creating an external supply-chain dependency.
package.jsonView on unpkg · L9Package manifest contains a dependency pinned to a remote tarball URL.
package.jsonView on unpkgFindings
Affected versions and remediation
This report applies to cspell-esm@99.9.1.
The versions list below shows the verdict for each recorded version.
- Avoid installing cspell-esm@99.9.1. 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: .
Think this verdict is wrong? Dispute it on GitHub or read how reports are produced.