Malicious Code Injection in lookingan-nalako27: A Threat to npm Packages
Summary
MAL-2025-158435: Malicious code in lookingan-nalako27 (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-nalako27' 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 npm with malicious packages. These packages often contain scripts designed to manipulate the npm registry and inflate developer reputation scores, posing a significant risk to developers and users relying on npm for secure package management.
Vulnerability Detail
The vulnerability in 'lookingan-nalako27' originates from its involvement in a malicious campaign that 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 the integrity of other packages. The malicious payload can affect developers' reputation and trust in the npm ecosystem, making it crucial to address this issue promptly.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall lookingan-nalako27If 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 measure, you can avoid using the 'lookingan-nalako27' package in your project. Additionally, consider using tools like Vulert to monitor your package-lock.json for vulnerabilities. You can check if your application is affected by this vulnerability using the Vulert playground at https://vulert.com/scanner without requiring any signup.
Conclusion
The 'lookingan-nalako27' package poses a significant risk due to its malicious nature, which can compromise npm projects and developer reputations. It is crucial to remove this package and monitor for vulnerabilities using tools like Vulert to maintain the security of your applications.
See every vulnerability recorded for lookingan-nalako27 →
FAQ
It is an npm package associated with a malicious campaign that modifies package metadata and floods the npm registry with derivative packages.
The vulnerability can compromise the integrity of your project by introducing malicious code and affecting your developer reputation.
You should remove the 'lookingan-nalako27' package immediately and monitor your project for any other vulnerabilities.
Yes, Vulert allows you to monitor your package-lock.json for vulnerabilities in real-time without requiring access to your code.
Regularly update your packages, use tools like Vulert for monitoring, and review package dependencies before installation.
