BTC $64,889.88 +0.87%
ETH $1,819.76 +0.89%
BNB $591.94 +0.81%
XRP $0.9742 +2.63%
SOL $73.84 +3.92%
TRX $0.3062 +0.77%
DOGE $0.0593 +1.59%
ADA $0.1543 +1.89%
BCH $212.61 +3.71%
LINK $9.31 +2.37%
HYPE $69.48 +6.14%
AAVE $112.93 +4.67%
SUI $0.7362 +3.27%
XLM $0.1403 +2.69%
ZEC $947.38 +9.49%
AAPL $352.15 -1.69%
AMZN $258.95 -1.82%
GOOGL $282.58 -3.93%
MSFT $515.78 -1.85%
META $620.90 -2.86%
NVDA $157.75 +0.33%
TSLA $381.36 -1.13%
SNDK $818.14 -1.10%
INTC $54.88 -3.04%
SPCX $138.38 -0.01%
MU $728.44 -0.34%
AMD $512.59 +1.98%
BTC $64,889.88 +0.87%
ETH $1,819.76 +0.89%
BNB $591.94 +0.81%
XRP $0.9742 +2.63%
SOL $73.84 +3.92%
TRX $0.3062 +0.77%
DOGE $0.0593 +1.59%
ADA $0.1543 +1.89%
BCH $212.61 +3.71%
LINK $9.31 +2.37%
HYPE $69.48 +6.14%
AAVE $112.93 +4.67%
SUI $0.7362 +3.27%
XLM $0.1403 +2.69%
ZEC $947.38 +9.49%
AAPL $352.15 -1.69%
AMZN $258.95 -1.82%
GOOGL $282.58 -3.93%
MSFT $515.78 -1.85%
META $620.90 -2.86%
NVDA $157.75 +0.33%
TSLA $381.36 -1.13%
SNDK $818.14 -1.10%
INTC $54.88 -3.04%
SPCX $138.38 -0.01%
MU $728.44 -0.34%
AMD $512.59 +1.98%

The Axios library was attacked through a supply chain, with hackers using stolen npm tokens to implant a remote trojan, affecting about 80% of cloud environments

2026-04-02 13:13:59

The attacker stole the npm access token of the chief maintainer of Axios, the most popular HTTP client library for JavaScript, and used that token to publish two malicious versions containing cross-platform remote access trojans (RATs) ([email protected] and [email protected]), targeting macOS, Windows, and Linux systems. The malicious packages were removed from the npm registry about 3 hours after being published.

According to data from security company Wiz, Axios is downloaded over 100 million times weekly and exists in about 80% of cloud and code environments. Security company Huntress detected the first infections just 89 seconds after the malicious packages went live and confirmed that at least 135 systems were compromised during the exposure window. Notably, the Axios project had previously deployed modern security measures such as OIDC trusted publishing mechanisms and SLSA provenance proofs, but the attacker completely bypassed these defenses. Investigations revealed that while configuring OIDC, the project retained the traditional long-lived NPM_TOKEN, and npm defaults to using the traditional token when both coexist, allowing the attacker to publish without breaching OIDC.

ChainCatcher reminds readers to view blockchain rationally, enhance risk awareness, and be cautious of various virtual token issuances and speculations. All content on this site is solely market information or related party opinions, and does not constitute any form of investment advice. If you find sensitive information in the content, please click , and we will handle it promptly.

app_icon
ChainCatcher Building the Web3 world with innovations.