Malicious Code Injection in Respectable Dragon Z3N Package

respectable_dragon_z3n Updated 27 Nov 2025

Summary

11/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-89947: Malicious code in respectable_dragon_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

The 'respectable_dragon_z3n' package is part of the npm ecosystem, often utilized in various JavaScript applications. It is associated with the tea.xyz token reward campaign, which has been known to flood the npm registry with numerous packages. This package, like others in the campaign, is designed to manipulate npm's publishing system, potentially affecting developers' reputations and the integrity of the npm registry.

Vulnerability Detail

The vulnerability in 'respectable_dragon_z3n' originates from its malicious code that modifies the package.json file. It removes private flags, alters version numbers, and generates random package names, leading to the continuous republishing of variants. This behavior can pollute the npm registry, inflate developer reputation scores fraudulently, and compromise the integrity of the software supply chain.

How To Fix

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

npm uninstall respectable_dragon_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 remove the 'respectable_dragon_z3n' package from your project by executing: 'npm uninstall respectable_dragon_z3n'. This will prevent any malicious activities associated with this package until a secure version is available.

Conclusion

The 'respectable_dragon_z3n' package poses significant risks due to its malicious code that alters package metadata and repackages itself. It is crucial to monitor your dependencies and take necessary actions to protect your applications from such vulnerabilities.

See every vulnerability recorded for respectable_dragon_z3n →

Share this vulnerability

FAQ

The package contains malicious code that modifies package.json files and repackages itself under different names, which can lead to npm registry pollution.

You can use Vulert, which monitors open-source vulnerabilities in real-time. Visit Vulert Scanner to check your application without needing to sign up.

Using this package can compromise your application's integrity, inflate developer reputation scores fraudulently, and expose your project to further vulnerabilities.

Regularly audit your dependencies using tools like Vulert and keep your packages updated to the latest secure versions.

If an immediate update is not possible, consider removing the package from your project to mitigate risks until a secure version is released.

How To Fix

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

npm uninstall respectable_dragon_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