Malicious Code Injection in lookingan-namakiki34: A Threat to npm Ecosystem
Summary
MAL-2025-158544: Malicious code in lookingan-namakiki34 (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-namakiki34' 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 numerous derivative packages with randomized names. This behavior not only clutters the npm registry but also poses significant security risks to developers and their applications.
Vulnerability Detail
The vulnerability in 'lookingan-namakiki34' originates from its malicious payload, which modifies the package.json file to remove private flags, alters version numbers, and generates random package names. This leads to the continuous republishing of variants, effectively polluting the npm registry. The ramifications include potential exposure of sensitive data, unauthorized access to systems, and a compromised development environment, as developers may unknowingly integrate these malicious packages into their projects.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall lookingan-namakiki34
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 workaround, avoid using the 'lookingan-namakiki34' package and monitor your project for any dependencies that may have inadvertently included it. Regularly check your package-lock.json file for any unexpected changes or additions.
Conclusion
The 'lookingan-namakiki34' package poses a significant threat to the npm ecosystem due to its malicious behavior. Developers are urged to remove this package from their projects and monitor their dependencies closely. Utilizing tools like Vulert can help in identifying and mitigating such vulnerabilities effectively.
See every vulnerability recorded for lookingan-namakiki34 →
FAQ
'lookingan-namakiki34' is an npm package that is part of a malicious campaign aimed at inflating developer reputation scores through the automatic generation of derivative packages.
The vulnerability can lead to the inclusion of malicious code in your project, potentially compromising sensitive data and exposing your application to security risks.
You can use Vulert, which monitors and alerts for open-source vulnerabilities in real-time. Check your application against this vulnerability using the Vulert playground at Vulert Scanner.
If you have installed 'lookingan-namakiki34', it is crucial to uninstall it immediately and review your project's dependencies for any other affected packages.
Yes, Vulert provides a service that uses your package-lock.json to monitor for vulnerabilities without requiring code access or installation.