Malicious Code Injection in pitra-39: A Threat to npm Ecosystem
Summary
MAL-2025-164309: Malicious code in pitra-39 (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-39 is part of a series of malicious npm packages associated with the tea.xyz token reward campaign. These packages are designed to manipulate the npm registry by generating and publishing derivative packages with randomized names. This behavior is intended to inflate developer reputation scores for token rewards, posing a significant threat to the integrity of the npm ecosystem.
Vulnerability Detail
The vulnerability in pitra-39 stems from its malicious payload, which modifies the package.json file to remove private flags, alters version numbers, and generates random package names. This results in the continuous republishing of variants that pollute the npm registry. The origin of this vulnerability is linked to the broader campaign that exploits npm's publishing mechanisms, leading to potential reputational damage for developers and increased difficulty in managing legitimate packages.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall pitra-39If 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-39 and any other packages associated with the tea.xyz campaign. Regularly audit your dependencies using tools like npm audit to identify and mitigate risks from malicious packages.
Conclusion
The pitra-39 package poses a significant threat to the npm ecosystem due to its malicious behavior. It is crucial for developers to remain vigilant, regularly audit their dependencies, and utilize tools like Vulert to monitor for vulnerabilities. By taking proactive measures, you can protect your projects from potential harm.
See every vulnerability recorded for pitra-39 →
FAQ
pitra-39 is an npm package that has been identified as malicious, designed to manipulate the npm registry for fraudulent purposes.
The package can modify your project's package.json file, remove private flags, and continuously publish variants, leading to potential pollution of the npm registry.
You can use Vulert, which monitors and alerts for open-source vulnerabilities in your software. Visit Vulert Scanner to check your application without any signup.
You should uninstall pitra-39 immediately using the command 'npm uninstall pitra-39' and audit your dependencies for any other malicious packages.
Yes, tools like npm audit and Vulert can help you identify and manage vulnerabilities in your npm packages effectively.
