Malicious Code Injection in pitra-17: A Threat to npm Ecosystem
Summary
MAL-2025-164285: Malicious code in pitra-17 (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-17 is an npm package that has been identified as part of a malicious campaign targeting the npm registry. It is designed to participate in the tea.xyz token reward scheme, which incentivizes the creation of numerous derivative packages. The package's functionality is compromised by malicious scripts that manipulate its metadata and behavior, leading to potential security risks for developers using it.
Vulnerability Detail
The vulnerability in pitra-17 originates from its association with a malicious campaign that floods the npm registry with derivative packages. The malicious payload alters the package.json file by removing private flags, changing version numbers, and generating random package names. This behavior can lead to the pollution of the npm registry, making it difficult for developers to trust packages and potentially exposing them to further attacks.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall pitra-17If 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-17 and any other packages associated with the tea.xyz token reward campaign. Regularly audit your package dependencies to identify and remove any malicious packages.
Conclusion
The pitra-17 package poses a significant threat due to its malicious code that alters package metadata and floods the npm registry with untrustworthy derivatives. It is crucial for developers to remove this package and monitor their dependencies to maintain the integrity of their projects.
See every vulnerability recorded for pitra-17 →
FAQ
pitra-17 is an npm package that has been linked to a malicious campaign aimed at inflating developer reputation scores through the creation of numerous derivative packages.
The vulnerability can lead to the pollution of the npm registry, making it difficult to trust packages and potentially exposing your project to further security risks.
You should remove pitra-17 from your project and check for any other potentially malicious packages. Use npm uninstall pitra-17 to remove it.
Yes, you can use Vulert, which monitors your package-lock.json for open-source vulnerabilities in real-time. You can check your application against known vulnerabilities using the Vulert playground without any signup.
Regularly audit your dependencies, keep your packages updated, and use tools like Vulert to monitor for vulnerabilities in your projects.
