Malicious Code Injection in pitra-43: A Threat to npm Ecosystem
Summary
MAL-2025-164314: Malicious code in pitra-43 (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-43 is an npm package that has been identified as part of a malicious campaign targeting the npm registry. This package is associated with the tea.xyz token reward initiative, which aims to inflate developer reputation scores by flooding the registry with derivative packages. The malicious nature of pitra-43 lies in its ability to modify package metadata and republish itself under various names, thereby compromising the integrity of the npm ecosystem.
Vulnerability Detail
The vulnerability in pitra-43 stems from its malicious code that alters the package.json file by removing private flags, changing version numbers, and generating random package names. This behavior not only pollutes the npm registry but also poses a significant risk to developers who may unknowingly install these compromised packages. The origin of this vulnerability is linked to the tea.xyz token reward campaign, which exploits npm's publishing mechanisms to distribute harmful code.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall pitra-43If 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-43 and any packages that are part of the tea.xyz token reward campaign. Regularly audit your dependencies using tools like npm audit to identify and mitigate potential vulnerabilities.
Conclusion
The pitra-43 package poses a significant threat to the npm ecosystem due to its malicious code that alters package metadata and floods the registry with compromised versions. It is crucial for developers to be vigilant, regularly audit their dependencies, and utilize tools like Vulert to monitor for vulnerabilities.
See every vulnerability recorded for pitra-43 →
FAQ
pitra-43 is an npm package identified as part of a malicious campaign that modifies package metadata and floods the npm registry with compromised packages.
If pitra-43 is included in your project, it can alter your package.json file, remove private flags, and republish itself under various names, potentially leading to security vulnerabilities.
You can use Vulert, which monitors open-source vulnerabilities in your software. By analyzing your package-lock.json file, Vulert can alert you to any vulnerabilities, including those from pitra-43.
You should uninstall pitra-43 immediately using the command 'npm uninstall pitra-43' and review your dependencies for any other potentially malicious packages.
There is no patch available for pitra-43 as it is a malicious package. The best course of action is to remove it from your project and ensure you are using trusted packages.
