Malicious Code Injection in lookingan-nalako31 Package
Summary
MAL-2025-158440: Malicious code in lookingan-nalako31 (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-nalako31 package is part of the npm ecosystem, which is widely used for JavaScript package management. This package has been identified as part of a malicious campaign that floods the npm registry with derivative packages. Its primary function is to facilitate the tea.xyz token reward system, which incentivizes developers to publish numerous packages, often leading to reputation inflation without genuine contributions.
Vulnerability Detail
The vulnerability in the lookingan-nalako31 package stems from its malicious code that modifies the package.json file. This code removes private flags, alters version numbers, and generates random package names, which are often themed around Indonesian culture. The malicious payload continuously republishes these variants, polluting the npm registry and potentially compromising the integrity of projects that depend on this package. This behavior can lead to security risks, including unauthorized access to sensitive data and the introduction of further vulnerabilities into dependent applications.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall lookingan-nalako31If 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 workaround, you can temporarily avoid using the lookingan-nalako31 package by replacing it with a trusted alternative or by manually managing your dependencies to ensure that no malicious packages are included. Regularly audit your package-lock.json file to identify and remove any suspicious packages.
Conclusion
The lookingan-nalako31 package poses a significant security risk due to its malicious code that alters package configurations and floods the npm registry. It is crucial for developers to remove this package from their projects and to remain vigilant about auditing their dependencies to maintain the integrity of their applications.
See every vulnerability recorded for lookingan-nalako31 →
FAQ
The lookingan-nalako31 package is an npm package that has been identified as part of a malicious campaign aimed at inflating developer reputation scores through the publication of numerous derivative packages.
This vulnerability can compromise the integrity of your application by introducing malicious code that modifies your package.json file, potentially leading to unauthorized access and other security risks.
If you have installed the lookingan-nalako31 package, you should immediately uninstall it using the command: npm uninstall lookingan-nalako31 and audit your dependencies for any other malicious packages.
You can use tools like Vulert, which monitors your package-lock.json file for open-source vulnerabilities in real-time. You can check your application for vulnerabilities using the Vulert playground without any signup.
To prevent similar vulnerabilities, regularly audit your dependencies, use trusted sources for packages, and consider implementing automated tools that can alert you to potential security issues.
