MalwarePublished 30 Sep 2026

test-supply-npm-lib-4 (npm) · Malicious Code

Affects test-supply-npm-lib-4Source GCVE Database

Malicious package : remove test-supply-npm-lib-4 and rotate any secrets on hosts that installed it.

Data as of 30 Sep 2026, 16:38 UTC

Classification

Malicious package

Published to npm · OSV MAL-2026-17314

What to do

Remove test-supply-npm-lib-4 from every project, lockfile and image that pulls it in. Treat any host that installed it as compromised: rotate the credentials, tokens and keys it could read, from a clean machine.

Affected software

Product	Affected	Fixed in
npmtest-supply-npm-lib-4	Affected 3.3.3 – 3.3.6 4 affected builds	Fixed in–

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

Description

The test-supply-npm-lib-4 package declares a dependency via a git URL pointing to a GitHub repository controlled by an individual account rather than the official npm registry. This dependency includes lifecycle scripts, such as a prepare hook, that run automatically during npm install. Because the code is fetched directly from GitHub and not vetted through the npm registry, it poses a risk of executing malicious code on the installer's machine.

Impact

If an attacker controls the referenced GitHub repository, they can execute arbitrary code on any machine that installs the test-supply-npm-lib-4 package, leading to potential compromise of the installer's system. This risk arises because the dependency is not vetted by the npm registry and lifecycle scripts run automatically during installation.

Defensive guidance

Users should avoid installing packages that declare dependencies via git URLs from untrusted sources, especially those that run lifecycle scripts. Prefer dependencies sourced from the official npm registry where packages undergo integrity checks. Review package.json dependencies carefully to ensure they do not reference untrusted git repositories.

Summary

The test-supply-npm-lib-4 npm package depends on a git URL-sourced package from a GitHub repository (agustedone/test-supply-npm-git-prepare-proof-4.git) pinned to a specific commit. This dependency is not retrieved from the npm registry and thus bypasses npm's integrity checks and review processes. During installation, npm clones the repository and executes lifecycle scripts, including a prepare hook, which can run arbitrary code controlled by whoever manages the GitHub repository. This creates a supply chain risk where malicious code can execute on the installer's environment.

References

Community reviews

Loading reviews…

What to do

Affected software

Description

AI analysisMachine-generated, updated 30 Sep 2026, 16:38 UTC

Technical details

References

Community reviews