Malicious Code Injection in pitra-16: A Threat to npm Ecosystem
Summary
MAL-2025-164284: Malicious code in pitra-16 (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 pitra-16 is part of a series of npm packages that emerged during the tea.xyz token reward campaign. These packages are designed to manipulate the npm registry by creating and publishing numerous derivative packages with randomized names. The primary function of these packages is to inflate developer reputation scores in exchange for token rewards, which raises concerns about their integrity and security.
Vulnerability Detail
The vulnerability in pitra-16 stems from its malicious code that modifies the package.json file to remove private flags, alters version numbers, and generates random package names. This behavior leads to the continuous republishing of these variants, polluting the npm registry and potentially compromising the integrity of other packages. The origin of this issue is linked to the tea.xyz token reward campaign, which incentivizes such malicious practices.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall pitra-16If 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, you can avoid using pitra-16 and any other packages associated with the tea.xyz campaign. Additionally, consider using npm audit to identify and address vulnerabilities in your project.
Conclusion
The pitra-16 package poses a significant threat to the npm ecosystem due to its malicious code that modifies package files and publishes harmful variants. It is crucial for developers to remove this package and monitor their projects for vulnerabilities to maintain security and integrity.
See every vulnerability recorded for pitra-16 →
FAQ
pitra-16 is an npm package that is part of a malicious campaign aimed at inflating developer reputation scores through the creation of numerous derivative packages.
The pitra-16 package can modify your package.json file, remove private flags, and publish random packages, which can lead to security vulnerabilities and pollution of the npm registry.
You can use Vulert, which monitors and alerts for open-source vulnerabilities in your software. By utilizing the Vulert playground, you can check if your application is affected without any signup.
If you have installed pitra-16, it is recommended to remove it from your project immediately and check for any other affected packages.
Yes, tools like npm audit can help identify vulnerabilities in your project. Additionally, Vulert provides real-time monitoring for open-source vulnerabilities.
