Malicious Code Injection in lookingan-namalaka42 Package
Summary
MAL-2025-158854: Malicious code in lookingan-namalaka42 (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 lookingan-namalaka42 package 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 known to flood the npm registry with malicious packages. The primary function of such packages is to manipulate developer reputation scores through automated publishing of derivative packages.
Vulnerability Detail
The vulnerability in the lookingan-namalaka42 package stems from its malicious code that modifies the package.json file to remove private flags and alters version numbers. It generates random package names, often themed around Indonesian culture, and continuously republishes these variants to pollute the npm registry. This behavior can lead to significant security risks, including the potential for dependency confusion and the injection of malicious code into legitimate applications.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall lookingan-namalaka42If 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-namalaka42 package and any other packages associated with the tea.xyz token reward campaign. Monitor your dependencies closely and consider using tools like Vulert to keep track of vulnerabilities in your project.
Conclusion
The lookingan-namalaka42 package poses a significant security risk due to its malicious code that alters package metadata and publishes harmful variants. It is crucial to remove this package from your project and monitor your dependencies for vulnerabilities. Utilizing tools like Vulert can help maintain the security of your applications.
See every vulnerability recorded for lookingan-namalaka42 →
FAQ
It is an npm package that is part of a malicious campaign aimed at inflating developer reputation scores through automated publishing.
The vulnerability can lead to the injection of malicious code, potentially compromising the security and integrity of your application.
You should uninstall the package immediately using npm uninstall lookingan-namalaka42 and review your other dependencies for similar vulnerabilities.
You can use tools like Vulert, which monitors your package-lock.json file for real-time alerts on open-source vulnerabilities without requiring code access.
Yes, you can use the Vulert playground at Vulert Scanner to check for vulnerabilities in your application without any signup.
