The Axios npm package maintainer revealed that the project was compromised through a sophisticated social engineering campaign led by North Korean threat actors known as UNC1069. By impersonating a legitimate company founder and deploying malware during a fraudulent video call, the attackers gained the credentials necessary to publish malicious versions of the highly popular library.
The breach began when maintainer Jason Saayman was targeted with a highly personalized deception involving a cloned corporate identity and a functional Slack workspace designed to look authentic. The attackers eventually lured him into a Microsoft Teams meeting where a fabricated error message prompted him to run a malicious update. This action installed a remote access trojan on his system, allowing the threat actors to seize his credentials and inject an implant named WAVESHAPER.V2 into two versions of the Axios package.
Industry experts have noted that this attack marks a concerning shift in tactics for North Korean groups, who historically focused on cryptocurrency founders and venture capitalists but are now targeting open source software maintainers. This specific campaign, previously tracked by researchers under names like GhostCall, leverages professional-grade coordination to gain trust before delivering a technical payload. The focus on a package like Axios is particularly strategic because its massive user base allows a single compromise to propagate through millions of downstream dependencies.
In the wake of the incident, Saayman has implemented several security upgrades to prevent future compromises, such as moving to an OIDC flow for publishing and establishing immutable releases. These measures are designed to remove single points of failure like static credentials that can be harvested via local malware. The event serves as a stark reminder of the vulnerability inherent in modern software supply chains, where the security of a popular library often rests on the personal devices of its individual maintainers.
The broader security community views this as a demonstration of the extreme difficulty in managing risk within the JavaScript ecosystem. Because Axios is downloaded nearly 100 million times weekly, a poisoned version can infiltrate corporate environments and private systems almost instantly. Security analysts emphasize that as threat actors continue to professionalize their social engineering, the burden on open source maintainers to defend against state-sponsored activity has become an increasingly unsustainable challenge.
Source: https://socket.dev/blog/hidden-blast-radius-of-the-axios-compromise#Why-the-Blast-Radius-Is-Larger-Than-It-Looks