depcruise-wrap-stream-in-html@99.9.1

AI Security Review

scanned 2h ago · by lpm-firewall-ai

The package has no own executable behavior, but npm installation fetches a dependency tarball from an external URL. That tarball is not present for inspection and could supply install-time code.

Static reason

One or more suspicious static signals were detected.

Trigger

npm installation resolves dependencies

Impact

Unreviewed third-party tarball may introduce code at dependency-install time.

Mechanism

Remote tarball dependency acquisition

Rationale

The direct remote tarball is a concrete unresolved supply-chain risk, while the inspected package code itself is inert. Source inspection supports a warning rather than a malicious block.

Evidence

package.jsonindex.js

Network endpoints1

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

OSV Corroboration

OpenSSF/OSV

Advisory

MAL-2026-14068

Source

OpenSSF Malicious Packages via OSV

Summary

Malicious code in depcruise-wrap-stream-in-html (npm)

Details

depcruise-wrap-stream-in-html@99.9.1 is a hollow package: index.js is `module.exports = {}` and the name mimics an internal helper of dependency-cruiser. Its only effect on install is resolving a runtime dependency `ltidisafe` from an arbitrary HTTPS tarball URL — `https://ltidi.storage.googleapis.com/depenconf/ltidisafe-3.7.5.tgz` — hosted on a Google Cloud Storage bucket unrelated to any known publisher of dependency-cruiser. On `npm install`, npm downloads and installs that tarball into node_modules, and any lifecycle scripts inside it execute on the installer's machine. The bucket owner can swap the tarball contents at any time without republishing to npm, bypassing registry scanning and version pinning guarantees. The 99.9.1 version number and lookalike name are consistent with a dependency-confusion / smuggling lure.

depcruise-wrap-stream-in-html@99.9.1

AI Security Review

OSV Corroboration

Decision evidence

Source & flagged code

Source & flagged code

Findings

Source & flagged code