Malicious Code Injection in pitra-58 Package: A Threat to npm Ecosystem
Summary
MAL-2025-164330: Malicious code in pitra-58 (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-58 package is part of the npm ecosystem, which is widely used for JavaScript package management. This package is associated with the tea.xyz token reward campaign, which has been known to flood npm with malicious packages. The primary functionality of pitra-58 is to serve as a tool within this campaign, but it has been compromised to include harmful scripts that manipulate package metadata.
Vulnerability Detail
The vulnerability in pitra-58 originates from its design to automatically generate and publish derivative packages with randomized names. This malicious behavior includes modifying the package.json file to remove private flags, altering version numbers, and continuously republishing variants to pollute the npm registry. The ramifications of this vulnerability include the potential for developers to unknowingly install compromised packages, leading to security risks and reputational damage within the developer community.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall pitra-58If 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, avoid using the pitra-58 package and consider using alternative packages that provide similar functionality without the associated risks. Additionally, you can monitor your package-lock.json file for any unauthorized changes.
Conclusion
The pitra-58 package poses a significant threat due to its malicious code that alters package metadata and repopulates the npm registry with compromised packages. It is crucial for developers to remove this package and monitor their projects for any vulnerabilities to maintain the integrity of their applications.
See every vulnerability recorded for pitra-58 →
FAQ
pitra-58 is an npm package that is part of a token reward campaign, but it has been identified as containing malicious code that can compromise your project.
The vulnerability can lead to unauthorized modifications of your package.json file and the installation of malicious packages, which can compromise your application's security.
You should uninstall the pitra-58 package immediately using 'npm uninstall pitra-58' and check your project for any unauthorized changes.
Yes, you can use tools like Vulert, which monitors your package-lock.json file for open-source vulnerabilities in real-time without requiring code access or installation.
You can use the Vulert playground at Vulert Scanner to check if your application is affected by the pitra-58 vulnerability without needing to sign up.
