Malicious Code Injection in lookingan-namakiki65: A Threat to npm Packages
Summary
MAL-2025-158578: Malicious code in lookingan-namakiki65 (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-namakiki65' 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. They often include scripts that manipulate package metadata, making them a significant threat to the integrity of the npm registry.
Vulnerability Detail
The vulnerability in 'lookingan-namakiki65' stems from its malicious code that modifies the package.json file to remove private flags, alters version numbers, and generates random package names. This behavior leads to the continuous republishing of variants, which pollutes the npm registry and can compromise the security and reliability of applications relying on these packages. The origin of this vulnerability is linked to the tea.xyz token reward campaign, which incentivizes such malicious practices.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall lookingan-namakiki65If 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-namakiki65' package and replace it with a trusted alternative. Additionally, consider using tools like Vulert to monitor your package-lock.json for vulnerabilities in real-time. You can check if your application is affected by this vulnerability using the Vulert playground at https://vulert.com/scanner without any signup.
Conclusion
The 'lookingan-namakiki65' package poses a significant risk due to its malicious code that alters package metadata and repopulates the npm registry with harmful variants. It is crucial for developers to remove this package and monitor their dependencies for vulnerabilities to maintain the integrity of their applications.
See every vulnerability recorded for lookingan-namakiki65 →
FAQ
The package contains malicious code that modifies package metadata and republish variants, which can compromise the integrity of the npm registry.
You can check your package-lock.json file for the presence of 'lookingan-namakiki65' or use tools like Vulert to monitor for vulnerabilities.
Remove the 'lookingan-namakiki65' package immediately and replace it with a trusted alternative. Consider updating your dependencies regularly.
Yes, regularly audit your dependencies, use tools like Vulert for real-time monitoring, and follow best practices for package management.
Not all npm packages are trustworthy. Always verify the source and reputation of a package before including it in your project.
