Skip to content

πŸ”’ Security: Pin axios to 1.8.2 β€” active supply chain attack on 1.14.1#1

Open
nodefather wants to merge 1 commit intomycosoft:masterfrom
nodefather:security/pin-axios-version
Open

πŸ”’ Security: Pin axios to 1.8.2 β€” active supply chain attack on 1.14.1#1
nodefather wants to merge 1 commit intomycosoft:masterfrom
nodefather:security/pin-axios-version

Conversation

@nodefather
Copy link
Copy Markdown

What

Pins axios to exact version 1.8.2 (removes ^ semver range) to prevent resolution to the compromised axios@1.14.1.

Why

There is an active supply chain attack on axios. Version 1.14.1 was published with a malicious dependency plain-crypto-js@4.2.1 β€” a package that did not exist before today. An attacker took over an axios maintainer account and pushed this compromised version.

The malicious package is an obfuscated dropper that:

  • Dynamically loads fs, os, and execSync to evade static analysis
  • Executes decoded shell commands
  • Stages payloads into OS temp directories
  • Destroys forensic evidence post-execution

⚠️ Extra Risk: No Lockfile

This repo has no package-lock.json committed. That means any npm install would resolve to the latest matching version β€” which right now is the compromised 1.14.1.

After merging this PR, please also:

  1. Run npm install locally (the pinned version is safe)
  2. Commit the generated package-lock.json

References

Action

  • Use npm ci (not npm install) until this is resolved upstream
  • Do not upgrade axios until a clean version is confirmed
  • Generate and commit a package-lock.json for this repo
  • Merge this PR immediately

CRITICAL: axios@1.14.1 has been compromised with a malicious dependency
(plain-crypto-js@4.2.1) via maintainer account takeover.

This pins axios to the known-safe version 1.8.2 to prevent
accidental resolution to the compromised release.

NOTE: This repo has no package-lock.json committed, making it
especially vulnerable. A lockfile should be generated and committed.

Reference: https://github.com/axios/axios/issues/10590
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.

1 participant