check-audit
This report shows the evidence for check-audit@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-13976 confirms this npm version as malicious.
Independent LPM AI assessment
SuspiciousIndependent AI assessment: suspicious. LPM AI assessed this version as suspicious; the assessments disagree.
The remote dependency is a concrete staged-payload delivery surface, but inspected source does not show local execution or malicious effects. Warn pending dependency-payload inspection.
Independent scan evidence
public snapshot- Manifest pins dependency ltidisafe to a remote tarball URL, so installation fetches code outside the package source.
- No preinstall, install, or postinstall lifecycle hook is declared.
- The sole runtime entrypoint only exports an empty object; no local execution, harvesting, or network logic is present.
Source & flagged code
2 flagged · loading sourceManifest pins dependency ltidisafe to a remote tarball URL, so installation fetches code outside the package source.
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 check-audit@99.9.1.
The versions list below shows the verdict for each recorded version.
- Avoid installing check-audit@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.