Malicious Code Injection in pilka-kalimaa-vubiucb: A Threat to npm Packages
Summary
MAL-2025-164131: Malicious code in pilka-kalimaa-vubiucb (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-kalimaa-vubiucb is part of the npm ecosystem, which is widely used for JavaScript package management. This package has been identified as part of a malicious campaign that aims to exploit npm's publishing system. It is designed to inflate developer reputation scores through the automatic generation and publication of derivative packages with randomized names, which can lead to a polluted npm registry and potential security risks for developers using these packages.
Vulnerability Detail
The vulnerability in pilka-kalimaa-vubiucb originates from its association with the tea.xyz token reward campaign. This package contains malicious scripts that modify the package.json file to remove private flags, change version numbers, and create random package names. The continuous republishing of these variants can compromise the integrity of the npm registry, making it difficult for developers to trust the packages they are using. The malicious payload can lead to unauthorized access to sensitive data and can also affect the reputation of legitimate developers.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall pilka-kalimaa-vubiucbIf 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, avoid using the pilka-kalimaa-vubiucb package and monitor your project's dependencies for any signs of malicious activity. You can also use tools like Vulert to monitor your package-lock.json file for vulnerabilities in real-time. To check if your application is affected by this vulnerability, you can use the Vulert playground at https://vulert.com/scanner without any signup.
Conclusion
The pilka-kalimaa-vubiucb package poses a significant threat to npm users due to its malicious code designed to manipulate the npm registry. It is crucial to take immediate action by removing the package and monitoring your dependencies for vulnerabilities. Utilizing tools like Vulert can help maintain the security of your projects.
See every vulnerability recorded for pilka-kalimaa-vubiucb →
FAQ
pilka-kalimaa-vubiucb is an npm package that has been identified as part of a malicious campaign aimed at exploiting the npm registry.
The vulnerability can lead to the introduction of malicious code into your project, compromising its security and integrity.
You should uninstall the package immediately and check your project for any other potentially malicious dependencies.
You can use tools like Vulert to monitor your package-lock.json file for vulnerabilities in real-time.
Regularly update your dependencies, use trusted packages, and employ monitoring tools to keep your project secure.
