Malicious Code Injection in pitra-33: A Threat to npm Ecosystem
Summary
MAL-2025-164303: Malicious code in pitra-33 (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-33 package is part of the npm ecosystem and is associated with the tea.xyz token reward campaign. This package is designed to facilitate token rewards through the automatic generation and publication of derivative packages. However, it has been identified as containing malicious code that compromises its integrity and the security of the npm registry.
Vulnerability Detail
The vulnerability in pitra-33 originates from its malicious payload, which modifies the package.json file to remove private flags, alters version numbers, and generates random package names. This behavior is intended to inflate developer reputation scores within the tea protocol token rewards system. The continuous republishing of these variants pollutes the npm registry, leading to potential security risks for developers and users relying on legitimate packages.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall pitra-33If 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, consider removing the pitra-33 package from your project until a secure version is released. You can do this by executing: npm uninstall pitra-33. Additionally, monitor your package-lock.json file for any unauthorized changes.
Conclusion
The pitra-33 package poses a significant threat due to its malicious code that alters package metadata and floods the npm registry. It is crucial for developers to take immediate action by updating or removing the package and utilizing tools like Vulert to maintain the security of their projects.
See every vulnerability recorded for pitra-33 →
FAQ
pitra-33 is an npm package associated with the tea.xyz token reward campaign, designed to generate and publish derivative packages.
The vulnerability can lead to unauthorized modifications in your package.json file, potentially compromising your project's integrity and security.
If you have installed pitra-33, it is recommended to uninstall the package immediately and monitor your project for any unusual behavior.
Yes, you can use Vulert, which monitors and alerts for open-source vulnerabilities in real-time using your package-lock.json file. You can check your application for vulnerabilities using the Vulert playground without any signup.
Regularly update your dependencies, use tools like Vulert to monitor for vulnerabilities, and review the security advisories for the packages you use.
