Malicious Code Injection in pitra-27: A Threat to npm Ecosystem
Summary
MAL-2025-164296: Malicious code in pitra-27 (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-27 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 through the automatic generation and publication of derivative packages. The malicious nature of pitra-27 lies in its ability to modify package metadata and republish variants, thereby polluting the npm ecosystem.
Vulnerability Detail
The vulnerability in pitra-27 originates from its design to execute autopublish scripts that alter the package.json file. This includes removing private flags, changing version numbers, and generating random package names, primarily themed around Indonesian culture. The continuous republishing of these variants can lead to a significant degradation of the npm registry's integrity, making it difficult for developers to trust the packages they use.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall pitra-27If 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 measure, you can avoid using pitra-27 and any packages that depend on it. Regularly audit your npm packages using 'npm audit' to identify and mitigate potential vulnerabilities.
Conclusion
The pitra-27 package poses a significant threat to the npm ecosystem due to its malicious behavior of modifying package metadata and republishing variants. It is essential for developers to remove this package from their projects and utilize tools like Vulert to monitor for vulnerabilities in their dependencies.
See every vulnerability recorded for pitra-27 →
FAQ
pitra-27 is an npm package that has been identified as part of a malicious campaign to inflate developer reputation scores through the automatic generation of derivative packages.
The pitra-27 package can modify your project's package.json file, remove private flags, and republish variants, which can lead to a polluted npm registry and potential security risks.
You should uninstall pitra-27 immediately using the command 'npm uninstall pitra-27' and audit your project for any other vulnerabilities.
You can use tools like Vulert, which monitors your package-lock.json file for open-source vulnerabilities in real-time. You can also check your application against vulnerabilities using the Vulert playground without any signup.
Regularly audit your dependencies, use trusted packages, and keep your software updated to minimize the risk of vulnerabilities in your projects.
