Malicious Code Injection in lookingan-namalaka24: A Threat to npm Packages
Summary
MAL-2025-158834: Malicious code in lookingan-namalaka24 (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-namalaka24' is part of the npm ecosystem and is associated with the tea.xyz token reward campaign. This package is designed to generate and publish derivative packages with randomized names, which can inflate developer reputation scores for token rewards. Its functionality is compromised due to the presence of malicious code that alters package metadata.
Vulnerability Detail
The vulnerability in 'lookingan-namalaka24' originates from its malicious payload, which modifies the package.json file to remove private flags, alters version numbers, and generates random package names. This behavior leads to the continuous republishing of variants, polluting the npm registry and potentially compromising other packages. The malicious code is part of a broader scheme to exploit the npm ecosystem for fraudulent purposes.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall lookingan-namalaka24If 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-namalaka24' package and monitor your package-lock.json file for any unauthorized changes. Regularly audit your npm packages using 'npm audit' to identify vulnerabilities.
Conclusion
The 'lookingan-namalaka24' package poses a significant threat due to its malicious behavior, which can compromise the integrity of the npm ecosystem. It is crucial for developers to take immediate action to remove this package and monitor their applications for vulnerabilities.
See every vulnerability recorded for lookingan-namalaka24 →
FAQ
The main issue is that it contains malicious code that modifies package metadata and floods the npm registry with derivative packages.
You can use Vulert, which monitors and alerts for open-source vulnerabilities in your software. Check your application using the Vulert playground at Vulert Scanner.
You should uninstall the package immediately and check for any unauthorized changes in your project.
Yes, the consequences include potential pollution of the npm registry and compromised security of dependent packages.
Regularly audit your dependencies, use trusted packages, and monitor your project with tools like Vulert to catch vulnerabilities early.
