Axios under attack by social engineering reveals the fragility of the software supply chain

The development community recently woke up with news that one of the most used libraries in the JavaScript ecosystem was manipulated in the supply chain. The main maintainer of the package Axios, with weekly downloads around the hundreds of millions, he confirmed that his account was compromised after an extremely targeted social engineering campaign. The attack, attributed to North Korean actors identified as UNC1069, was not a random blow: it was a planned operation to gain access to an account with the ability to publish packages and, from there, spread malicious code.

According to the reconstruction of the maintainer himself, the attackers became real figures of a known company, clone both the visual identity and the online presence of the founder to generate confidence. They invited him to a work space in Slack which, in plain sight, seemed legitimate: appearance, channels and even publications emulated true activity. They then held a meeting for Microsoft Teams. During that call, upon entering, a false message appeared indicating that there was an outdated component and that it required an update. In accepting this operation, a remote-access Trojan was executed that gave the attacker control over the machine and, from there, the possibility of stealing the credentials necessary to publish in npm.

With these credentials, the adversaries uploaded two contaminated versions of the Axios package (1.14.1 and 0.30.4), which included an implant known as WAVESHAPER.V2. The result was that thousands of projects, and by extension millions of applications, could be exposed to a malicious code simply by incorporating a widely trusted dependence. This type of incident shows a structural vulnerability: when such a central library in the JavaScript ecosystem is compromised, the impact surface reaches not only direct dependents but also full transitional chains.

The details of the modus operandi coincide with previous research iridescence on UNC1069 and a related group called BlueNoroff, and have similarities to a campaign documented by security firms last year under the name GhostCall. Organizations such as Kaspersky and signature Huntress have been documenting how these actors have directed sophisticated attacks against influential people in cryptomonedas, risk capital and now, more worrisome, towards open source software maintainers.

The case of Axios illustrates that the threat does not always come by the technical exploitation of a server; often the human factor is the weakest link. The attackers invest in recreating a normal appearance: they create spaces for collaboration with appropriate branding, share plausible links and teach interactions that reduce the victim's suspicion. That attention to detail makes something as simple as an invitation to Slack or a call by Teams extremely effective.

In view of this, the affected maintainer has detailed several countermeasures that can help mitigate similar risks: clean and reinstall compromised devices, rotate all credentials, use more robust publishing flows that reduce reliance on persistent credentials and adopt practices in continuous integration actions that limit the ability to publish automatically. Mechanisms such as immutable launches and the use of more modern identity protocols (e.g. OIDC) have also been proposed to sign and authorize publications, making it difficult for an attacker who steals a password to publish packages on behalf of another.

The practical impact is not trivial. In the words of ecosystem researchers, this episode shows how complicated it is to reason about exposure in modern JavaScript projects, where the resolution of dependencies and the huge amount of reusable packages make a single committed piece can cause chain effects. Therefore, beyond the specific corrections, the community and the platforms that support it are required to rethink the confidence processes, account management with publication privileges and tools that protect the integrity of the software that millions of developers and end users use every day.

For those who manage open source projects, learning is clear: safety must be addressed as a continuous operational aspect. Review access policies, minimize the number of devices allowed, use strong multifactor authentication and implement early detection of abnormal behaviors are steps that help reduce the probability and impact of an intrusion. In addition, follow research and analysis of specialized signatures, such as works published by Kaspersky, Huntress or the releases of the package platforms themselves, provides context and practical recommendations to strengthen defenses.

This incident with Axios is not a call to paralyze innovation or to reduce confidence in free software, but to learn collectively: the software supply chain is an attractive goal for its efficiency to scale up damage, and to protect it requires coordination of best technical practices, operational controls and, above all, greater awareness of the social engineering tactics that are now using increasingly professional actors.

If you want to go deeper, the project page in GitHub and the registration of the package in npm are good starting points to check updates. To understand the context of the campaigns attributed to these groups and their techniques, the analysis of research centres and cybersecurity companies as Kaspersky and Huntress provide detailed reports and operational recommendations.