Krebs on Security: 18 Popular Code Packages Hacked, Rigged to Steal Crypto

Source URL: https://krebsonsecurity.com/2025/09/18-popular-code-packages-hacked-rigged-to-steal-crypto/
Source: Krebs on Security
Title: 18 Popular Code Packages Hacked, Rigged to Steal Crypto

Feedly Summary: At least 18 popular JavaScript code packages that are collectively downloaded more than two billion times each week were briefly compromised with malicious software today, after a developer involved in maintaining the projects was phished. The attack appears to have been quickly contained and was narrowly focused on stealing cryptocurrency. But experts warn that a similar attack with a slightly more nefarious payload could quickly lead to a disruptive malware outbreak that is far more difficult to detect and restrain.

AI Summary and Description: Yes

Summary: The report details a recent compromise of major JavaScript code packages on NPM, resulting from a phishing attack on a developer. The incident highlights vulnerabilities in supply chain security and raises concerns about the potential for more severe attacks, emphasizing the need for robust authentication mechanisms in software development environments.

Detailed Description:

– **Incident Overview**:
– An attacker phished a developer’s NPM account, leading to the injection of malicious code into at least 18 popular JavaScript packages.
– The phishing attack was executed through a fake NPM website that collected the developer’s credentials and two-factor authentication (2FA) token.

– **Nature of the Attack**:
– The malicious code intercepted cryptocurrency transactions in the user’s browser, redirecting payments to attacker-controlled accounts without notifying the user.
– The malware acted as a browser-based interceptor, manipulating both network traffic and application interfaces.

– **Response and Containment**:
– The attack was contained quickly, possibly preventing a larger scale disruption.
– Security firms like Akido warned of the grave implications had the attackers chosen to execute a more destructive payload.

– **Implications for Software Security**:
– The vulnerability illustrated by this attack draws attention to supply chain risks inherent in open-source software development.
– Security expert opinions in the report highlight how compromised code repositories can lead to substantial consequences for developers and organizations.

– **Recommendations for Improvement**:
– Implementing higher standards for code contributions, such as requiring verification of code provenance.
– Adopting “phish-proof” 2FA methods across platforms like NPM to deter future phishing attempts.

– **Broader Concerns**:
– The incident reflects the ongoing risks in software development reliance on a small number of maintainers and the potential for devastating supply-chain attacks.
– Experts argue that organizations need to bolster their security practices to protect against similar compromises in the future.

Overall, the incident serves as a critical reminder of the vulnerabilities associated with code dependencies and the urgent need for improved security measures in software development frameworks and repositories.