Dev.to AI2h ago|Business & Industry

North Korean Hackers Compromise Axios Maintainer Through Sophisticated Social Engineering

North Korean hackers built a fake company and social profiles to trick the lead maintainer of the popular axios library into installing malware, allowing them to publish malicious versions with a remote access trojan. This attack highlights the vulnerabilities in open-source software security.

đź’ˇ

Why it matters

This attack on the axios library, which has over 100 million weekly downloads, demonstrates the sophisticated tactics used by North Korean hackers to compromise open-source software and the limitations of current security measures.

Key Points

  • 1North Korean hackers created a fake company with a Slack workspace, LinkedIn profiles, and a Teams meeting to gain the trust of the axios maintainer
  • 2They tricked the maintainer into installing a remote access trojan (RAT) during the Teams meeting, giving them full control of his machine
  • 3The hackers used this access to publish malicious versions of axios with a dependency on a trojan package, which was live for 3 hours before being taken down
  • 4This attack exposed gaps in npm's security model that 2-factor authentication could not prevent, as the hackers were able to change the maintainer's email and use a long-lived access token

Details

The attack involved North Korean hackers building a fake company, complete with a Slack workspace, LinkedIn activity, and fake employee profiles, to trick the lead maintainer of the popular axios library into installing malware. After establishing trust through the Slack workspace, the hackers scheduled a Teams meeting where they tricked the maintainer into installing an update that was actually a remote access trojan (RAT). This gave the hackers full control of the maintainer's machine, allowing them to publish malicious versions of axios with a dependency on a trojan package. The malware deployed platform-specific payloads on affected systems, beaconing to a North Korean-linked domain. While the maintainer had 2-factor authentication enabled, this did not stop the attack, as the hackers were able to change his npm email and use a long-lived access token to publish the malicious versions. This highlights the vulnerabilities in open-source software security and the need for more robust measures to protect critical libraries.

Like
Save
Read original
Cached
Comments
?

No comments yet

Be the first to comment

AI Curator - Daily AI News Curation

AI Curator

Your AI news assistant

Ask me anything about AI

I can help you understand AI news, trends, and technologies