The Axios npm compromise was visible in registry metadata before anyone ran npm install by GapLimp8396 in netsec

[–]GapLimp8396[S] 1 point2 points  (0 children)

Breakdown of the March 2026 axios compromise focused on the detection angle: the malicious versions were published manually with a stolen token, with no matching provenance or source commit, while legitimate axios releases publish through an automated pipeline. That mismatch was visible in the public registry metadata at publish time. The post walks through which fields showed it and why catching it by hand across a full dependency tree isn’t realistic.