⚠️ Security Alert: Axios supply chain attack via npm

[SamTerces]

Discussion Type

Bug

Discussion Content

There is an active supply chain compromise affecting Axios on npm.

Compromised versions:
axios@1.14.1
axios@0.30.4

These versions included a malicious dependency: “plain-crypto-js”
This dependency executes during npm install and can install a remote access payload.

What to do immediately:

Check your installed axios versions:
npm list axios

Search for malicious dependency:
find . -name "plain-crypto-js"

If found:

      - Remove immediately
      - Rotate ALL credentials (API keys, tokens, SSH)
      - Consider system cleanup/reinstall

Safe versions:

      1.   1. 1.14.0 and below
      2.   2. 0.30.3 and below

Important:

      1. This attack uses npm install scripts - meaning your CI/CD pipelines are also at risk.
      2. Do NOT blindly run installs without reviewing lockfiles.
      3. If you installed dependencies in the last ~24 hours, double check.

Stay safe.

[github-actions[bot]]

💬 Your Product Feedback Has Been Submitted 🎉

Thank you for taking the time to share your insights with us! Your feedback is invaluable as we build a better GitHub experience for all our users.

Here's what you can expect moving forward ⏩

• Your input will be carefully reviewed and cataloged by members of our product teams. 
  • Due to the high volume of submissions, we may not always be able to provide individual responses.
  • Rest assured, your feedback will help chart our course for product improvements.
• Other users may engage with your post, sharing their own perspectives or experiences. 
• GitHub staff may reach out for further clarification or insight. 
  • We may 'Answer' your discussion if there is a current solution, workaround, or roadmap/changelog post related to the feedback.

Where to look to see what's shipping 👀

• Read the Changelog for real-time updates on the latest GitHub features, enhancements, and calls for feedback.
• Explore our Product Roadmap, which details upcoming major releases and initiatives.

What you can do in the meantime 💻

• Upvote and comment on other user feedback Discussions that resonate with you.
• Add more information at any point! Useful details include: use cases, relevant labels, desired outcomes, and any accompanying screenshots.

As a member of the GitHub community, your participation is essential. While we can't promise that every suggestion will be implemented, we want to emphasize that your feedback is instrumental in guiding our decisions and priorities.

Thank you once again for your contribution to making GitHub even better! We're grateful for your ongoing support and collaboration in shaping the future of our platform. ⭐

[syedsafeer]

Thanks for the detailed alert @SamTerces! This is a major supply chain risk for the community.
One extra precaution: After removing the malicious package, users should also run npm cache clean --force before reinstalling the safe versions. This ensures that no malicious artifacts stay in the local npm cache to infect future projects.