Malicious Code Injection in lookingan-namakiki9: npm Package Vulnerability
Summary
MAL-2025-158605: Malicious code in lookingan-namakiki9 (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-namakiki9' is part of the npm ecosystem and is associated with the tea.xyz token reward campaign. This campaign has been known to flood the npm registry with packages that contain malicious scripts designed to manipulate developer reputation scores. The package's primary function is to generate and publish derivative packages with randomized names, which can lead to significant pollution of the npm registry.
Vulnerability Detail
The vulnerability in 'lookingan-namakiki9' stems from its inclusion in a malicious campaign that modifies the package.json file to remove private flags, alters version numbers, and generates 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 compromised packages, potentially leading to security breaches and loss of reputation.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall lookingan-namakiki9If 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 prevent the installation of this malicious package by using npm's package-lock.json to monitor dependencies. Ensure that you do not install any packages that are not explicitly listed in your package.json file.
Conclusion
The 'lookingan-namakiki9' package presents a significant vulnerability due to its malicious code designed to manipulate npm registry integrity. Developers should take immediate action to update or remove the package and utilize tools like Vulert for ongoing monitoring of vulnerabilities.
See every vulnerability recorded for lookingan-namakiki9 →
FAQ
The impact includes potential security breaches, pollution of the npm registry, and damage to developer reputation.
You can use Vulert to monitor your package-lock.json for vulnerabilities. Visit Vulert Scanner to check your application without any signup.
If you cannot update the package, consider removing it from your project and replacing it with a secure alternative.
Vulert uses your package-lock.json to monitor and alert you in real-time for open-source vulnerabilities in your software.
Regularly audit your dependencies and use tools like Vulert to stay informed about potential vulnerabilities in your packages.
