Malicious Code Injection in lookingan-nalako29: A Threat to npm Packages
Summary
MAL-2025-158437: Malicious code in lookingan-nalako29 (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-nalako29' is part of the npm ecosystem, which is widely used for JavaScript package management. This package has been identified as part of a malicious campaign that aims to exploit the npm registry by flooding it with derivative packages. The malicious nature of this package lies in its ability to modify its own metadata and republish itself under various names, thereby undermining the integrity of the npm ecosystem.
Vulnerability Detail
The vulnerability in 'lookingan-nalako29' originates from its association with the tea.xyz token reward campaign, which employs scripts to automatically generate and publish numerous derivative packages. These scripts alter the package.json file by removing private flags, changing version numbers, and creating random package names. This behavior not only inflates developer reputation scores but also pollutes the npm registry with potentially harmful packages, posing a risk to developers who may unknowingly install these variants.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall lookingan-nalako29If 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 avoid using the 'lookingan-nalako29' package altogether. If it is already in use, consider replacing it with a trusted alternative package that serves a similar purpose. Additionally, you can monitor your package dependencies using tools like Vulert, which can alert you to vulnerabilities in real-time without requiring code access.
Conclusion
The 'lookingan-nalako29' package poses a significant threat to the integrity of the npm ecosystem due to its malicious behavior of modifying and republishing itself. Developers should take immediate action to remove this package and monitor their dependencies for vulnerabilities. Utilizing tools like Vulert can enhance security by providing real-time alerts for open-source vulnerabilities.
See every vulnerability recorded for lookingan-nalako29 →
FAQ
The primary risk is that it can modify your project's package.json file and republish itself under different names, leading to potential security vulnerabilities and dependency issues.
You can use the Vulert playground at Vulert Scanner to check if your application is affected by this vulnerability without any signup.
If you have installed lookingan-nalako29, it is advisable to remove it from your project and replace it with a trusted alternative package.
Yes, tools like Vulert can help monitor and alert you in real-time for open-source vulnerabilities in your software by analyzing your package-lock.json.
The npm ecosystem is crucial for JavaScript development, providing a vast repository of packages that developers can use to build applications efficiently. However, it is also a target for malicious actors.
