Malicious Code Injection in pitra-12 Package: npm Vulnerability Overview
Summary
MAL-2025-164280: Malicious code in pitra-12 (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-12 package is part of the npm ecosystem and is associated with the tea.xyz token reward campaign. This package is designed to facilitate the automatic generation and publication of derivative packages, which can inflate developer reputation scores for rewards. However, it has been identified as containing malicious code that modifies its own metadata and behavior.
Vulnerability Detail
The vulnerability in the pitra-12 package originates from its malicious intent to manipulate the npm registry. It includes scripts that automatically alter the package.json file by removing private flags, changing version numbers, and generating random package names. This behavior leads to the pollution of the npm registry and can compromise the integrity of the ecosystem, potentially affecting other developers and their projects.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall pitra-12If 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 pitra-12 package altogether and look for alternative packages that provide similar functionality without the associated risks. Additionally, you can monitor your project dependencies using tools like Vulert, which can alert you to vulnerabilities in real-time without requiring code access.
Conclusion
The pitra-12 package poses a significant risk due to its malicious code that alters package metadata and pollutes the npm registry. It is essential to remove this package from your projects and monitor for vulnerabilities using tools like Vulert to maintain the integrity of your software dependencies.
See every vulnerability recorded for pitra-12 →
FAQ
The pitra-12 package is an npm package associated with the tea.xyz token reward campaign, designed to automate the generation and publication of derivative packages.
The pitra-12 package modifies its own package.json file to remove private flags, changes version numbers, and generates random package names, leading to pollution of the npm registry.
You can use the Vulert playground at Vulert Scanner to check if your application is affected by the pitra-12 vulnerability without needing to sign up.
If you have pitra-12 installed, you should uninstall it immediately using the command 'npm uninstall pitra-12' and check your package-lock.json for any references.
Yes, Vulert is a tool that monitors and alerts for open-source vulnerabilities in real-time using just your package-lock.json file.
