Skip to content

fix: pin axios to 1.14.0 — supply chain attack mitigation#879

Open
paulonasc wants to merge 2 commits intoapify:masterfrom
paulonasc:fix/pin-axios-supply-chain-attack
Open

fix: pin axios to 1.14.0 — supply chain attack mitigation#879
paulonasc wants to merge 2 commits intoapify:masterfrom
paulonasc:fix/pin-axios-supply-chain-attack

Conversation

@paulonasc
Copy link
Copy Markdown

Summary

  • Pins axios direct dependency from ^1.6.7 to exact 1.14.0

Context

axios@1.14.1 and axios@0.30.4 were compromised with a malicious dependency (plain-crypto-js@4.2.1) that deploys a Remote Access Trojan (RAT) via a postinstall hook. The RAT targets macOS, Linux, and Windows and phones home to a C2 server.

Anyone running npm install with apify-client currently resolves axios@^1.6.7 to the compromised 1.14.1.

Advisory: https://www.aikido.dev/blog/axios-npm-compromised-maintainer-hijacked-rat

Changes

  • package.json: pin axios to exact 1.14.0

axios 1.14.1 and 0.30.4 were compromised with a malicious dependency
(plain-crypto-js@4.2.1) that deploys a RAT via postinstall hook.

This pins the direct dependency to 1.14.0 to prevent npm from resolving
to the compromised versions.

Advisory: https://www.aikido.dev/blog/axios-npm-compromised-maintainer-hijacked-rat
Regenerated lockfile so npm ci installs the pinned safe version
deterministically. Without this, the lockfile still resolved to
a different axios version, making the package.json pin ineffective
in CI pipelines.
@B4nan
Copy link
Copy Markdown
Member

B4nan commented Mar 31, 2026

Anyone running npm install with apify-client currently resolves axios@^1.6.7 to the compromised 1.14.1.

I don't think this is necessary, the vulnerable version is no longer available on NPM.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants