A serious supply chain attack has hit Axios, one of the most widely used tools in web development. Security researchers from Socket Security found that hackersA serious supply chain attack has hit Axios, one of the most widely used tools in web development. Security researchers from Socket Security found that hackers

Axios Supply Chain Attack Exposes Crypto Apps to Risk

2026/03/31 15:59
3 min read
For feedback or concerns regarding this content, please contact us at crypto.news@mexc.com

A serious supply chain attack has hit Axios, one of the most widely used tools in web development. Security researchers from Socket Security found that hackers injected malware into specific versions of the library published on npm.

This attack could impact millions of crypto apps. It includes many crypto platforms that rely on Axios to connect with servers. Because Axios is used across so many systems, the risk is wide and immediate. The affected versions include axios@1.14.1 and axios@0.30.4. Developers who installed these versions may have unknowingly exposed their systems.

How the Attack Happened?

The attack did not come from a simple bug. Instead, hackers used a supply chain method. This means they targeted the software distribution process itself. In this case, attackers added a malicious package called “plain-crypto-js@4.2.1” as a hidden dependency. This package was not part of Axios before. Someone inserted it quietly during the release.

Even more concerning, the release did not follow Axios’s normal process. It did not appear in official GitHub tags. This suggests the attacker gained unauthorized access to the publishing system. Reports indicate that a maintainer account may have been compromised. This allowed the attacker to push the infected version directly to npm.

What the Malware Can Do?

The malware is not harmless. It installs a remote access tool, also known as a RAT. Once inside a system, it can run commands, collect data and connect to external servers. It works across macOS, Windows and Linux. The attack is also designed to hide itself. It runs during installation and then removes traces of its activity. This makes it harder to detect. With this, even developers may not realize their system has been affected.

Why Crypto Projects Are at Risk?

Crypto apps often rely on tools like Axios to send and receive data. This includes wallet services, exchanges and decentralized apps. If these apps use the affected versions, attackers could access sensitive data. This may include private keys, API tokens or user information.

Since many projects use automatic updates, some may have installed the compromised version without knowing. This makes the situation more serious. The attack also shows how one weak point can affect many systems at once.

What Developers Should Do Now?

Security experts urge developers to act quickly. First, check all dependencies and lockfiles. Look for the affected Axios versions and the malicious package. If found, remove them immediately. Then, switch to a safe version of Axios.

It is also important to review systems for unusual activity. Security teams must handle any signs of unauthorized access carefully. The npm registry has removed the harmful versions. But the incident is still under investigation. This attack is a clear reminder. Even trusted tools can become targets. In a fast moving space like crypto, staying alert is no longer optional.

The post Axios Supply Chain Attack Exposes Crypto Apps to Risk appeared first on Coinfomania.

Disclaimer: The articles reposted on this site are sourced from public platforms and are provided for informational purposes only. They do not necessarily reflect the views of MEXC. All rights remain with the original authors. If you believe any content infringes on third-party rights, please contact crypto.news@mexc.com for removal. MEXC makes no guarantees regarding the accuracy, completeness, or timeliness of the content and is not responsible for any actions taken based on the information provided. The content does not constitute financial, legal, or other professional advice, nor should it be considered a recommendation or endorsement by MEXC.