Malicious Code Injection in lookingan-namalaka41: A Threat to npm Ecosystem
Summary
MAL-2025-158853: Malicious code in lookingan-namalaka41 (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-namalaka41' is part of the npm ecosystem and is associated with the tea.xyz token reward campaign. This package is designed to automate the generation and publication of derivative packages, which can inflate developer reputation scores for token rewards. Its functionality is compromised due to malicious scripts that alter package metadata and republish variants, leading to potential security risks.
Vulnerability Detail
The vulnerability in 'lookingan-namalaka41' originates from its association with a malicious campaign that employs scripts to modify the package.json file. This includes removing private flags, changing version numbers, and generating random package names. The continuous republishing of these variants can lead to pollution of the npm registry, making it difficult for developers to trust the integrity of packages. The ramifications include potential exploitation of developers and users who may unknowingly install compromised packages.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall lookingan-namalaka41If 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, avoid using the 'lookingan-namalaka41' package and consider using alternative packages that provide similar functionality without the associated risks.
Conclusion
The 'lookingan-namalaka41' package poses significant risks due to its malicious code that alters package metadata and repopulates the npm registry with compromised variants. It is crucial for developers to remove this package and monitor their applications for vulnerabilities to maintain security.
See every vulnerability recorded for lookingan-namalaka41 →
FAQ
The primary risk is the injection of malicious code that alters package metadata and can lead to the installation of compromised packages.
You can use Vulert, which monitors and alerts for open-source vulnerabilities in real-time. Visit Vulert Scanner to check your application without needing to sign up.
If you have installed the package, immediately uninstall it using 'npm uninstall lookingan-namalaka41' and check for any other affected packages.
Yes, consider using other npm packages that provide similar functionalities but do not have known vulnerabilities.
Regularly audit your dependencies, use tools like Vulert for real-time monitoring, and only install packages from trusted sources.
