axios-timed (npm) · Malicious Code
Affects axios-timedSource GCVE Database
Malicious package : remove axios-timed and rotate any secrets on hosts that installed it.
Data as of 20 Nov 2026, 01:16 UTC
Malicious package
Published to npm · OSV MAL-2025-191068
What to do
Remove axios-timed 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 |
|---|---|---|
| npmaxios-timed | 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 axios-timed versions 1.0.1 and 1.0.2 were compromised by a malicious actor known as Sha1-Hulud: The Second Coming NPM worm. The malicious code 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 must be rotated from a different machine.
References
- github.com/advisories/GHSA-gcjx-8xwp-g5r4 (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)