Malicious Code Injection in pitra-50: A Threat to npm Ecosystem
Summary
MAL-2025-164322: Malicious code in pitra-50 (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-50 is part of the npm ecosystem, which is widely used for JavaScript package management. It is associated with the tea.xyz token reward campaign, which has been known to flood the npm registry with malicious packages. These packages often contain scripts that automate the generation and publication of derivative packages, compromising the integrity of the npm ecosystem.
Vulnerability Detail
The vulnerability in pitra-50 originates from its design to include autopublish scripts that modify the package.json file. These scripts remove private flags, alter version numbers, and generate random package names, leading to the pollution of the npm registry. This malicious behavior can inflate developer reputation scores fraudulently and can potentially lead to the distribution of compromised software to users.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall pitra-50If 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-50 package from your project by executing: npm uninstall pitra-50. This will prevent any malicious code from executing while you assess the situation.
Conclusion
The pitra-50 package poses a significant risk to the npm ecosystem due to its malicious code that can manipulate package metadata and publish unauthorized versions. It is crucial for developers to take immediate action by uninstalling the package and monitoring their projects for vulnerabilities.
See every vulnerability recorded for pitra-50 →
FAQ
pitra-50 is a package in the npm ecosystem that has been identified as containing malicious code aimed at manipulating the npm registry.
The malicious code can alter your package.json file, remove private flags, and publish unauthorized versions of your package, potentially leading to security vulnerabilities.
You should uninstall pitra-50 immediately and check for any unauthorized changes in your project files.
Yes, you can use Vulert, which monitors your package-lock.json for vulnerabilities in real-time without requiring code access or installation.
You can use the Vulert playground at Vulert Scanner to check if your application is affected by this vulnerability without needing to sign up.
