Malicious Code Injection in tragic_cobra_z3n: A Threat to npm Ecosystem

tragic_cobra_z3n Updated 27 Nov 2025

Summary

11/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-97050: Malicious code in tragic_cobra_z3n (npm). Affected versions are not published. No fix is published. How to fix ↓

Free scan

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.

Check my app free

No signup required · Results in about 60 seconds

Upload your dependency manifest or SBOM

Drag & drop your file here or

Java Javascript PHP Python Go Rust Ruby Dart C/C++ Elixir CycloneDX SPDX

Upload a supported dependency manifest or SBOM. No installation or source-code access required.

See supported files and SBOM formats
SBOM sbom.json · bom.json · bom.xml · *.spdx.json · *.cdx.json · *.cdx.xml
Java pom.xml · gradle.lockfile · buildscript-gradle.lockfile
Javascript package-lock.json · yarn.lock · pnpm-lock.yaml
PHP composer.lock
Python poetry.lock · requirements.txt · Pipfile.lock
Go go.mod
Rust Cargo.lock
Ruby Gemfile.lock
Dart pubspec.lock
C/C++ conan.lock
Elixir mix.lock
Enter your work email to receive your report link.

Verify your email to view the full report and start 30 days of continuous monitoring. No credit card required.

Sponsored Devnack Your last release was probably never penetration tested Manual testing by engineers who build software, not an auditor's checklist. Trusted by teams at Swift and Google Talk to Devnack

Background

tragic_cobra_z3n 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 inflate developer reputation scores through the automatic generation and publication of derivative packages. The malicious nature of this package lies in its ability to manipulate package metadata, thereby posing a significant risk to developers and users relying on npm packages.

Vulnerability Detail

The vulnerability in tragic_cobra_z3n stems from its inclusion in a campaign that deploys autopublish scripts designed to create and publish numerous derivative packages with randomized names. This results in the alteration of package.json files, including the removal of private flags and modification of version numbers. The continuous republishing of these variants leads to pollution of the npm registry, which can compromise the integrity of the ecosystem and potentially introduce security risks to dependent projects.

How To Fix

This package is malicious. Remove it and rotate any credentials it could have accessed.

npm uninstall tragic_cobra_z3n

If 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_cobra_z3n package and instead look for alternative packages that provide similar functionality without the associated risks. Always verify the integrity and reputation of packages before including them in your project.

Conclusion

The tragic_cobra_z3n package poses a significant threat to the npm ecosystem due to its malicious code designed to manipulate package metadata and flood the registry. It is essential to remove this package from your projects and monitor your dependencies for vulnerabilities to maintain the security and integrity of your applications.

See every vulnerability recorded for tragic_cobra_z3n →

Share this vulnerability

FAQ

tragic_cobra_z3n is an npm package identified as part of a malicious campaign that manipulates package metadata and floods the npm registry with derivative packages.

The vulnerability can lead to the pollution of the npm registry, compromising the integrity of your project's dependencies and potentially introducing security risks.

You should uninstall the package immediately using 'npm uninstall tragic_cobra_z3n' and review your project's dependencies for any other potentially malicious packages.

You can use tools like Vulert, which monitors your package-lock.json file to alert you in real-time for open-source vulnerabilities. You can also check your application for vulnerabilities using the Vulert playground without any signup.

Yes, you should look for alternative packages that provide similar functionality but have a good reputation and are actively maintained.

How To Fix

This package is malicious. Remove it and rotate any credentials it could have accessed.

npm uninstall tragic_cobra_z3n

If 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 →

Subscribe to Vulert on Telegram
Daily digest of new CVEs, critical and high severity, affected packages and fixes — plus a weekly roundup.
Join the channel →
Help improve this record
Report an issue or send feedback