Malicious Code Injection in pitra-10: A Threat to npm Ecosystem
Summary
MAL-2025-164278: Malicious code in pitra-10 (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
pitra-10 is an npm package that has been identified as part of a malicious campaign targeting the npm registry. This package is associated with the tea.xyz token reward initiative, which aims to inflate developer reputation scores through the automatic generation and publication of derivative packages. The malicious nature of pitra-10 lies in its ability to modify its own package.json file, thereby compromising the integrity of the npm ecosystem.
Vulnerability Detail
The vulnerability in pitra-10 originates from its design to include autopublish scripts that automatically generate and publish numerous derivative packages with randomized names. This behavior not only pollutes the npm registry but also modifies critical fields in the package.json file, such as removing private flags and altering version numbers. The ramifications of this vulnerability include potential security risks for developers who unknowingly integrate these malicious packages into their projects, leading to compromised applications and reputational damage.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall pitra-10If 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, avoid using pitra-10 and any other packages associated with the tea.xyz token reward campaign. Instead, consider using alternative packages that provide similar functionality without the associated risks.
Conclusion
The pitra-10 vulnerability poses a significant threat to the npm ecosystem by enabling the automatic generation of malicious packages that can compromise project integrity. It is crucial for developers to remain vigilant, regularly audit their dependencies, and utilize tools like Vulert to monitor for vulnerabilities.
See every vulnerability recorded for pitra-10 →
FAQ
pitra-10 is an npm package that has been identified as part of a malicious campaign to inflate developer reputation scores through the automatic generation of derivative packages.
The pitra-10 package can modify your package.json file, remove private flags, and publish malicious variants, potentially compromising your project's integrity and security.
You should uninstall pitra-10 immediately using 'npm uninstall pitra-10' and review your project's dependencies for any other potentially malicious packages.
You can use tools like Vulert, which monitors and alerts in real-time for open-source vulnerabilities in your software. You can check your application against known vulnerabilities using the Vulert playground.
Regularly audit your dependencies, use trusted sources for packages, and consider employing automated tools that can alert you to vulnerabilities as they arise.
