Malicious Code Injection in Tragic Carp Z3N: A Threat to npm Ecosystem
Summary
MAL-2025-98969: Malicious code in tragic_carp_z3n (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
Tragic Carp Z3N is an npm package that has been identified as part of a malicious campaign targeting the npm registry. This package is designed to manipulate the npm ecosystem by generating and publishing derivative packages with randomized names, aiming to inflate developer reputation scores for token rewards. Its functionality is compromised due to the presence of malicious scripts that alter package metadata and continuously republish variants, leading to pollution of the npm registry.
Vulnerability Detail
The vulnerability in Tragic Carp Z3N originates from its association with the tea.xyz token reward campaign, which employs autopublish scripts to modify package.json files. These scripts remove private flags, change version numbers, and create random package names, ultimately leading to the proliferation of malicious packages in the npm registry. The ramifications include potential security risks for developers who unknowingly use these packages, as well as a degradation of trust in the npm ecosystem due to the pollution of the registry.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall tragic_carp_z3nIf 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 Tragic Carp Z3N package and replace it with a trusted alternative that provides similar functionality. Always verify the integrity and reputation of packages before including them in your project.
Conclusion
The Tragic Carp Z3N package poses a significant threat to the npm ecosystem due to its malicious code that alters package metadata and proliferates harmful variants. It is essential for developers to be vigilant, remove affected packages, and utilize tools like Vulert to monitor for vulnerabilities in their projects.
See every vulnerability recorded for tragic_carp_z3n →
FAQ
Tragic Carp Z3N is an npm package that has been identified as part of a malicious campaign to manipulate the npm registry.
The vulnerability can lead to the inclusion of malicious code in your project, potentially compromising security and trust in the npm ecosystem.
You should uninstall the Tragic Carp Z3N package immediately using 'npm uninstall tragic_carp_z3n' and review your project's dependencies.
You can use Vulert to monitor and alert for open-source vulnerabilities in your software. It requires only your package-lock.json file for real-time alerts.
Yes, you can use the Vulert playground at Vulert Scanner to check if your application is affected by this vulnerability without any signup.
