Malicious Code Injection in pilka-lni-limaubi: A Threat to npm Ecosystem
Summary
MAL-2025-164153: Malicious code in pilka-lni-limaubi (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 pilka-lni-limaubi is part of a series of npm packages that have been linked to the tea.xyz token reward campaign. These packages are designed to manipulate the npm registry by generating and publishing numerous derivative packages with randomized names. This behavior not only inflates developer reputation scores but also poses a significant risk to the integrity of the npm ecosystem.
Vulnerability Detail
The vulnerability in pilka-lni-limaubi stems from its malicious payload, which modifies the package.json file to remove private flags, alters version numbers, and generates random package names. This manipulation leads to the continuous republishing of variants, effectively polluting the npm registry. The origin of this vulnerability is traced back to the tea.xyz token reward campaign, which exploits npm's publishing mechanisms for malicious purposes.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall pilka-lni-limaubiIf 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 avoid using the pilka-lni-limaubi package and monitor your dependencies for any malicious activity. You may also consider using tools like Vulert to monitor your package-lock.json for vulnerabilities in real-time.
Conclusion
The pilka-lni-limaubi package poses a significant threat to the npm ecosystem due to its malicious code that manipulates package metadata and floods the registry with derivative packages. It is crucial for developers to be vigilant and take immediate action to remove affected packages and monitor their dependencies.
See every vulnerability recorded for pilka-lni-limaubi →
FAQ
pilka-lni-limaubi is an npm package that has been identified as part of a malicious campaign to manipulate the npm registry.
The vulnerability can lead to the pollution of the npm registry and may compromise the integrity of your project's dependencies.
You should uninstall the pilka-lni-limaubi package immediately and monitor your project for any other potentially malicious dependencies.
Yes, regularly audit your dependencies and use tools like Vulert to monitor for vulnerabilities in real-time.
You can find detailed information about this vulnerability in the Open Source Vulnerability database or by visiting the Vulert website.
