Malicious Code Injection in apparent_damselfly_z3n Package

apparent_damselfly_z3n Updated 27 Nov 2025

Summary

11/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-99512: Malicious code in apparent_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 Devnack Mobile apps built by Devnack Design, build and launch iOS and Android apps with a senior product team. From idea to store release Start a project

Background

The apparent_damselfly_z3n package is part of the npm ecosystem, which is widely used for JavaScript package management. This package was identified as part of a malicious campaign that aimed to exploit npm by flooding it with derivative packages. These packages are designed to inflate developer reputation scores through automated publishing scripts, which can lead to significant pollution of the npm registry.

Vulnerability Detail

The vulnerability in the apparent_damselfly_z3n package originates from its association with the tea.xyz token reward campaign. It contains malicious scripts that modify the package.json file to remove private flags, alter version numbers, and generate random package names. This behavior not only compromises the integrity of the npm registry but also poses risks to developers who may unknowingly use these compromised packages, leading to potential security breaches and loss of trust in the ecosystem.

How To Fix

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

npm uninstall apparent_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 workaround, you can avoid using the apparent_damselfly_z3n package and any packages that may have been derived from it. Regularly audit your dependencies using tools like npm audit to identify and address vulnerabilities in your project.

Conclusion

The apparent_damselfly_z3n package poses a significant threat due to its malicious code designed to manipulate npm registry entries. It is crucial for developers to remain vigilant, regularly audit their dependencies, and utilize tools like Vulert to ensure their projects are secure from such vulnerabilities.

See every vulnerability recorded for apparent_damselfly_z3n →

Share this vulnerability

FAQ

It is an npm package that has been identified as part of a malicious campaign to exploit the npm registry.

Using this package can compromise your project's integrity and expose it to security risks, including unauthorized access and data breaches.

You should uninstall the apparent_damselfly_z3n package immediately and review your project's dependencies for any other malicious packages.

You can use tools like Vulert, which monitors your package-lock.json file for open-source vulnerabilities in real-time without requiring installation.

Yes, you can use the Vulert playground at Vulert Scanner to check if your application is affected by this vulnerability without signing up.

How To Fix

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

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