Malicious Code Injection in 'close_dragon_dumbs' Package - npm Vulnerability

close_dragon_dumbs Updated 24 Nov 2025

Summary

11/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-100606: Malicious code in close_dragon_dumbs (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 MarkAI Find prospects already talking about the problem you solve AI watches the communities your customers use to find qualified prospects, then alerts you when a conversation is worth joining. See MarkAI

Background

The 'close_dragon_dumbs' package is part of the npm ecosystem, which is widely used for JavaScript package management. This package, like many others, is intended to facilitate the development and deployment of applications by providing reusable code. However, it has been identified as part of a malicious campaign that floods the npm registry with harmful packages designed to manipulate developer reputation scores through automated publishing scripts.

Vulnerability Detail

The vulnerability in the 'close_dragon_dumbs' package stems from its association with a malicious campaign that modifies the package.json file to remove private flags, alters version numbers, and generates random package names. This behavior is intended to inflate developer reputation scores for token rewards in the tea.xyz protocol. The malicious payload continuously republishes variants of the package, polluting the npm registry and potentially leading to security risks for developers who unknowingly use these compromised packages.

How To Fix

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

npm uninstall close_dragon_dumbs

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 'close_dragon_dumbs' package altogether. If it is already included in your project, remove it by running: 'npm uninstall close_dragon_dumbs'. This will help mitigate any immediate risks associated with the malicious code.

Conclusion

The 'close_dragon_dumbs' package poses a significant security risk due to its malicious code designed to manipulate npm registry reputation scores. It is crucial to take immediate action by updating or removing this package to safeguard your project from potential threats.

See every vulnerability recorded for close_dragon_dumbs →

Share this vulnerability

FAQ

The 'close_dragon_dumbs' package is an npm package that has been identified as part of a malicious campaign aimed at manipulating developer reputation scores.

The vulnerability can lead to the injection of malicious code into your project, potentially compromising its security and integrity.

If you have installed the 'close_dragon_dumbs' package, it is recommended to uninstall it immediately and check for any other affected packages.

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

Regularly update your dependencies, use security monitoring tools like Vulert, and review the packages you include in your project to avoid malicious ones.

How To Fix

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

npm uninstall close_dragon_dumbs

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