Malicious Code Injection in pilka-luiu-kni: A Threat to npm Packages
Summary
MAL-2025-164192: Malicious code in pilka-luiu-kni (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-kni' is part of a broader campaign targeting the npm ecosystem, specifically designed to exploit the tea.xyz token reward system. This package, like many others in this campaign, is intended to inflate developer reputation scores by automatically generating and publishing numerous derivative packages with randomized names. This behavior not only clutters the npm registry but also poses significant security risks to developers who may unknowingly use these compromised packages.
Vulnerability Detail
The vulnerability in 'pilka-luiu-kni' originates from its malicious intent to modify the package.json file by removing private flags, altering version numbers, and generating random package names. This manipulation allows the package to continuously republish itself and its variants, polluting the npm registry and potentially leading to the unintentional use of these malicious packages by developers. The ramifications include compromised application integrity, exposure to further attacks, and a general degradation of trust in the npm ecosystem.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall pilka-luiu-kniIf 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 malicious package by using npm's package-lock.json to monitor dependencies. If you are using Vulert, you can check your application for vulnerabilities without any installation. Simply visit the Vulert playground at https://vulert.com/scanner and upload your package-lock.json file to see if your application is affected.
Conclusion
The 'pilka-luiu-kni' package poses a significant threat to the npm ecosystem due to its malicious behavior aimed at manipulating package metadata and inflating developer reputation scores. It is crucial for developers to be vigilant and remove any instances of this package from their projects to maintain the integrity and security of their applications.
See every vulnerability recorded for pilka-luiu-kni →
FAQ
'pilka-luiu-kni' is an npm package that is part of a malicious campaign aimed at inflating developer reputation scores through the automatic generation of derivative packages.
The vulnerability can lead to the unintentional use of malicious code, compromising the integrity of your application and potentially exposing it to further attacks.
You should immediately remove the 'pilka-luiu-kni' package from your project and check for any other affected packages.
Yes, you can use tools like Vulert, which allows you to monitor and alert for open-source vulnerabilities in real-time using just your package-lock.json file.
You can check your application for vulnerabilities by visiting the Vulert playground at Vulert Scanner and uploading your package-lock.json file.
