exact-ticker (npm) · Malicious Code
Affects exact-tickerSource GCVE Database
Malicious package : remove exact-ticker and rotate any secrets on hosts that installed it.
Data as of 18 Nov 2026, 02:11 UTC
Malicious package
Published to npm · OSV MAL-2025-190697
What to do
Remove exact-ticker 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 |
|---|---|---|
| npmexact-ticker | 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 exact-ticker version 0.3.5 was found to contain malicious code associated with 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 GitHub actions. It may also destroy the user's home directory. Any system with this package installed should be considered fully compromised, and all secrets and keys should be rotated from a separate, clean system.
References
- github.com/advisories/GHSA-2694-2hhp-543w (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)