registry / Malware / gunzip-js

gunzip-js

This report shows the evidence for gunzip-js@99.9.1. 1 of 2 known versions is blocked or flagged. The newest version, 0.0.1-security, is allowed. See all versions.

This package appears in our research on the dependency confusion probes at version 99 and above, with how it works, the full package list and what to do if you installed it.

OpenSSF/OSV Malicious Advisory

imported 2mo ago · by OpenSSF/OSV

OpenSSF/OSV advisory MAL-2026-14056 confirms this npm version as malicious.

Advisory

MAL-2026-14056

Source

OpenSSF Malicious Packages via OSV

Summary

Malicious code in gunzip-js (npm)

Details

gunzip-js@99.9.1 is a near-empty npm package (typosquat of the well-known gunzip-maybe / gunzip family) whose package.json declares its sole dependency `ltidisafe` as an HTTPS tarball URL — `https://ltidi.storage.googleapis.com/depenconf/ltidisafe-3.7.2.tgz` — instead of a version resolved from the npm registry. On `npm install`, npm downloads that tarball from the anonymous Google Cloud Storage bucket and installs it into node_modules, executing any lifecycle scripts (preinstall/install/postinstall) and any top-level code reached via require. The GCS bucket is not associated with any known publisher, the path segment `depenconf` mirrors the term dependency-confusion, the version 99.9.1 is the classic high-number squat pattern, and the package's own index.js is empty — the only effect of installing gunzip-js is to pull attacker-controlled code from an unaudited external host into the installer's dependency graph. ## Source: ossf-package-analysis (cb01fea066eb17256cd8a5ef589351ca7c5fda77eaff201237eac8f306b5b53d) The OpenSSF Package Analysis project identified 'gunzip-js' @ 99.9.1 (npm) as malicious. It is considered malicious because: - The package communicates with a domain associated with malicious activity.

References

OpenSSF/OSV advisory PACKAGE

Independent LPM AI assessment

Suspicious

Independent AI assessment: suspicious. LPM AI assessed this version as suspicious; the assessments disagree.

The uninspectable remote dependency is a concrete provenance risk, while the package source contains no direct malicious actions. Warn pending review of the referenced tarball rather than block.

Static reason

One or more suspicious static signals were detected.

Trigger

npm install resolves the declared dependency.

Impact

The externally hosted dependency could change independently of npm registry package provenance; its contents were unavailable for source inspection.

Mechanism

remote tarball dependency retrieval

AI rationale

The uninspectable remote dependency is a concrete provenance risk, while the package source contains no direct malicious actions. Warn pending review of the referenced tarball rather than block.

Evidence

package.jsonindex.js

Network endpoints1

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

Independent scan evidence

public snapshot

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

Evidence for AI warning decision

Manifest pins dependency to an external tarball URL rather than a registry version.

Evidence against

No preinstall, install, or postinstall lifecycle hook is declared.
The sole runtime entrypoint only exports an empty object.
No package source performs network, file, shell, 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

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

High

Suspicious Dependency Evidence

Manifest pins dependency to an external tarball URL rather than a registry version.

package.jsonView on unpkg · L10

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

Medium

Remote Tarball Dependency

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

package.jsonView on unpkg

Source & flagged code

2 flagged · loading source

package.jsonView file

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

High

Suspicious Dependency Evidence

Manifest pins dependency to an external tarball URL rather than a registry version.

package.jsonView on unpkg · L10

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

Affected versions and remediation

This report applies to gunzip-js@99.9.1.

The versions list below shows the verdict for each recorded version.

Avoid installing gunzip-js@99.9.1. Remove it from direct dependencies and check your lockfile for transitive copies.
Choose an independently verified alternative or release. This report does not establish that other versions are safe.
If this version ran, investigate the affected machine and build environment. Rotate credentials it could access and rebuild from a trusted environment.

Evidence last updated: 2026-08-16 09:25:25.314Z (UTC).

Source advisory published: 2026-08-15 15:31:09.000Z (UTC).

Think this verdict is wrong? Dispute it on GitHub or read how reports are produced.

Versions

2 known versions

0.0.1-securitylatestClean—AllowPublishedAug 18, 2026, 4:19 PM 99.9.1shownMaliciousMalwareBlockPublishedAug 15, 2026, 2:27 PM

OpenSSF/OSV Malicious Advisory

Independent LPM AI assessment

Independent scan evidence

Source & flagged code

Source & flagged code

Findings

Affected versions and remediation

Versions

Related packages

Other malware packages

Source & flagged code

Related packages

Other malware packages