Malicious Code Injection in lookingan-nalako40: A Threat to npm Ecosystem
Summary
MAL-2025-158450: Malicious code in lookingan-nalako40 (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-nalako40' is part of the npm ecosystem and is associated with the tea.xyz token reward campaign. This package is designed to generate and publish derivative packages with randomized names, which can inflate developer reputation scores for token rewards. Its functionality is compromised due to the presence of malicious scripts that manipulate package metadata.
Vulnerability Detail
The vulnerability in 'lookingan-nalako40' originates from its malicious code 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 damaging the integrity of the ecosystem. The malicious payload can also affect developers by inflating reputation scores through deceptive practices.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall lookingan-nalako40If 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 workaround, you can remove the 'lookingan-nalako40' package from your project by executing: 'npm uninstall lookingan-nalako40'. This will prevent any malicious code from executing until a secure version is available.
Conclusion
The 'lookingan-nalako40' package poses a significant risk due to its malicious code that alters package metadata and pollutes the npm registry. It is crucial for developers to take immediate action by updating or removing the package to safeguard their projects. Utilizing tools like Vulert can enhance your ability to monitor and respond to such vulnerabilities effectively.
See every vulnerability recorded for lookingan-nalako40 →
FAQ
The vulnerability can lead to the pollution of the npm registry and may compromise the integrity of your project's dependencies.
You can use Vulert, which monitors and alerts for open-source vulnerabilities in real-time. Visit Vulert Scanner to check your application without any signup.
Check the npm registry for any updated versions of 'lookingan-nalako40' that may contain security patches.
As a workaround, consider uninstalling the package to mitigate the risk until a secure version is available.
Vulert uses the package-lock.json file to monitor and alert for open-source vulnerabilities in your software, providing real-time insights.
