Malicious Code Injection in lookingan-nalako38: A Threat to npm Ecosystem
Summary
MAL-2025-158447: Malicious code in lookingan-nalako38 (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-nalako38' is part of a series of malicious packages that emerged during the tea.xyz token reward campaign. These packages are designed to manipulate the npm registry by automatically generating and publishing numerous derivative packages with altered names and metadata. This behavior not only inflates developer reputation scores but also poses significant risks to the integrity of the npm ecosystem.
Vulnerability Detail
The vulnerability in 'lookingan-nalako38' originates from its malicious intent to modify the package.json file by removing private flags and changing version numbers. It generates random package names, often themed around Indonesian culture, and continuously republishes these variants to clutter the npm registry. This can lead to confusion among developers, potential security risks, and the degradation of the npm ecosystem's reliability.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall lookingan-nalako38
If 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-nalako38' package and replace it with a reputable alternative that serves the same purpose. Always verify the integrity and source of packages before including them in your project.
Conclusion
The 'lookingan-nalako38' package poses a significant threat to the npm ecosystem due to its malicious behavior of modifying package metadata and flooding the registry. It is essential for developers to remain vigilant, regularly update their dependencies, and utilize tools like Vulert to monitor for vulnerabilities.
See every vulnerability recorded for lookingan-nalako38 →
FAQ
It is a malicious npm package that modifies package metadata and floods the npm registry with derivative packages.
It can lead to confusion, potential security risks, and degradation of the npm ecosystem's reliability.
You should uninstall the package immediately using 'npm uninstall lookingan-nalako38'.
You can use Vulert, which monitors and alerts for open-source vulnerabilities in real-time using just your package-lock.json file.
Yes, you can use the Vulert playground at Vulert Scanner to check for vulnerabilities in your application without any signup.