Malicious Code Injection in blushing_mule_z3n: A Threat to npm Users

blushing_mule_z3n Updated 27 Nov 2025

Summary

11/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-93408: Malicious code in blushing_mule_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 Lume, the Habilume companion Habilume Habit tracker with a companion that grows with you Complete habits, earn Lume Points, and watch your Lume grow as you stay consistent. App Store Google Play

Background

blushing_mule_z3n is an npm package 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 aims to inflate developer reputation scores by flooding the registry with derivative packages. The package's functionality is compromised, making it a vector for malicious activities.

Vulnerability Detail

The vulnerability stems from the presence of malicious code within the blushing_mule_z3n package. This code is designed to modify the package.json file by removing private flags, altering version numbers, and generating random package names. The malicious payload continuously republishes these variants, polluting the npm registry and potentially leading to security risks for users who inadvertently install these packages. The origin of this vulnerability is linked to the tea.xyz token reward campaign, which exploits npm's publishing mechanisms.

How To Fix

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

npm uninstall blushing_mule_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 blushing_mule_z3n package and replace it with a trusted alternative. Regularly audit your npm packages to ensure that no malicious packages are present in your project.

Conclusion

The blushing_mule_z3n package poses a significant threat to npm users due to its malicious code designed to manipulate package metadata and pollute the npm registry. Users are advised to uninstall this package and monitor their dependencies closely. Utilizing tools like Vulert can help in identifying vulnerabilities in real-time.

See every vulnerability recorded for blushing_mule_z3n →

Share this vulnerability

FAQ

blushing_mule_z3n is an npm package that has been identified as part of a malicious campaign to inflate developer reputation scores through the creation of derivative packages.

The malicious code modifies your package.json file, removes private flags, and republishes variants, which can lead to security vulnerabilities and pollution of the npm registry.

You can use Vulert, which monitors and alerts for open-source vulnerabilities in real-time. Visit Vulert Scanner to check if your application is affected without requiring any installation.

If you have installed blushing_mule_z3n, you should uninstall it immediately using the command npm uninstall blushing_mule_z3n and review your project for any other potentially malicious packages.

Currently, there is no patched version of blushing_mule_z3n available. The best course of action is to remove the package and monitor for updates from trusted sources.

Sponsored Lume, the Habilume companion Habilume Habit tracker with a companion that grows with you Complete habits, earn Lume Points, and watch your Lume grow as you stay consistent. App Store Google Play

How To Fix

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

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