Malicious Code Injection in lookingan-namalaka6: A Threat to npm Packages
Summary
MAL-2025-158873: Malicious code in lookingan-namalaka6 (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-namalaka6' is part of the npm ecosystem, which is widely used for JavaScript package management. This package is associated with the tea.xyz token reward campaign, which has been linked to a series of malicious activities aimed at inflating developer reputation scores. The package's functionality is compromised by the presence of autopublish scripts that generate and publish derivative packages with randomized names, leading to pollution of the npm registry.
Vulnerability Detail
The vulnerability in 'lookingan-namalaka6' stems from its association with a malicious campaign that modifies the package.json file to remove private flags, alters version numbers, and generates random package names. This behavior not only compromises the integrity of the package but also poses a risk to developers who may unknowingly install these malicious variants. The continuous republishing of these packages can lead to a cluttered 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-namalaka6If 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-namalaka6' package until a secure version is released. Additionally, consider using alternative packages that provide similar functionality without the associated risks.
Conclusion
The 'lookingan-namalaka6' package poses a significant risk due to its malicious code that alters package metadata and floods the npm registry with derivative packages. Developers are urged to take immediate action by updating or removing the package and utilizing tools like Vulert for ongoing vulnerability monitoring.
See every vulnerability recorded for lookingan-namalaka6 →
FAQ
The main issue is that it contains malicious code that modifies package.json and publishes derivative packages, which can lead to npm registry pollution.
You can use Vulert, which monitors and alerts for open-source vulnerabilities in your software. By using the Vulert playground, you can check your application without any signup.
If you have installed this package, it is advisable to remove it and update to a secure version if available. Use 'npm uninstall lookingan-namalaka6' to remove it.
While specific exploits have not been detailed, the malicious behavior of the package can lead to unintended consequences for developers and their projects.
Vulert uses the package-lock.json file to monitor and alert in real-time for open-source vulnerabilities, ensuring that developers are informed about potential risks.
