Customize Consent Preferences

We use cookies to help you navigate efficiently and perform certain functions. You will find detailed information about all cookies under each consent category below.

The cookies that are categorized as "Necessary" are stored on your browser as they are essential for enabling the basic functionalities of the site.... 

Always Active

Necessary cookies are required to enable the basic features of this site, such as providing secure log-in or adjusting your consent preferences. These cookies do not store any personally identifiable data.

Functional cookies help perform certain functionalities like sharing the content of the website on social media platforms, collecting feedback, and other third-party features.

Analytical cookies are used to understand how visitors interact with the website. These cookies help provide information on metrics such as the number of visitors, bounce rate, traffic source, etc.

Performance cookies are used to understand and analyze the key performance indexes of the website which helps in delivering a better user experience for the visitors.

No cookies to display.

Advertisement cookies are used to provide visitors with customized advertisements based on the pages you visited previously and to analyze the effectiveness of the ad campaigns.

No cookies to display.

News Flash

Lazarus strikes again: hacker attack puts millions of developers at risk

A new supply chain attack reveals how vulnerable the developer ecosystem is

Hacker attack puts millions of developers at risk

Table of contents

  • A wave of attacks threatens the NPM ecosystem 
  • How the attack works 
  • Protection strategies against supply chain attacks
  • The future of cyber attacks on the supply chain

A wave of attacks threatens the NPM ecosystem 

The APT Lazarus group, linked to North Korea, has launched a series of targeted attacks on the npm ecosystem, compromising open-source packages used by thousands of developers.

This type of supply chain attack is particularly dangerous as it infiltrates directly into developers’ workflows, allowing attackers to distribute malware through code dependencies. 

How the attack works 

Lazarus exploited developers’ lack of verification of npm packages to insert malicious code into seemingly legitimate libraries. When a developer installs or updates one of these dependencies, the malware activates automatically, compromising the system and stealing sensitive data. 

Compromised NPM packages and attack tactics 

The hackers targeted six popular npm packages, already downloaded over 330 times, using typosquatting to trick developers into installing fake versions of legitimate libraries. 

To make the infiltration even more effective, the group created GitHub repositories associated with the malicious packages, enhancing their credibility. Fortunately, cyber security researchers from the Socket Research Team identified and reported the threat, leading to the removal of these repositories. 

The malware and its effects 

The attack uses a malware known as BeaverTail, designed to infect Windows, macOS, and Linux. Once installed, this malicious software can: 

  • Steal login credentials stored in browsers like Chrome, Brave, and Firefox
  • Compromise cryptocurrency wallets, including Solana and Exodus
  • Install a second-stage backdoor, called InvisibleFerret, allowing attackers to maintain persistent access to the infected system. 

Impact and risks for companies and developers

The potential impact of this new threat is enormous. With stolen credentials, attackers can gain unauthorized access to critical systems, launch large-scale attacks, and compromise the security of entire organizations.

The compromise of the software supply chain is one of the most dangerous threats to modern cyber security, as it exploits the trust developers place in open-source packages to spread malicious software without being immediately detected.

Protection strategies against supply chain attacks

To reduce the risk of such attacks, developers and companies should adopt key security measures:

  • Carefully verify the origin and integrity of NPM packages before installing them;
  • Continuously monitor code with security tools capable of detecting suspicious behavior;
  • Regularly update software and promptly apply security patches;
  • Implement a multi-layered security strategy, including sandboxing and blocking suspicious outbound connections;
  • Use automated audits to analyze third-party dependencies and identify potential vulnerabilities;
  • Educate and train developers on cyber threats and typosquatting techniques.

The future of cyber attacks on the supply chain

According to Kirill Boychenko, a researcher at the Socket Research Team, attacks from the Lazarus group are expected to become even more sophisticated:

“Hackers will continue to refine their tactics, making malicious code increasingly difficult to detect. Typosquatting and obfuscation techniques will be enhanced, expanding the reach of attacks to new ecosystems and packages.”

This prediction highlights the importance of proactive defense, with advanced detection tools and greater awareness among software developers.

The security of the software supply chain is an increasingly urgent issue: adopting preventive measures can make the difference between a protected digital environment and a catastrophic vulnerability.

To top