Malicious Code Injection in pitra-14: A Threat to npm Ecosystem
Summary
MAL-2025-164282: Malicious code in pitra-14 (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-14 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 manipulate developer reputation scores by flooding the registry with derivative packages. The malicious nature of pitra-14 lies in its ability to modify package metadata and publish numerous variants, thereby polluting the npm ecosystem.
Vulnerability Detail
The vulnerability in pitra-14 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. The malicious payload continuously republishes these variants, which can lead to a significant increase in the number of untrustworthy packages in the npm registry, potentially compromising the integrity of applications that rely on npm packages.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall pitra-14If 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-14 and any packages that depend on it. Regularly audit your dependencies using tools like npm audit to identify and mitigate risks associated with malicious packages.
Conclusion
The pitra-14 package poses a significant threat to the npm ecosystem due to its malicious capabilities to alter package metadata and flood the registry with untrustworthy variants. Immediate action is required to remove this package and safeguard your applications from potential risks.
See every vulnerability recorded for pitra-14 →
FAQ
pitra-14 is an npm package that has been identified as part of a malicious campaign to manipulate developer reputation scores in the npm registry.
The malicious code in pitra-14 can modify your package.json file, leading to the publication of untrustworthy packages and potentially compromising your application's integrity.
You should uninstall pitra-14 immediately using 'npm uninstall pitra-14' and check your package-lock.json for any references to this package.
You can use tools like npm audit or services like Vulert, which monitors your package-lock.json for vulnerabilities in real-time without requiring installation.
Yes, you can use the Vulert playground at Vulert Scanner to check if your application is affected by this vulnerability 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.
