registry / knip-bun / 99.9.1

knip-bun@99.9.1

AI Security Review

scanned 2d ago · by lpm-firewall-ai

No malicious behavior is present in package-owned source. Installing it fetches an unverified remote-tarball dependency.

Static reason

One or more suspicious static signals were detected.

Trigger

npm installation resolves dependencies.

Impact

The fetched dependency could introduce uninspected install or runtime behavior.

Mechanism

remote tarball dependency retrieval

Rationale

Package-owned source is benign, but the uninspectable remote dependency creates a concrete unresolved supply-chain risk.

Evidence

package.jsonindex.js

Network endpoints1

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

OSV Corroboration

OpenSSF/OSV

Advisory

MAL-2026-13983

Source

OpenSSF Malicious Packages via OSV

Summary

Malicious code in knip-bun (npm)

Details

Package `knip-bun` typosquats the popular `knip` linter. The main module is an empty stub (`module.exports = {}`), and `package.json` declares a dependency `ltidisafe` pinned to an arbitrary Google Cloud Storage URL (`https://ltidi.storage.googleapis.com/depenconf/ltidisafe-3.6.8.tgz`) rather than a package on the npm registry. On `npm install`, npm downloads and installs the tarball from that bucket into the installer's dependency tree and runs whatever install/lifecycle logic it contains. The bucket is unaffiliated with the knip or bun projects, and the fetched tarball is fully controlled by whoever owns that GCS bucket.

References

OSV advisory PACKAGE

Decision evidence

public snapshot

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

Evidence for block

package.json pins ltidisafe to a remote tarball rather than a registry version.
The remote dependency is not included in this extracted package, so its install-time contents cannot be verified here.

Evidence against

No preinstall, install, postinstall, or prepare lifecycle hook is declared.
The sole entrypoint exports an empty object and contains no runtime behavior.
No package-owned code performs network, shell, file, credential, or agent-control actions.

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": "knip-bun",

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

11 },

High

Ai Review Evidence

package.json pins ltidisafe to a remote tarball rather than a registry version.

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

High

Ai Review Evidence

package.json pins ltidisafe to a remote tarball rather than a registry version.

package.jsonView on unpkg · L9

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

HighAi Review Evidencepackage.json

MediumRemote Tarball Dependencypackage.json

LowScripts Present