UNC1069 Social Engineering of Axios Maintainer Led to npm Supply Chain Attack
04.04.2026
5417

UNC1069 compromised Axios 1.14.1 and 0.30.4 via social engineering, impacting 100M weekly downloads and exposing supply chains.
UNC1069 Social Engineering of Axios Maintainer Led to npm Supply Chain Attack
Hold up, devs. UNC1069 just pulled off a slick social engineering hack on an Axios maintainer, compromising versions 1.14.1 and 0.30.4. This isn't just another npm drama—it's a full-blown supply chain attack hitting a library with 100M weekly downloads. The threat actor, linked to North Korea, used clever social engineering to gain access and push malicious updates. If you're using Axios, check your versions NOW.

The attack vector? Pure social engineering. UNC1069, a North Korean threat actor, manipulated the maintainer into granting access, then pushed tainted updates to npm. This isn't just about stealing credentials—it's about embedding malware into one of the most widely used JavaScript libraries globally. The compromised versions were live for hours before detection, meaning countless projects could be affected.
- • Threat Actor: UNC1069 (North Korea-linked)
- • Target: Axios maintainer
- • Compromised Versions: 1.14.1 and 0.30.4
- • Impact: 100M+ weekly downloads
- • Attack Method: Social engineering to gain npm access
- • Risk: Supply chain malware injection
- • Tags: Credential Theft, Malware, Open Source, NPM
This incident screams the fragility of open-source ecosystems. A single maintainer's credentials can bring down millions of dependencies. UNC1069's move shows how threat actors are shifting from direct attacks to exploiting trust in maintainer communities. If you haven't updated your dependency management and security protocols, now's the time—because the next attack might not be so easy to spot.
UNC1069 compromised Axios 1.14.1 and 0.30.4 via social engineering, impacting 100M weekly downloads and exposing supply chains.
#npm#supply chain attacks#malware#Open Source#social engineering
Got a topic? Write to ATLA WIRE on Telegram:t.me/atla_community

