Malicious Code Injection in lookingan-namakita59: A Threat to npm Packages
Summary
MAL-2025-158671: Malicious code in lookingan-namakita59 (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-namakita59' is part of the npm ecosystem, which is widely used for JavaScript package management. This package is associated with the tea.xyz token reward campaign, which has been known to flood the npm registry with malicious packages. These packages often contain scripts designed to manipulate package metadata and inflate developer reputation scores, posing significant risks to users and the integrity of the npm registry.
Vulnerability Detail
The vulnerability in 'lookingan-namakita59' stems from its malicious code that modifies the package.json file to remove private flags and alters version numbers. It generates random package names, primarily themed around Indonesian culture, and continuously republishes these variants to pollute the npm registry. This behavior can lead to unauthorized access, reputation damage for developers, and a compromised npm ecosystem.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall lookingan-namakita59If 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-namakita59' package from your project by executing 'npm uninstall lookingan-namakita59'. This will prevent any malicious code from executing in your environment until a secure version is available.
Conclusion
The 'lookingan-namakita59' package presents a significant security risk due to its malicious code designed to manipulate npm package metadata. Users are advised to uninstall the package and monitor for updates. Utilizing tools like Vulert can help in identifying and managing such vulnerabilities effectively.
See every vulnerability recorded for lookingan-namakita59 →
FAQ
The vulnerability involves malicious code that alters package metadata and republishes variants to the npm registry, potentially compromising the integrity of the ecosystem.
You can use Vulert, which monitors and alerts for open-source vulnerabilities in real-time. Visit Vulert Scanner to check your application without any signup.
If you have installed this package, it is recommended to uninstall it immediately and check for any updates or patches.
Yes, using npm packages can pose risks if the packages are not properly vetted, as malicious packages can compromise your application and its data.
Vulert uses package-lock.json to monitor for vulnerabilities in your software, providing alerts in real-time to help you maintain a secure application.
