Malicious Code Injection in poor_mongoose_z3n Package - npm Vulnerability

poor_mongoose_z3n Updated 27 Nov 2025

Summary

11/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-95931: Malicious code in poor_mongoose_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 poor_mongoose_z3n package is part of the npm ecosystem, typically used for various web development tasks. However, it has been identified as part of a malicious campaign that floods the npm registry with derivative packages. This package is designed to inflate developer reputation scores through automated scripts that republish variants of itself with altered metadata.

Vulnerability Detail

The vulnerability originates from the package being associated with the tea.xyz token reward campaign, which employs malicious scripts to modify package.json files. These scripts remove private flags, alter version numbers, and generate random package names, leading to pollution of the npm registry. This can result in security risks, as developers may unknowingly install compromised packages, leading to potential data breaches or system vulnerabilities.

How To Fix

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

npm uninstall poor_mongoose_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 remove the poor_mongoose_z3n package from your project by executing: npm uninstall poor_mongoose_z3n. This will prevent any malicious code from executing until a secure version is available.

Conclusion

The poor_mongoose_z3n package has been identified as a malicious entity within the npm ecosystem, posing significant risks to developers and their applications. It is crucial to take immediate action by updating or removing the package and utilizing tools like Vulert to monitor for vulnerabilities.

See every vulnerability recorded for poor_mongoose_z3n →

Share this vulnerability

FAQ

The poor_mongoose_z3n package is an npm package that has been identified as part of a malicious campaign aimed at inflating developer reputation scores.

The vulnerability can lead to the installation of compromised packages, which may introduce security risks, data breaches, or system vulnerabilities.

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.

If you are using the poor_mongoose_z3n package, you should uninstall it immediately and check for any updates or patches that may address the vulnerability.

To prevent future vulnerabilities, regularly audit your dependencies, use tools like Vulert for monitoring, and stay informed about security advisories related to the packages you use.

How To Fix

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

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