template-lib (npm) · Malicious Code
Affects template-libSource GCVE Database
Malicious package : remove template-lib and rotate any secrets on hosts that installed it.
Data as of 18 Nov 2026, 02:22 UTC
Malicious package
Published to npm · OSV MAL-2025-191021
What to do
Remove template-lib 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 |
|---|---|---|
| npmtemplate-lib | Affected
| Fixed in– |
Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.
Description
The npm package template-lib versions 1.1.3 and 1.1.4 were found to contain malicious code introduced by the Sha1-Hulud: The Second Coming NPM worm. This malware steals tokens and credentials, publishes them to GitHub, propagates itself to other NPM packages owned by the user, and establishes persistence via a GitHub action. It may also destroy the user's home directory. Systems with this package installed should be considered fully compromised.
References
- github.com/advisories/GHSA-96m7-j7g9-h9mr (opens in a new tab)
- aikido.dev/blog/shai-hulud-strikes-again-hitting-zapier-ensdomains (opens in a new tab)
- wiz.io/blog/shai-hulud-2-0-ongoing-supply-chain-attack (opens in a new tab)
- stepsecurity.io/blog/sha1-hulud-the-second-coming-zapier-ens-domains-and-other-prominent-npm-packages-compromised (opens in a new tab)