Malicious Code Injection in querulous_damselfly_z3n: A Threat to npm Packages

querulous_damselfly_z3n Updated 27 Nov 2025

Summary

11/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-96146: Malicious code in querulous_damselfly_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 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

querulous_damselfly_z3n is an npm package that has been identified as part of a malicious campaign targeting the npm ecosystem. 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 and proliferate harmful variants across the npm registry.

Vulnerability Detail

The vulnerability in querulous_damselfly_z3n originates from its design to include autopublish scripts that modify the package.json file. These modifications remove private flags, alter version numbers, and generate random package names, leading to the continuous republishing of these variants. This behavior not only pollutes the npm registry but also poses risks to developers who may unknowingly incorporate these malicious packages into their projects, potentially compromising their applications.

How To Fix

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

npm uninstall querulous_damselfly_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 measure, you can prevent the installation of this malicious package by using npm's package-lock.json file to monitor dependencies. Ensure that your package-lock.json does not include querulous_damselfly_z3n. You can also utilize tools like Vulert to monitor your dependencies for vulnerabilities in real-time.

Conclusion

The querulous_damselfly_z3n package poses a significant threat to the npm ecosystem due to its malicious code that modifies package metadata and proliferates harmful variants. It is crucial for developers to be vigilant, regularly update their dependencies, and utilize monitoring tools like Vulert to safeguard their applications from such vulnerabilities.

See every vulnerability recorded for querulous_damselfly_z3n →

Share this vulnerability

FAQ

querulous_damselfly_z3n is an npm package identified as part of a malicious campaign that modifies package metadata to inflate developer reputation scores.

The vulnerability can lead to the inclusion of malicious packages in your project, which may compromise the security and integrity of your application.

You should uninstall the package immediately using the command 'npm uninstall querulous_damselfly_z3n' and review your project's dependencies for any other vulnerabilities.

Yes, regularly monitor your dependencies using tools like Vulert, which can alert you to open-source vulnerabilities in real-time without requiring code access.

You can use the Vulert playground at Vulert Scanner to check if your application is affected by this vulnerability without needing to sign up.

How To Fix

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

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