registry / resolve-audit / 99.9.1

resolve-audit@99.9.1

AI Security Review

scanned 2d ago · by lpm-firewall-ai

npm installation fetches an opaque remote dependency tarball. The package source itself contains no confirmed active attack behavior.

Static reason

One or more suspicious static signals were detected.

Trigger

npm install of resolve-audit

Impact

Remote dependency content is outside this package source and could change the installed dependency payload.

Mechanism

remote tarball dependency resolution

Rationale

The package is inert at runtime, but its remote tarball dependency creates a meaningful unresolved supply-chain payload risk. This warrants a warning rather than a block because no concrete malicious behavior is present in inspected source.

Evidence

package.jsonindex.js

Network endpoints1

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

OSV Corroboration

OpenSSF/OSV

Advisory

MAL-2026-13987

Source

OpenSSF Malicious Packages via OSV

Summary

Malicious code in resolve-audit (npm)

Details

resolve-audit@99.9.1 is a stub package (index exports an empty object) whose package.json declares its only dependency `ltidisafe` as a direct HTTPS tarball URL: https://ltidi.storage.googleapis.com/depenconf/ltidisafe-3.6.6.tgz. On `npm install`, npm fetches this arbitrary tarball from an anonymous, mutable Google Cloud Storage bucket (path segment `depenconf`, a dependency-confusion marker) rather than resolving through the npm registry, with no version-by-hash pinning. Any lifecycle scripts inside that tarball execute on the installer. The version number 99.9.1 is characteristic of dependency-confusion/version-squat lures designed to win resolution against a private-registry package of the same name.

References

OSV advisory PACKAGE

Decision evidence

public snapshot

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

Evidence for block

package.json pins dependency ltidisafe to a remote Google Cloud Storage tarball under a depenconf path.

Evidence against

No preinstall, install, or postinstall lifecycle scripts are declared.
index.js only exports an empty object; no runtime behavior is present.
No credential access, shell execution, file writes, or network calls appear in package source.

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": "resolve-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.6.tgz"

11 },

High

Suspicious Dependency Evidence

package.json pins dependency ltidisafe to a remote Google Cloud Storage tarball under a depenconf path.

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.6.tgz" }

High

Suspicious Dependency Evidence

package.json pins dependency ltidisafe to a remote Google Cloud Storage tarball under a depenconf path.

package.jsonView on unpkg · L9

•Remote tarball dependency specs: ltidisafe@https://ltidi.storage.googleapis.com/depenconf/ltidisafe-3.6.6.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