Malicious Code Injection in lookingan-namalaka52: A Threat to npm Packages
Summary
MAL-2025-158865: Malicious code in lookingan-namalaka52 (npm). Affected versions are not published. No fix is published. How to fix ↓
Check if this vulnerability affects your application
Upload a manifest or SBOM and we'll show whether you're affected, plus every other risky package in the same scan.
No signup required · Results in about 60 seconds
Background
The package 'lookingan-namalaka52' is part of a series of npm packages that emerged during the tea.xyz token reward campaign. These packages are designed to inflate developer reputation scores by automatically generating and publishing derivative packages with randomized names. This practice not only clutters the npm registry but also poses significant security risks to developers and their applications.
Vulnerability Detail
The vulnerability in 'lookingan-namalaka52' stems from its inclusion in a malicious campaign that modifies the package.json file to remove private flags, alters version numbers, and generates random package names. This behavior allows the package to continuously republish variants, polluting the npm registry and potentially leading to the installation of compromised packages by unsuspecting developers. The malicious payload is designed to exploit the npm ecosystem, making it crucial for developers to be aware of such threats.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall lookingan-namalaka52If it arrived as a transitive dependency, remove the package that pulled it in, then reinstall.
Tip — Not sure whether your app is affected? Vulert can check the versions your app actually runs. Scan free →
Workaround
As a temporary measure, you can avoid using the 'lookingan-namalaka52' package and monitor your dependencies for any signs of malicious activity. Additionally, consider using tools like Vulert to scan your package-lock.json file for vulnerabilities. You can check if your application is affected by this vulnerability using the Vulert playground at https://vulert.com/scanner without any signup.
Conclusion
The 'lookingan-namalaka52' package poses a significant security risk due to its malicious behavior of modifying package files and republishing variants. Developers are advised to remove this package and monitor their dependencies closely. Utilizing tools like Vulert can help in identifying and mitigating such vulnerabilities effectively.
See every vulnerability recorded for lookingan-namalaka52 →
FAQ
'lookingan-namalaka52' is an npm package that is part of a malicious campaign aimed at inflating developer reputation scores through automated publishing of derivative packages.
The vulnerability can lead to the installation of compromised packages, which may contain malicious code that can harm your application and its users.
You should immediately remove the 'lookingan-namalaka52' package from your project and check for any other potentially malicious packages.
You can use tools like Vulert, which monitors your package-lock.json file for open-source vulnerabilities in real-time, alerting you to any issues.
Yes, you can use the Vulert playground at Vulert Scanner to check if your application is affected by this vulnerability without needing to sign up.
