Malicious Code Injection in pitra-30: A Threat to npm Ecosystem
Summary
MAL-2025-164300: Malicious code in pitra-30 (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-30 package is part of the npm ecosystem, which is widely used for JavaScript package management. This package has been identified as part of a malicious campaign that aims to exploit the npm registry by flooding it with derivative packages. The primary function of pitra-30 is to serve as a token reward mechanism for the tea.xyz protocol, but its malicious behavior undermines the integrity of the npm ecosystem.
Vulnerability Detail
The vulnerability in pitra-30 originates from its design to include autopublish scripts that manipulate the package.json file. These scripts remove private flags, alter version numbers, and generate random package names, leading to the continuous republishing of variants. This behavior not only inflates developer reputation scores but also pollutes the npm registry, potentially leading to security risks for developers who unknowingly use these compromised packages.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall pitra-30If 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-30 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 any signup.
Conclusion
The pitra-30 package poses a significant threat to the npm ecosystem due to its malicious behavior. It is crucial for developers to be vigilant and remove any affected packages while utilizing tools like Vulert to stay informed about potential vulnerabilities. By taking proactive measures, you can help maintain the security and integrity of your projects.
See every vulnerability recorded for pitra-30 →
FAQ
pitra-30 is an npm package that has been identified as part of a malicious campaign to exploit the npm registry.
Using pitra-30 can compromise your project's integrity by introducing malicious code that alters package configurations and floods the npm registry.
You should uninstall pitra-30 immediately using the command 'npm uninstall pitra-30' and check for any dependencies that may also be affected.
You can use Vulert, which monitors your package-lock.json for vulnerabilities in real-time. Visit https://vulert.com for more information.
Regularly update your packages, use trusted sources, and employ tools like Vulert to monitor your dependencies for vulnerabilities.
