Malicious Code Injection in pitra-47: A Threat to npm Packages
Summary
MAL-2025-164318: Malicious code in pitra-47 (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-47 is an npm package that has been identified as part of a malicious campaign targeting the npm ecosystem. This package is associated with the tea.xyz token reward initiative, which aims to inflate developer reputation scores through the automatic generation and publication of derivative packages. The malicious nature of pitra-47 lies in its ability to manipulate package metadata and proliferate harmful variants across the npm registry.
Vulnerability Detail
The vulnerability in pitra-47 originates from its design to execute autopublish scripts that modify the package.json file. This includes removing private flags, altering version numbers, and generating random package names, primarily themed around Indonesian culture. The continuous republishing of these variants leads to pollution of the npm registry, which can compromise the integrity of the ecosystem and potentially expose developers to security risks.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall pitra-47If 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-47 and any other packages that are part of the tea.xyz token reward campaign. Regularly audit your package.json and package-lock.json files to identify and remove any suspicious packages.
Conclusion
The pitra-47 package poses a significant threat to the npm ecosystem due to its malicious code and ability to pollute the registry. It is essential for developers to remain vigilant, promptly remove any affected packages, and utilize tools like Vulert to monitor for vulnerabilities in their projects.
See every vulnerability recorded for pitra-47 →
FAQ
pitra-47 is an npm package identified as part of a malicious campaign that modifies package metadata and floods the npm registry with harmful variants.
The presence of pitra-47 can compromise the integrity of your project by introducing malicious code and polluting the npm registry, which may lead to security vulnerabilities.
You should uninstall pitra-47 immediately using 'npm uninstall pitra-47' and audit your project for any other potentially harmful packages.
You can use tools like Vulert, which monitors your package-lock.json for open-source vulnerabilities in real-time. You can check your application for vulnerabilities using the Vulert playground without any signup.
Regularly audit your dependencies, use trusted packages, and consider using automated tools to monitor for vulnerabilities in your projects.
