Malicious Code Injection in lookingan-namakiki84: A Threat to npm Users
Summary
MAL-2025-158599: Malicious code in lookingan-namakiki84 (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-namakiki84' is part of a broader campaign targeting npm users, utilizing malicious scripts to manipulate package metadata. This package is associated with the tea.xyz token reward scheme, which incentivizes developers to publish numerous derivative packages, often leading to reputation inflation in the npm registry. The malicious nature of this package poses significant risks to developers and users alike.
Vulnerability Detail
The vulnerability in 'lookingan-namakiki84' stems from its design to execute autopublish scripts that modify the package.json file. It removes private flags, alters version numbers, and generates random package names, effectively polluting the npm registry. This behavior not only compromises the integrity of the npm ecosystem but also exposes users to potential security risks, as these malicious packages can be used to distribute harmful code.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall lookingan-namakiki84If 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 affected package and monitor your project for any unusual behavior. Additionally, consider using Vulert to scan your package-lock.json file for vulnerabilities. You can access the Vulert playground at https://vulert.com/scanner to check if your application is affected without needing to sign up.
Conclusion
The lookingan-namakiki84 package represents a significant threat to the npm ecosystem due to its malicious behavior. Developers should take immediate action to remove this package and utilize tools like Vulert to monitor for vulnerabilities in their projects. Staying vigilant and proactive is essential to maintaining the security and integrity of your software.
See every vulnerability recorded for lookingan-namakiki84 →
FAQ
The primary risk is that it modifies package metadata to inflate developer reputation scores, which can lead to the proliferation of malicious packages in the npm registry.
You can check your package.json and package-lock.json files for any references to lookingan-namakiki84 or use npm commands to list installed packages.
You should uninstall the package immediately using 'npm uninstall lookingan-namakiki84' and review your project for any other potentially malicious packages.
Yes, Vulert can monitor your package-lock.json file for vulnerabilities in real-time, alerting you to any issues without requiring code access or installation.
There is no patch available for this specific package; the best course of action is to remove it from your project.
