Malicious Code Injection in lookingan-namakiki52: A Threat to npm Packages
Summary
MAL-2025-158564: Malicious code in lookingan-namakiki52 (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-namakiki52' 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 poses significant risks to the integrity of the npm registry and the security of applications relying on these packages.
Vulnerability Detail
The vulnerability in 'lookingan-namakiki52' stems from its malicious code, which modifies the package.json file to remove private flags, alters version numbers, and generates random package names. This results in the continuous republishing of variants that pollute the npm registry. The origin of this vulnerability is linked to the tea.xyz token reward campaign, which incentivizes the creation of such malicious packages, potentially leading to compromised applications and loss of developer trust.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall lookingan-namakiki52If 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 package by using npm's package-lock.json to monitor dependencies. Additionally, consider using tools like Vulert to check for vulnerabilities in your project. You can access the Vulert playground at https://vulert.com/scanner to see if your application is affected without needing to sign up.
Conclusion
The 'lookingan-namakiki52' package poses a significant security risk due to its malicious code designed to manipulate package metadata and pollute the npm registry. It is essential to remove this package from your projects and utilize tools like Vulert for ongoing vulnerability monitoring to safeguard your applications.
See every vulnerability recorded for lookingan-namakiki52 →
FAQ
The malicious code can compromise the integrity of your application by modifying essential files and introducing potentially harmful packages.
You can check your package.json and package-lock.json files for any references to lookingan-namakiki52 or use tools like Vulert to scan your project.
Regularly audit your dependencies, use tools like Vulert for real-time monitoring, and avoid using unverified packages from the npm registry.
Immediately uninstall the package using 'npm uninstall lookingan-namakiki52' and check for any other affected packages.
Yes, Vulert can monitor your package-lock.json file to alert you in real-time for any open-source vulnerabilities in your software.
