Malicious Code Injection in moaning_fly_z3n Package

moaning_fly_z3n Updated 27 Nov 2025

Summary

11/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-88448: Malicious code in moaning_fly_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

The moaning_fly_z3n package is an npm module 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 has led to the creation of numerous derivative packages aimed at inflating developer reputation scores. The package's functionality is compromised by the presence of malicious scripts that alter its metadata and behavior.

Vulnerability Detail

The vulnerability in the moaning_fly_z3n package originates from its inclusion in a broader malicious campaign that utilizes autopublish scripts to generate and publish numerous derivative packages with randomized names. This behavior not only pollutes the npm registry but also modifies the package.json file to remove private flags and change version numbers, potentially leading to security risks and loss of control over package integrity. The malicious payload can affect developers who unknowingly use this package, leading to unintended consequences in their projects.

How To Fix

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

npm uninstall moaning_fly_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 monitor your package dependencies and avoid using any packages that are part of the tea.xyz token reward campaign. Regularly audit your npm packages using tools like npm audit to identify and address vulnerabilities.

Conclusion

The moaning_fly_z3n package poses a significant risk due to its malicious code designed to manipulate package metadata and publish unauthorized derivatives. It is crucial for developers to remove this package and monitor their dependencies to maintain the security and integrity of their projects.

See every vulnerability recorded for moaning_fly_z3n →

Share this vulnerability

FAQ

moaning_fly_z3n is an npm package that has been identified as part of a malicious campaign aimed at inflating developer reputation scores through the creation of numerous derivative packages.

The malicious code modifies the package.json file, removes private flags, and can lead to the publication of unauthorized packages, potentially compromising your project's integrity.

You should uninstall the moaning_fly_z3n package immediately using the command npm uninstall moaning_fly_z3n and review your project for any other potentially compromised packages.

Regularly audit your dependencies using tools like npm audit, and consider using Vulert to monitor your package-lock.json for real-time alerts on open-source vulnerabilities.

Vulert is a service that monitors your package-lock.json file for open-source vulnerabilities in real-time. You can use the Vulert playground to check if your application is affected by vulnerabilities without needing to sign up.

How To Fix

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

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