Malicious Code Injection in pitra-45: A Threat to npm Ecosystem
Summary
MAL-2025-164316: Malicious code in pitra-45 (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-45 is part of a broader campaign targeting the npm ecosystem, specifically linked to the tea.xyz token reward initiative. This package is designed to automate the generation and publication of derivative packages, which can mislead developers and inflate reputation scores within the npm registry. Its primary function is to facilitate token rewards, but it has been compromised to include malicious scripts.
Vulnerability Detail
The vulnerability in pitra-45 stems from its inclusion in a malicious campaign 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 variants, which pollutes the npm registry and can compromise the integrity of other packages. The malicious payload is designed to exploit the npm ecosystem, potentially affecting developers who rely on these packages for legitimate purposes.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall pitra-45If 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-45 and any packages that depend on it. Additionally, consider using tools like Vulert to monitor your project for vulnerabilities. You can check if your application is affected by this vulnerability using the Vulert playground at https://vulert.com/scanner without needing to sign up.
Conclusion
The pitra-45 package poses a significant risk to the npm ecosystem due to its malicious code that alters package metadata and floods the registry with unwanted 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-45 →
FAQ
pitra-45 is an npm package associated with a token reward campaign that has been found to contain malicious code.
The vulnerability can lead to the modification of your package.json file, potentially compromising your project's integrity and security.
You should uninstall pitra-45 immediately using 'npm uninstall pitra-45' and replace it with a secure alternative.
You can use tools like Vulert, which monitors your package-lock.json for vulnerabilities in real-time.
Yes, you can use the Vulert playground at Vulert Scanner to check your application for vulnerabilities without needing to sign up.
