test-supply-npm-lib-4npm
test-supply-npm-lib-4 is a confirmed malicious npm package (MAL-2026-17314) that executes malicious code on install (malicious versions 3.3.3, 3.3.4). Do not install it — remove it immediately and rotate any exposed credentials.
Malicious code in test-supply-npm-lib-4 (npm)
What this malware does
package.json declares a dependency test-supply-npm-git-prepare-proof-4 whose value is a bare git URL (git+https://[email protected]/agustedone/test-supply-npm-git-prepare-proof-4.git) rather than a registry version range. On npm install, npm clones that repository at mutable HEAD and runs any lifecycle scripts (preinstall/install/postinstall/prepare) it contains, with no version pin, no commit SHA, and no integrity check. Whoever controls the referenced GitHub repository controls code that executes on the installer's machine at install time. The shipped package body is otherwise an inert stub — the manifest line itself is the delivery mechanism.
Malicious versions
Indicators of compromise (SHA-256)
Detection & response playbook
Malicious packageFind it
Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for test-supply-npm-lib-4 (2 malicious versions). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging test-supply-npm-lib-4 across your stack and pipelines.
If you installed it — respond
Remove test-supply-npm-lib-4 from your project and lockfile, then assume any secrets accessible to the build or runtime were exposed: rotate API keys, tokens, and credentials, and audit for unexpected outbound activity or persistence.
Did it already run?
If test-supply-npm-lib-4 was ever installed, its post-install/runtime payload may have already executed. O3's L7 egress monitoring and runtime eBPF sensors detect the credential exfiltration or command-and-control callback after install and block the malicious outbound channel, so you catch and contain the actual compromise — not just the presence of the package.
How O3 protects you
O3 blocks test-supply-npm-lib-4 before install through its supply-chain scanner, and if it has already run, detects and severs the exfiltration or C2 callback at runtime through L7 egress monitoring and eBPF.
Frequently asked questions
Campaign
References
Credits
- Amazon Inspector · finder
Detect & block this
O3 blocks test-supply-npm-lib-4-class packages before install and in CI — and if it already ran, its runtime egress monitoring catches the malicious outbound activity and severs the channel.