π 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
Open
π Security: Pin axios to 1.8.2 β active supply chain attack on 1.14.1#1nodefather wants to merge 1 commit intomycosoft:masterfrom
nodefather wants to merge 1 commit intomycosoft:masterfrom
Conversation
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
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
What
Pins axios to exact version
1.8.2(removes^semver range) to prevent resolution to the compromisedaxios@1.14.1.Why
There is an active supply chain attack on axios. Version
1.14.1was published with a malicious dependencyplain-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:
fs,os, andexecSyncto evade static analysisThis repo has no
package-lock.jsoncommitted. That means anynpm installwould resolve to the latest matching version β which right now is the compromised1.14.1.After merging this PR, please also:
npm installlocally (the pinned version is safe)package-lock.jsonReferences
Action
npm ci(notnpm install) until this is resolved upstreampackage-lock.jsonfor this repo