Malicious Code Injection in lookingan-namakita18: A Threat to npm Ecosystem
Summary
MAL-2025-158626: Malicious code in lookingan-namakita18 (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-namakita18' is part of a series of npm packages that have been associated with the tea.xyz token reward campaign. These packages are designed to manipulate the npm registry by generating and publishing derivative packages with randomized names. The malicious nature of this package lies in its ability to modify critical files and inflate developer reputation scores for token rewards.
Vulnerability Detail
The vulnerability in 'lookingan-namakita18' originates from its inclusion in a malicious campaign that floods the npm registry with derivative packages. The malicious payload alters the package.json file by removing private flags, changing version numbers, and generating random package names. This behavior not only compromises the integrity of the npm registry but also poses a risk to developers who may unknowingly use these compromised packages, leading to potential security breaches and loss of trust in the ecosystem.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall lookingan-namakita18If 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-namakita18' package altogether and look for alternative packages that provide similar functionality without the associated risks. Additionally, you can monitor your dependencies using tools like Vulert, which can alert you to vulnerabilities in your package-lock.json file.
Conclusion
The 'lookingan-namakita18' package poses a significant threat due to its malicious code designed to manipulate the npm registry. It is crucial for developers to be vigilant, remove affected packages, and utilize monitoring tools like Vulert to safeguard their applications from such vulnerabilities.
See every vulnerability recorded for lookingan-namakita18 →
FAQ
The main issue is that it contains malicious code designed to manipulate the npm registry and inflate developer reputation scores.
You can use the Vulert playground at Vulert Scanner to check if your application is affected by this vulnerability without requiring any signup.
You should uninstall the package immediately using 'npm uninstall lookingan-namakita18' and monitor your project for any other vulnerabilities.
Yes, tools like Vulert can monitor your package-lock.json and alert you in real-time for open-source vulnerabilities.
Using compromised packages can lead to security breaches, data loss, and a loss of trust in the npm ecosystem.
