Malicious Code Injection in lookingan-namakiki32 Package
Summary
MAL-2025-158542: Malicious code in lookingan-namakiki32 (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 lookingan-namakiki32 package is part of the npm ecosystem and is associated with the tea.xyz token reward campaign. This package is designed to facilitate the automatic generation and publication of derivative packages, which can inflate developer reputation scores in exchange for token rewards. However, it has been identified as containing malicious code that compromises the integrity of the npm registry.
Vulnerability Detail
The vulnerability originates from the malicious code embedded within the lookingan-namakiki32 package. This code modifies the package.json file to remove private flags, alters version numbers, and generates random package names, leading to the continuous republishing of variants that pollute the npm registry. The ramifications include potential security risks for developers and users relying on the integrity of npm packages, as well as the degradation of the npm ecosystem's reliability.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall lookingan-namakiki32If 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 remove the lookingan-namakiki32 package from your project by executing the command: 'npm uninstall lookingan-namakiki32'. This will prevent any malicious code from executing while you seek a more permanent solution.
Conclusion
The lookingan-namakiki32 package has been identified as containing malicious code that poses a significant risk to developers and users within the npm ecosystem. It is crucial to take immediate action by updating or removing the affected package to safeguard your projects.
See every vulnerability recorded for lookingan-namakiki32 →
FAQ
It is an npm package associated with the tea.xyz token reward campaign, designed to generate and publish derivative packages.
The malicious code modifies your package.json file and can lead to the pollution of the npm registry, compromising the integrity of your project.
Yes, you can use Vulert, which monitors and alerts for open-source vulnerabilities in real-time using your package-lock.json file. You can check your application for this vulnerability using the Vulert playground without any signup.
If no patched version is available, it is advisable to remove the package from your project to mitigate the risk of exploitation.
Regularly monitor your dependencies for vulnerabilities using tools like Vulert, and keep your packages updated to the latest secure versions.
