Malicious Code Injection in pitra-61: A Threat to npm Packages
Summary
MAL-2025-164334: Malicious code in pitra-61 (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 package pitra-61 is part of the npm ecosystem and is associated with the tea.xyz token reward campaign. This campaign has been known to flood the npm registry with packages that contain malicious scripts. These scripts are designed to manipulate package metadata and inflate developer reputation scores for token rewards. The pitra-61 package specifically modifies the package.json file, removing private flags and changing version numbers, which can lead to further exploitation and pollution of the npm registry.
Vulnerability Detail
The vulnerability in pitra-61 originates from its association with malicious scripts that automate the generation and publication of derivative packages. These scripts, such as auto.js and autopublish.js, are designed to create random package names and continuously republish them, thereby polluting the npm registry. The malicious payload alters critical metadata in package.json, which can lead to unauthorized access and exploitation of affected systems. This vulnerability poses significant risks to developers relying on npm packages, as it can compromise the integrity of their applications.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall pitra-61If 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-61 and any other packages associated with the tea.xyz token reward campaign. Monitor your package-lock.json file for any unauthorized changes and consider using tools like Vulert to keep track of vulnerabilities in your dependencies.
Conclusion
The pitra-61 package poses a significant threat due to its malicious code that modifies package metadata and floods the npm registry. It is crucial for developers to be vigilant about their dependencies and take immediate action to remove any affected packages. Utilizing tools like Vulert can enhance your security posture by providing real-time alerts for vulnerabilities.
See every vulnerability recorded for pitra-61 →
FAQ
pitra-61 is an npm package that is part of a malicious campaign aimed at inflating developer reputation scores through the publication of derivative packages.
The vulnerability can lead to unauthorized modifications in your package.json file, potentially compromising your application's integrity and security.
You should uninstall pitra-61 immediately using 'npm uninstall pitra-61' and review your other dependencies for similar vulnerabilities.
Regularly update your dependencies, use trusted packages, and monitor your projects with tools like Vulert to detect vulnerabilities in real-time.
Vulert is a tool that monitors and alerts for open-source vulnerabilities in your software using just the package-lock.json file. You can check if your application is affected by vulnerabilities without any installation.
