Malicious Code Injection in lookingan-namakita11: A Threat to npm Packages
Summary
MAL-2025-158619: Malicious code in lookingan-namakita11 (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
Habilume
Habit tracker with a companion that grows with you
Complete habits, earn Lume Points, and watch your Lume grow as you stay consistent.
Background
The package 'lookingan-namakita11' 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 through the automatic generation and publication of derivative packages. They often contain scripts that manipulate package metadata and publish variants to the npm registry, posing a significant risk to developers and users relying on npm for package management.
Vulnerability Detail
The vulnerability in 'lookingan-namakita11' stems from its malicious code that modifies the package.json file by removing private flags and altering version numbers. It generates random package names, often themed around Indonesian culture, and continuously republishes these variants. This behavior not only pollutes the npm registry but also compromises the integrity of the packages, potentially leading to security risks for applications that depend on them.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall lookingan-namakita11If 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 prevent the installation of this package by using npm's package-lock.json to monitor dependencies. You can also use the following command to uninstall the package: npm uninstall lookingan-namakita11.
Conclusion
The 'lookingan-namakita11' package presents a significant security risk due to its malicious code that alters package metadata and floods the npm registry. Developers should take immediate action to remove this package and monitor their applications for vulnerabilities. Utilizing tools like Vulert can enhance security management and provide real-time alerts for open-source vulnerabilities.
See every vulnerability recorded for lookingan-namakita11 →
FAQ
The main threat is the malicious code that modifies package metadata and floods the npm registry with derivative packages, which can lead to security vulnerabilities in dependent applications.
You can use Vulert, which monitors and alerts for open-source vulnerabilities in real-time. Visit the Vulert playground at Vulert Scanner to check your application without requiring any signup.
If you have installed the package, it is crucial to uninstall it immediately and check your application for any potential security issues that may have arisen from its use.
Currently, there are no known patches for 'lookingan-namakita11'. The best course of action is to remove the package and monitor for any updates from the package maintainers.
Vulert uses your package-lock.json to monitor for vulnerabilities in your open-source dependencies, providing real-time alerts and insights to help you maintain secure applications.
Habilume
Habit tracker with a companion that grows with you
Complete habits, earn Lume Points, and watch your Lume grow as you stay consistent.
