Malicious Code Injection in pitra-15: A Threat to npm Ecosystem
Summary
MAL-2025-164283: Malicious code in pitra-15 (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 pitra-15 package is part of the npm ecosystem, which is widely used for JavaScript package management. This package is associated with the tea.xyz token reward campaign, which has been known to flood the npm registry with malicious packages. The primary function of pitra-15 is to facilitate the automatic generation and publication of derivative packages, which can inflate developer reputation scores for token rewards. However, this functionality has been exploited to introduce malicious code that compromises the integrity of the npm registry.
Vulnerability Detail
The vulnerability in pitra-15 originates from its design to automatically modify package.json files, removing private flags and altering version numbers. This malicious payload generates random package names, often themed around Indonesian culture, and continuously republishes these variants. The ramifications include pollution of the npm registry, potential security risks for developers using these packages, and a degradation of trust in the npm ecosystem. The malicious behavior is characterized by the presence of autopublish scripts that facilitate this exploitation.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall pitra-15If 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 remove the pitra-15 package from your project by executing the command: 'npm uninstall pitra-15'. This will prevent the malicious code from executing while you seek a secure alternative package.
Conclusion
The pitra-15 package poses a significant threat to the npm ecosystem due to its malicious code that modifies package.json files and republishes variants. It is essential to take immediate action by updating or removing the package to safeguard your projects. Regular monitoring for vulnerabilities using tools like Vulert can help maintain the security of your applications.
See every vulnerability recorded for pitra-15 →
FAQ
pitra-15 is an npm package associated with the tea.xyz token reward campaign, designed to automatically generate and publish derivative packages.
The vulnerability can lead to the pollution of the npm registry, compromising the integrity of your project and potentially introducing security risks.
You should uninstall pitra-15 immediately and check for any updates or patches for your other dependencies.
Yes, you can use Vulert to monitor your project for open-source vulnerabilities in real-time by analyzing your package-lock.json file.
You can use the Vulert playground at Vulert Scanner without any signup to check if your application is affected by this vulnerability.
