Malicious Code Exploitation in lookingan-nalako95: A Threat to npm Ecosystem
Summary
MAL-2025-158510: Malicious code in lookingan-nalako95 (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
Habilume
Habit tracker with a companion that grows with you
Complete habits, earn Lume Points, and watch your Lume grow as you stay consistent.
Background
The package 'lookingan-nalako95' is part of a broader campaign that exploits the npm ecosystem by flooding it with malicious packages. These packages are designed to manipulate developer reputation scores through automated publishing scripts. The malicious nature of this package lies in its ability to modify essential files and republish variants, thereby polluting the npm registry.
Vulnerability Detail
The vulnerability originates from the package being part of the tea.xyz token reward campaign, which employs scripts to generate and publish derivative packages with randomized names. The malicious payload alters the package.json file by removing private flags, changing version numbers, and creating random package names. This behavior not only compromises the integrity of the npm registry but also poses risks to developers who may unknowingly use these tainted packages, leading to potential security breaches in their applications.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall lookingan-nalako95If 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, avoid using the 'lookingan-nalako95' package and monitor your project for any dependencies that may inadvertently include it. You can also use tools like Vulert to monitor your package-lock.json file for vulnerabilities.
Conclusion
The lookingan-nalako95 package presents a significant threat to the npm ecosystem due to its malicious behavior of modifying package files and republishing variants. Developers are advised to remove this package and utilize tools like Vulert for ongoing vulnerability monitoring to safeguard their applications.
See every vulnerability recorded for lookingan-nalako95 →
FAQ
The main threat is that it modifies package.json files and republish variants, which can lead to a polluted npm registry and potential security risks for developers.
You can use Vulert, which monitors your package-lock.json file for vulnerabilities in real-time. Visit the Vulert playground at Vulert Scanner to check your application without any signup.
You should uninstall the package immediately using 'npm uninstall lookingan-nalako95' and check for any other dependencies that may be affected.
Currently, there are no patches available for the lookingan-nalako95 package. The best course of action is to remove it from your project.
Vulert provides real-time monitoring and alerts for open-source vulnerabilities by analyzing your package-lock.json file, helping you maintain a secure application.
Habilume
Habit tracker with a companion that grows with you
Complete habits, earn Lume Points, and watch your Lume grow as you stay consistent.
