Malicious Code Injection in pitra-36: A Threat to npm Packages
Summary
MAL-2025-164306: Malicious code in pitra-36 (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
pitra-36 is an npm package that has been identified as part of a malicious campaign targeting the npm registry. This package, like others in the tea.xyz token reward scheme, is designed to manipulate the npm ecosystem by generating and publishing derivative packages with randomized names. Its primary functionality is to inflate developer reputation scores for token rewards, but this comes at the cost of security and integrity within the npm registry.
Vulnerability Detail
The vulnerability in pitra-36 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. The malicious payload continuously republishes these variants, leading to pollution of the npm registry. This can result in developers unknowingly using compromised packages, which may lead to further exploitation or data breaches.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall pitra-36If 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 remove the pitra-36 package from your project by executing: 'npm uninstall pitra-36'. This will prevent any malicious code from executing until a secure version is available.
Conclusion
The pitra-36 package poses a significant threat due to its malicious code that alters package metadata and floods the npm registry with compromised packages. It is crucial for developers to take immediate action by uninstalling the package and monitoring for updates. Utilizing tools like Vulert can help maintain the security of your projects.
See every vulnerability recorded for pitra-36 →
FAQ
pitra-36 is an npm package involved in a malicious campaign that aims to inflate developer reputation scores through the creation of derivative packages.
The vulnerability can lead to the introduction of malicious code into your project, potentially compromising security and functionality.
You should uninstall the package immediately and monitor for any updates or patches that may address the vulnerability.
Yes, you can use Vulert to monitor and alert for open-source vulnerabilities in your software. Visit Vulert Scanner to check your application without any signup.
Regularly audit your dependencies and use tools like Vulert to monitor for vulnerabilities in real-time.
Habilume
Habit tracker with a companion that grows with you
Complete habits, earn Lume Points, and watch your Lume grow as you stay consistent.
