Malicious Code Vulnerability in pitra-60: npm Package Exploit
Summary
MAL-2025-164333: Malicious code in pitra-60 (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 pitra-60 package is part of the tea.xyz token reward campaign, which has been known to flood the npm ecosystem with malicious packages. These packages are designed to manipulate developer reputation scores by automatically generating and publishing derivative packages with randomized names. The pitra-60 package specifically contains scripts that alter package metadata, making it a significant threat to developers and the integrity of the npm registry.
Vulnerability Detail
The vulnerability in the pitra-60 package originates from its inclusion in a campaign that uses autopublish scripts to create and publish numerous derivative packages. These scripts modify the package.json file to remove private flags, change version numbers, and generate random package names, leading to pollution of the npm registry. This can result in developers unintentionally using compromised packages, which may lead to further security risks and a loss of trust in the npm ecosystem.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall pitra-60If 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 the pitra-60 package and look for alternative packages that provide similar functionality without the associated risks. Additionally, you can monitor your project's dependencies using tools like Vulert, which can alert you to vulnerabilities in real-time.
Conclusion
The pitra-60 package poses a significant threat due to its malicious code designed to manipulate npm's package registry. Developers should take immediate action to remove this package and monitor their dependencies for vulnerabilities. Utilizing tools like Vulert can provide real-time alerts and help maintain the security of your applications.
See every vulnerability recorded for pitra-60 →
FAQ
The pitra-60 package is part of a malicious campaign that aims to inflate developer reputation scores by flooding the npm registry with derivative packages.
The vulnerability can lead to the inclusion of compromised packages in your project, which may introduce security risks and affect the integrity of your application.
If you have used pitra-60, it is crucial to remove it from your project and check for any other affected packages. Consider using tools like Vulert to monitor for vulnerabilities.
Yes, you can use the Vulert playground at Vulert Scanner to check if your application is affected by this vulnerability without requiring any signup.
Currently, there are no known patches for the pitra-60 package. It is advised to remove the package and monitor for any updates.
Habilume
Habit tracker with a companion that grows with you
Complete habits, earn Lume Points, and watch your Lume grow as you stay consistent.
