Malicious code in axios (npm)
Compromised versions · axios
- 0.30.4
- 1.14.1
Safe
Every other versionincluding the latest, 1.20.0
npm install axios@1.20.0Not affected
1.0.0 – 1.14.0
60 releases
Affected
1.14.1
1 release
Safe
1.15.0 – 1.20.0
10 releases, latest
Not affected
0.1.0 – 0.30.3
63 releases
Affected
0.30.4
1 release
Safe
0.31.0 – 0.34.0
5 releases
Is your project affected?
Paste your package.json, or type the range you declare for axios. It is read in your browser and sent nowhere.
What happens
If one of these versions was installed
- Treat the machines and CI runners that installed it as compromised.
- Rotate the npm, GitHub and cloud tokens they could reach.
- Reinstall from a lockfile that pins a version outside the list.
-= Per source details. Do not edit below this line.=-
Source: amazon-inspector (503284900929e333b801f9f47419a2b4c21e4022d13a03fc14e4b5390767a51d)
The package axios was found to contain malicious code.
Source: ghsa-malware (bcd851213ecf0f8dc58fe88d79b3d19a59388272b2426097de7edc4c53df5d9e)
Any computer that has this package installed or running should be considered fully compromised. All secrets and keys stored on that computer should be rotated immediately from a different computer. The package should be removed, but as full control of the computer may have been given to an outside entity, there is no guarantee that removing the package will remove all malicious software resulting from installing it.
Source: google-open-source-security (50bbf7104516d22bb93a54feaf5122939b7fe72e943ce7da13ca88cb6c70aacf)
The npm package "axios" was compromised and a malicious dependency was added called "plain-crypto-js". The malicious code appears to install a remote access trojan.