Malicious Code Injection in lookingan-namakiki53: A Threat to npm Ecosystem
Summary
MAL-2025-158565: Malicious code in lookingan-namakiki53 (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-namakiki53' is part of the npm ecosystem, which is widely used for JavaScript package management. This package has been identified as part of a malicious campaign that aims to exploit the npm registry by flooding it with derivative packages. These packages are designed to inflate developer reputation scores through automated publishing scripts, which can lead to significant issues within the ecosystem.
Vulnerability Detail
The vulnerability in 'lookingan-namakiki53' originates from its association with the tea.xyz token reward campaign. The package contains scripts that modify the package.json file to remove private flags, alter version numbers, and generate random package names. This behavior not only pollutes the npm registry but also poses a risk of unintentional dependency on malicious code for developers who may unknowingly install these packages.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall lookingan-namakiki53If 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 'lookingan-namakiki53' and any of its derivatives. Additionally, you can use the following command to uninstall the package: 'npm uninstall lookingan-namakiki53'.
Conclusion
The 'lookingan-namakiki53' package poses a significant threat to the npm ecosystem due to its malicious code that modifies package metadata and floods the registry. It is crucial for developers to be aware of this vulnerability and take appropriate actions to secure their projects.
See every vulnerability recorded for lookingan-namakiki53 →
FAQ
The vulnerability involves malicious code that modifies package metadata and floods the npm registry with derivative packages.
You can use Vulert, which monitors and alerts for open-source vulnerabilities in your software. Visit Vulert Scanner to check your application without any signup.
It is advisable to uninstall the package immediately and check for any dependencies that may have been affected.
While specific exploits have not been detailed, the malicious nature of the package can lead to unintended consequences in the npm ecosystem.
The malicious code can alter your project's package.json, leading to potential security risks and dependency issues.
