Malicious Code Injection in pitra-57: A Threat to npm Ecosystem
Summary
MAL-2025-164329: Malicious code in pitra-57 (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
Habilume
Habit tracker with a companion that grows with you
Complete habits, earn Lume Points, and watch your Lume grow as you stay consistent.
Background
The package pitra-57 is part of the npm ecosystem, which is widely used for JavaScript package management. This package is associated with the tea.xyz token reward campaign, which has been linked to a series of malicious activities aimed at inflating developer reputation scores. The functionality of pitra-57 has been compromised, making it a vector for malicious code that can affect other packages and the integrity of the npm registry.
Vulnerability Detail
The vulnerability in pitra-57 originates from its design to include autopublish scripts that automatically generate and publish derivative packages with randomized names. This malicious behavior modifies the package.json file by removing private flags, altering version numbers, and creating random package names, which leads to pollution of the npm registry. The ramifications include potential security risks for developers using these packages, as well as degradation of the npm ecosystem's reliability.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall pitra-57If 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 prevent the installation of pitra-57 by using the npm shrinkwrap feature or by explicitly excluding it in your package.json dependencies. Additionally, consider using the following command to audit your dependencies for vulnerabilities: npm audit.
Conclusion
The pitra-57 package poses a significant threat to the npm ecosystem due to its malicious code designed to manipulate package metadata and inflate developer reputation scores. It is crucial for developers to remove this package and regularly audit their dependencies to maintain the integrity of their projects.
See every vulnerability recorded for pitra-57 →
FAQ
pitra-57 is an npm package that has been identified as containing malicious code designed to manipulate the npm registry.
You can check your package.json or package-lock.json files for any references to pitra-57. Additionally, using tools like Vulert can help monitor your dependencies for vulnerabilities.
Using pitra-57 can lead to security vulnerabilities, including the potential for your project to be compromised by malicious code that alters package metadata and affects other dependencies.
Regularly audit your dependencies using npm audit, keep your packages updated, and consider using tools like Vulert to monitor for vulnerabilities in real-time.
Vulert is a service 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 using the Vulert playground without any signup.
Habilume
Habit tracker with a companion that grows with you
Complete habits, earn Lume Points, and watch your Lume grow as you stay consistent.
