Wednesday, March 12, 2025
HomecryptocurrencyLazarus Hackers Exploit 6 NPM Packages to Steal Login Credentials

Lazarus Hackers Exploit 6 NPM Packages to Steal Login Credentials

Published on

SIEM as a Service

Follow Us on Google News

North Korea’s Lazarus Group has launched a new wave of attacks targeting the npm ecosystem, compromising six packages designed to steal login credentials and deploy backdoors.

The malicious packages is-buffer-validator, yoojae-validator, event-handle-package, array-empty-validator, react-event-dependency, and auth-validator have collectively been downloaded over 330 times.

These packages mimic the names of widely trusted libraries, employing a typosquatting tactic to deceive developers into integrating them into their workflows.

The Lazarus Group’s tactics closely align with their previous operations, including the use of identical obfuscation techniques and cross-platform targeting of Windows, macOS, and Linux systems.

The malware embedded in these packages is designed to collect system environment details, extract sensitive browser data, and target cryptocurrency wallets.

It systematically iterates through browser profiles to locate and extract sensitive files such as login data from Chrome, Brave, and Firefox, as well as keychain archives on macOS.

According to Socket Report, the stolen data is then exfiltrated to a hardcoded command and control (C2) server.

Technical Analysis and Attribution

The code within these malicious packages demonstrates sophisticated obfuscation techniques, including self-invoking functions and dynamic function constructors, to obscure its true functionality.

Despite these layers of concealment, the malware’s objectives align with previously documented Lazarus operations, which have consistently leveraged multi-stage payload delivery and persistence mechanisms to maintain long-term access to compromised systems.

The deployment of BeaverTail malware along with the InvisibleFerret backdoor further reinforces the likelihood of Lazarus’s involvement.

Attributing this attack definitively to Lazarus or a sophisticated copycat remains challenging due to the inherent difficulties in absolute attribution.

However, the tactics, techniques, and procedures (TTPs) observed in this npm attack closely mirror those of Lazarus’s known operations, extensively documented by researchers since 2022.

Mitigation and Recommendations

To mitigate these threats, organizations should implement a multi-layered approach to detection and defense.

Automated dependency auditing and code reviews can help identify anomalies in third-party packages, particularly those with low download counts or from unverified sources.

Continuous monitoring of unusual dependency changes can expose malicious updates, while blocking outbound connections to known C2 endpoints prevents data exfiltration.

Educating development teams on common typosquatting tactics promotes vigilance and reinforces proper vetting before installing new packages.

Are you from SOC/DFIR Teams? – Analyse Malware Incidents & get live Access with ANY.RUN -> Start Now for Free.

Aman Mishra
Aman Mishra
Aman Mishra is a Security and privacy Reporter covering various data breach, cyber crime, malware, & vulnerability.

Latest articles

DCRat Malware Spreading via YouTube to Steal Login Credentials

Cybersecurity researchers have identified a renewed wave of attacks involving the Dark Crystal RAT...

Java Axios Package Vulnerability Threatens Millions of Servers with SSRF Exploit

A critical security issue has been identified in the Axios package for JavaScript, which...

Microsoft Patch Tuesday March 2025 – 6 Actively Exploited Zero-Days & 57 Vulnerabilities Are Fixed

Microsoft has rolled out its March 2025 Patch Tuesday update, addressing a total of...

PHP XXE Injection Vulnerability Allows Attackers to Access Config Files & Private Keys

A newly uncovered XML External Entity (XXE) injection vulnerability in PHP has demonstrated how...

Supply Chain Attack Prevention

Free Webinar - Supply Chain Attack Prevention

Recent attacks like Polyfill[.]io show how compromised third-party components become backdoors for hackers. PCI DSS 4.0’s Requirement 6.4.3 mandates stricter browser script controls, while Requirement 12.8 focuses on securing third-party providers.

Join Vivekanand Gopalan (VP of Products – Indusface) and Phani Deepak Akella (VP of Marketing – Indusface) as they break down these compliance requirements and share strategies to protect your applications from supply chain attacks.

Discussion points

Meeting PCI DSS 4.0 mandates.
Blocking malicious components and unauthorized JavaScript execution.
PIdentifying attack surfaces from third-party dependencies.
Preventing man-in-the-browser attacks with proactive monitoring.

More like this

DCRat Malware Spreading via YouTube to Steal Login Credentials

Cybersecurity researchers have identified a renewed wave of attacks involving the Dark Crystal RAT...

Java Axios Package Vulnerability Threatens Millions of Servers with SSRF Exploit

A critical security issue has been identified in the Axios package for JavaScript, which...

Microsoft Patch Tuesday March 2025 – 6 Actively Exploited Zero-Days & 57 Vulnerabilities Are Fixed

Microsoft has rolled out its March 2025 Patch Tuesday update, addressing a total of...