Malicious Code Injection in pitra-59: A Threat to npm Packages
Summary
MAL-2025-164331: Malicious code in pitra-59 (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-59 is an npm package that has been identified as part of a malicious campaign targeting the npm ecosystem. This package is associated with the tea.xyz token reward initiative, which has been known to flood the npm registry with numerous derivative packages. The primary function of pitra-59, like many similar packages, is to manipulate the npm registry for the purpose of inflating developer reputation scores through the automatic generation and publishing of packages with randomized names.
Vulnerability Detail
The vulnerability in pitra-59 stems from its inclusion in a malicious campaign that deploys scripts designed to modify package.json files. These modifications include removing private flags, altering version numbers, and generating random package names, which ultimately leads to the pollution of the npm registry. The malicious payload can significantly impact developers by compromising the integrity of the npm ecosystem and potentially introducing security risks into applications that depend on these packages.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall pitra-59If 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 pitra-59 and any other packages from the tea.xyz campaign. Regularly audit your dependencies using tools like npm audit to identify and remove any malicious packages.
Conclusion
The pitra-59 package poses a significant threat to the npm ecosystem due to its malicious code that modifies package.json files. It is crucial for developers to be vigilant and remove such packages from their projects to maintain the integrity and security of their applications. Regular audits and monitoring can help mitigate these risks.
See every vulnerability recorded for pitra-59 →
FAQ
pitra-59 is an npm package involved in a malicious campaign that modifies package.json files to inflate developer reputation scores.
The vulnerability can lead to the introduction of malicious code into your application, compromising its security and integrity.
You should uninstall pitra-59 immediately and check your package-lock.json for any references to this package.
You can use tools like npm audit or services 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 for vulnerabilities in your application without any signup.
