Malicious Code Injection in lookingan-nalako68: A Threat to npm Packages
Summary
MAL-2025-158480: Malicious code in lookingan-nalako68 (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-nalako68' is part of a series of npm packages that emerged during the tea.xyz token reward campaign. These packages are designed to inflate developer reputation scores by automatically generating and publishing derivative packages with randomized names. The malicious nature of this package lies in its ability to modify essential files, thereby compromising the integrity of the npm registry.
Vulnerability Detail
The vulnerability in 'lookingan-nalako68' originates from its inclusion in a malicious campaign that floods the npm ecosystem with harmful packages. This package contains scripts that alter the package.json file by removing private flags, changing version numbers, and generating random package names. The continuous republishing of these variants leads to pollution of the npm registry, which can mislead developers and compromise their projects.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall lookingan-nalako68If 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 monitor your project for any unauthorized changes in the package.json file and revert them if necessary. Additionally, consider using tools like Vulert to keep track of vulnerabilities in your npm packages. You can check if your application is affected by this vulnerability using the Vulert playground at https://vulert.com/scanner without any signup.
Conclusion
The 'lookingan-nalako68' package poses a significant threat to npm users due to its malicious code that alters package files and floods the registry. It is essential to remove this package and monitor your projects for any vulnerabilities to maintain the integrity of your software.
See every vulnerability recorded for lookingan-nalako68 →
FAQ
The main issue is that it contains malicious code that modifies package.json files and floods the npm registry with harmful variants.
You can check your package.json and package-lock.json files for any references to lookingan-nalako68 or use tools like Vulert to scan your project.
You should uninstall the package immediately using 'npm uninstall lookingan-nalako68' and check for any unauthorized changes in your project files.
Yes, Vulert is a tool that monitors and alerts for open-source vulnerabilities in your software using just the package-lock.json file.
Yes, you can use the Vulert playground at Vulert Scanner to check if your application is affected by this vulnerability without any signup.
