Malicious Code Injection in piluka-ali-ipibi Package: A Threat to npm Users
Summary
MAL-2025-164228: Malicious code in piluka-ali-ipibi (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 piluka-ali-ipibi package is part of the npm ecosystem, often used in JavaScript projects for various functionalities. However, it has been identified as a malicious package linked to the tea.xyz token reward campaign, which aims to manipulate developer reputation scores through automated publishing of derivative packages. This vulnerability poses a significant risk to developers and users relying on this package.
Vulnerability Detail
The vulnerability originates from the piluka-ali-ipibi package, which contains malicious code designed to modify the package.json file. This code removes private flags, alters version numbers, and generates random package names, leading to the continuous republishing of variants that pollute the npm registry. The ramifications include compromised developer reputations and potential security risks for applications relying on these packages.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall piluka-ali-ipibiIf 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 piluka-ali-ipibi package and look for alternative packages that provide similar functionality without the associated risks. Additionally, consider using tools like Vulert to monitor your project for vulnerabilities.
Conclusion
The piluka-ali-ipibi package poses a significant threat due to its malicious code that alters package metadata and floods the npm registry. It is essential for developers to remove this package from their projects and monitor their dependencies for vulnerabilities. Utilizing tools like Vulert can help maintain the security of your applications.
See every vulnerability recorded for piluka-ali-ipibi →
FAQ
The piluka-ali-ipibi package is an npm package that has been identified as malicious, designed to manipulate developer reputation scores through automated publishing.
This vulnerability can lead to the pollution of the npm registry, compromising the integrity of your project's dependencies and potentially exposing your application to security risks.
If you have installed the piluka-ali-ipibi package, you should uninstall it immediately using 'npm uninstall piluka-ali-ipibi' and monitor your project for any further vulnerabilities.
You can use Vulert, a tool that monitors your package-lock.json file for open-source vulnerabilities in real-time. You can check your application for vulnerabilities using the Vulert playground at Vulert Scanner without needing to sign up.
Yes, you should look for alternative packages that provide similar functionalities without the associated risks. Always review package details and community feedback before integrating them into your project.
