Malicious Code Injection in mass_mouse_z3n Package: A Threat to npm Ecosystem

mass_mouse_z3n Updated 27 Nov 2025

Summary

11/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-88317: Malicious code in mass_mouse_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 Penetration testing for web, API and mobile Manual testing by engineers who build software, not an auditor's checklist. Trusted by teams at Swift and Google Talk to Devnack

Background

The mass_mouse_z3n package is part of the npm ecosystem, which is widely used for JavaScript package management. It is often utilized in various projects to facilitate the integration of third-party libraries. However, this package has been identified as part of a malicious campaign that aims to exploit the npm registry by flooding it with derivative packages that inflate developer reputation scores for token rewards.

Vulnerability Detail

The vulnerability in the mass_mouse_z3n 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 designed to continuously republish variants, polluting the npm registry and potentially compromising the integrity of applications that depend on these packages. The malicious code is part of a broader scheme to manipulate the npm ecosystem for financial gain.

How To Fix

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

npm uninstall mass_mouse_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 mass_mouse_z3n package and replace it with a trusted alternative. Additionally, you can use the following command to uninstall the package: npm uninstall mass_mouse_z3n.

Conclusion

The mass_mouse_z3n package poses a significant threat to the npm ecosystem due to its malicious code that manipulates package metadata and floods the registry. It is essential for developers to be vigilant, remove affected packages, and utilize tools like Vulert to monitor their projects for vulnerabilities.

See every vulnerability recorded for mass_mouse_z3n →

Share this vulnerability

FAQ

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

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

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 signup.

You should uninstall the mass_mouse_z3n package immediately and monitor your project for any unusual behavior.

Yes, tools like Vulert can help monitor your dependencies for vulnerabilities using just the package-lock.json file.

How To Fix

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

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