Malicious Code Injection in lookingan-nalako65: A Threat to npm Ecosystem
Summary
MAL-2025-158477: Malicious code in lookingan-nalako65 (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-nalako65' 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 behavior not only clutters the npm registry but also poses significant security risks to developers and their applications.
Vulnerability Detail
The vulnerability in 'lookingan-nalako65' originates from its malicious payload, which modifies the package.json file to remove private flags and alters version numbers. It generates random package names, often themed around Indonesian culture, and continuously republishes these variants. This behavior can lead to the pollution of the npm registry, making it difficult for developers to find legitimate packages and potentially exposing their applications to further vulnerabilities.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall lookingan-nalako65If 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-nalako65' package and look for alternative packages that provide similar functionality without the associated risks. Always verify the source and integrity of packages before including them in your project.
Conclusion
The 'lookingan-nalako65' package poses significant risks due to its malicious behavior of modifying package.json files and flooding the npm registry with unwanted variants. Developers are urged to remove this package and utilize tools like Vulert to monitor their projects for vulnerabilities. Staying vigilant and informed is crucial in maintaining the security of your applications.
See every vulnerability recorded for lookingan-nalako65 →
FAQ
The primary risk is the modification of package.json files, which can lead to the exposure of sensitive information and the proliferation of malicious packages in the npm registry.
You can use Vulert, which monitors and alerts for open-source vulnerabilities in real-time. By uploading your package-lock.json file to the Vulert playground, you can check for vulnerabilities without any signup.
You should uninstall the package immediately using 'npm uninstall lookingan-nalako65' and review your project for any potential impacts caused by its use.
Yes, you should look for reputable packages that serve similar purposes but have a verified history and community support.
Regularly audit your dependencies, use tools like Vulert for monitoring, and only install packages from trusted sources.
