Malicious Code Injection in lookingan-namala10: A Threat to npm Ecosystem
Summary
MAL-2025-158718: Malicious code in lookingan-namala10 (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-namala10' is part of the npm ecosystem, which is widely used for JavaScript package management. This package is associated with the tea.xyz token reward campaign, which has been known to flood npm with malicious packages. These packages often contain scripts designed to manipulate the npm registry and inflate developer reputation scores through the automatic generation of derivative packages.
Vulnerability Detail
The vulnerability in 'lookingan-namala10' originates from its association with a malicious campaign that modifies the package.json file to remove private flags, alters version numbers, and generates random package names. This behavior leads to the continuous republishing of variants, polluting the npm registry and potentially compromising the integrity of other packages. The malicious payload can affect developers' reputations and the overall trustworthiness of the npm ecosystem.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall lookingan-namala10If 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-namala10' package and monitor your dependencies for any similar malicious packages. Use the following command to check for vulnerabilities in your project: npm audit.
Conclusion
The 'lookingan-namala10' package poses a significant threat to the npm ecosystem due to its malicious code that modifies package metadata and floods the registry. Developers should take immediate action to remove this package and utilize tools like Vulert for ongoing vulnerability monitoring.
See every vulnerability recorded for lookingan-namala10 →
FAQ
The malicious code can lead to the pollution of the npm registry, affecting the reputation of developers and the integrity of other packages.
You can use tools like Vulert to monitor your package-lock.json for vulnerabilities. Visit Vulert Scanner to check if your application is affected without needing to sign up.
Regularly audit your dependencies using npm audit and consider using tools like Vulert for real-time monitoring of open-source vulnerabilities.
Remove the package immediately and check your project for any unintended consequences caused by the malicious code.
Currently, there is no patched version available. It is recommended to remove the package and monitor for updates.
