Malicious Code Injection in lookingan-konami26: A Threat to npm Ecosystem
Summary
MAL-2025-158285: Malicious code in lookingan-konami26 (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-konami26' is part of a campaign that exploits the npm ecosystem by flooding it with malicious packages. These packages are designed to manipulate developer reputation scores through automated scripts that publish derivative packages with random names. This behavior not only affects the integrity of the npm registry but also poses a risk to developers who may unknowingly use these compromised packages.
Vulnerability Detail
The vulnerability in 'lookingan-konami26' originates from its involvement in the tea.xyz token reward campaign, which aims to inflate developer reputation scores. The malicious code modifies the package.json file by removing private flags, altering version numbers, and generating random package names. This results in the continuous republishing of variants that pollute the npm registry, potentially leading to security risks for developers who rely on these packages.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall lookingan-konami26If 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 workaround, you can avoid using the 'lookingan-konami26' package altogether. If you have dependencies that rely on it, consider finding alternative packages that provide similar functionality without the associated risks.
Conclusion
The 'lookingan-konami26' package poses a significant threat to the npm ecosystem due to its malicious code designed to manipulate package publishing and developer reputation. It is crucial for developers to remove this package and monitor their dependencies for similar vulnerabilities. Utilizing tools like Vulert can aid in maintaining the security of your applications.
See every vulnerability recorded for lookingan-konami26 →
FAQ
The main risk is that it can modify your project's package.json file, leading to the installation of potentially harmful packages and compromising your project's integrity.
You can use Vulert, which monitors and alerts for open-source vulnerabilities in your software. Visit Vulert Scanner to check your application without needing to sign up.
You should uninstall the package immediately using 'npm uninstall lookingan-konami26' and check your package-lock.json for any references to it.
Yes, consider researching other npm packages that offer similar functionality without the risks associated with lookingan-konami26.
Vulert uses your package-lock.json to monitor for vulnerabilities in real-time, providing alerts and insights to help maintain the security of your software.
