Malicious Code Injection in pilka-luiu-kanuaniniu: A Threat to npm Ecosystem
Summary
MAL-2025-164189: Malicious code in pilka-luiu-kanuaniniu (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-luiu-kanuaniniu' is part of a series of npm packages associated with 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. This behavior poses a significant risk to the integrity of the npm registry and can lead to the proliferation of malicious code.
Vulnerability Detail
The vulnerability in 'pilka-luiu-kanuaniniu' originates from its malicious payload, which modifies the package.json file to remove private flags, alters version numbers, and generates random package names. This allows the package to continuously republish variants, polluting the npm registry and potentially compromising other projects that depend on these packages. The malicious scripts included (auto.js, autopublish.js, etc.) are designed to automate this process, making it difficult for developers to detect and mitigate the threat.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall pilka-luiu-kanuaniniuIf 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 affected package and replace it with a reputable alternative that provides similar functionality without the associated risks. Always validate the source and integrity of packages before including them in your project.
Conclusion
The 'pilka-luiu-kanuaniniu' package poses a significant risk due to its malicious behavior of modifying project files and republishing variants. It is crucial for developers to remain vigilant, regularly audit their dependencies, and utilize tools like Vulert to monitor for vulnerabilities. Taking proactive steps can help safeguard your projects from such threats.
See every vulnerability recorded for pilka-luiu-kanuaniniu →
FAQ
Using this package can lead to the modification of your project's package.json file, potentially exposing your project to further vulnerabilities and reputation damage.
You can use tools like Vulert, which monitors your package-lock.json for vulnerabilities in real-time. Visit Vulert Scanner to check if your application is affected without any signup.
Immediately uninstall the package using 'npm uninstall pilka-luiu-kanuaniniu' and review your project's dependencies for any other potentially malicious packages.
Yes, consider using well-established packages that offer similar functionality but have a proven track record of security and reliability.
Regularly audit your dependencies, use tools like Vulert for monitoring, and only install packages from trusted sources.
