Malicious Code Injection in lookingan-namala18: A Threat to npm Ecosystem
Summary
MAL-2025-158727: Malicious code in lookingan-namala18 (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-namala18' is part of a series of malicious npm packages that emerged during the tea.xyz token reward campaign. These packages are designed to inflate developer reputation scores by automatically generating and publishing derivative packages with randomized names. This behavior not only clutters the npm registry but also poses a significant risk to developers who may unknowingly incorporate these packages into their projects.
Vulnerability Detail
The vulnerability in 'lookingan-namala18' stems from its malicious code that modifies the package.json file to remove private flags, alters version numbers, and generates random package names. This behavior is intended to pollute the npm registry and can lead to unintended consequences for developers, including the potential for reputation damage and security risks associated with using compromised packages. The malicious payload is part of a broader scheme to exploit the npm ecosystem for token rewards.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall lookingan-namala18
If 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 measure, you can avoid using the 'lookingan-namala18' package and monitor your project for any dependencies that may have inadvertently included it. Regularly check your package-lock.json file for any suspicious entries.
Conclusion
The 'lookingan-namala18' package poses a significant threat to developers within the npm ecosystem due to its malicious behavior. It is crucial to remove this package from your projects and utilize tools like Vulert to monitor for vulnerabilities. Staying vigilant and informed can help mitigate risks associated with open-source dependencies.
See every vulnerability recorded for lookingan-namala18 →
FAQ
The main issue is that it contains malicious code designed to manipulate package metadata and flood the npm registry with derivative packages.
You can use tools like Vulert, which monitors your package-lock.json for vulnerabilities in real-time. Visit Vulert Scanner to check your application without needing to sign up.
You should uninstall the package immediately using 'npm uninstall lookingan-namala18' and review your project's dependencies for any other malicious packages.
Yes, using this package can lead to security vulnerabilities, reputation damage, and potential disruptions in your development workflow due to the pollution of the npm registry.
Regularly audit your dependencies, use trusted packages, and stay informed about known vulnerabilities in the npm ecosystem.