Malicious Code Injection in lookingan-nakomi27: A Threat to npm Ecosystem
Summary
MAL-2025-158385: Malicious code in lookingan-nakomi27 (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-nakomi27' 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. The primary function of this package is to serve as a tool for developers, but it has been compromised to include harmful scripts that manipulate package metadata.
Vulnerability Detail
The vulnerability originates from the malicious code embedded within the 'lookingan-nakomi27' package. This code is designed to modify the package.json file by removing private flags, altering version numbers, and generating random package names. The malicious payload continuously republishes these variants to pollute the npm registry, potentially harming developers' reputations and compromising the integrity of the npm ecosystem.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall lookingan-nakomi27If 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-nakomi27' package and look for alternative packages that provide similar functionality without the associated risks. Additionally, consider using tools like Vulert to monitor your package-lock.json for vulnerabilities.
Conclusion
The 'lookingan-nakomi27' package poses a significant threat due to its embedded malicious code, which can compromise the integrity of the npm ecosystem. It is essential to take immediate action by uninstalling the package and monitoring your project for vulnerabilities. Utilizing tools like Vulert can help safeguard your applications against such threats.
See every vulnerability recorded for lookingan-nakomi27 →
FAQ
The malicious code can lead to unauthorized changes in your project, potentially compromising your application's security and integrity.
You can use the Vulert playground at Vulert Scanner to check if your application is affected by this vulnerability without any signup.
You should uninstall the package immediately and check for any unauthorized changes in your project.
Yes, you can look for other npm packages that offer similar functionalities without the associated risks. Always review package details before installation.
Vulert uses your package-lock.json to monitor and alert you in real-time for open-source vulnerabilities in your software, ensuring you stay informed about potential risks.
