Malicious Code Injection in lookingan-namalaka22: A Threat to npm Packages
Summary
MAL-2025-158832: Malicious code in lookingan-namalaka22 (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-namalaka22' is part of a series of 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. The malicious nature of this package lies in its ability to modify critical files and republish itself, contributing to the pollution of the npm registry.
Vulnerability Detail
The vulnerability in 'lookingan-namalaka22' originates from its inclusion in a malicious campaign that utilizes autopublish scripts to alter package.json files. This manipulation removes private flags, changes version numbers, and generates random package names, leading to a significant risk of dependency confusion and potential exploitation. The continuous republishing of these variants can clutter the npm registry, making it difficult for developers to find legitimate packages.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall lookingan-namalaka22If 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-namalaka22' package and replace it with a trusted alternative. Always verify the integrity of packages before including them in your project.
Conclusion
The 'lookingan-namalaka22' package poses a significant risk due to its malicious code designed to manipulate package metadata and republish itself. It is crucial for developers to be vigilant about the packages they include in their projects and to utilize tools like Vulert for ongoing vulnerability monitoring.
See every vulnerability recorded for lookingan-namalaka22 →
FAQ
The vulnerability can lead to dependency confusion, where malicious packages can be installed instead of legitimate ones, potentially compromising your application.
You can use Vulert to monitor and alert for open-source vulnerabilities in your software. Visit Vulert Scanner to check if your application is affected without requiring any signup.
If you have installed this package, you should uninstall it immediately using 'npm uninstall lookingan-namalaka22' and review your project's dependencies for any other malicious packages.
No patches are available for this package as it is inherently malicious. The best course of action is to remove it from your project.
To prevent similar vulnerabilities, regularly audit your dependencies, use tools like Vulert for real-time monitoring, and only install packages from trusted sources.
