Malicious Code Detected in lookingan-namala17: A Threat to npm Users
Summary
MAL-2025-158726: Malicious code in lookingan-namala17 (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-namala17' is part of a series of npm packages that have been identified as malicious. These packages are linked to a token reward campaign that aims to inflate developer reputation scores through the automatic generation and publication of derivative packages. This behavior poses a significant risk to the integrity of the npm registry and the security of applications relying on these packages.
Vulnerability Detail
The vulnerability in 'lookingan-namala17' originates from its design to include autopublish scripts that modify the package.json file by removing private flags, altering version numbers, and generating random package names. This malicious activity leads to the pollution of the npm registry, potentially compromising the security of applications that depend on these packages. The continuous republishing of variants can also confuse developers and lead to the installation of untrusted code.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall lookingan-namala17
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 workaround, you can avoid using the 'lookingan-namala17' package and any other packages that are part of the same malicious campaign. Consider using alternative packages that provide similar functionality without the associated risks.
Conclusion
The 'lookingan-namala17' package poses a significant threat due to its malicious code designed to manipulate package metadata and pollute the npm registry. It is essential for developers to remove this package and monitor their dependencies to maintain the security of their applications.
See every vulnerability recorded for lookingan-namala17 →
FAQ
The vulnerability involves malicious code that modifies package.json files and repackages them under random names, leading to potential security risks.
You can use tools like Vulert to monitor your package-lock.json file for vulnerabilities. Visit Vulert Scanner to check if your application is affected without needing to sign up.
You should uninstall the package immediately using 'npm uninstall lookingan-namala17' and review your dependencies for any other affected packages.
There are no patches available for lookingan-namala17 as it is a malicious package. The best course of action is to remove it from your project.
Regularly audit your dependencies, use tools like Vulert for real-time monitoring, and only install packages from trusted sources.