Malicious Code Injection in consistent_stoat_z3n Package

consistent_stoat_z3n Updated 24 Nov 2025

Summary

11/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-100884: Malicious code in consistent_stoat_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 consistent_stoat_z3n package is part of the npm ecosystem, which is widely used for JavaScript package management. It is often utilized in various applications to enhance functionality and streamline development processes. However, this package has been identified as part of a malicious campaign that floods npm with harmful packages, designed to manipulate developer reputation scores for token rewards.

Vulnerability Detail

The vulnerability in the consistent_stoat_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 intended to inflate developer reputation scores by continuously republishing variants of the package, thereby polluting the npm registry. The malicious payload can lead to significant security risks, including unauthorized access to sensitive data and the potential for further exploitation of affected applications.

How To Fix

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

npm uninstall consistent_stoat_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 prevent the installation of the malicious package by using npm's package-lock.json file to lock your dependencies. Ensure that your project does not include the consistent_stoat_z3n package or any of its derivatives. Additionally, consider using tools like Vulert to monitor your dependencies for vulnerabilities.

Conclusion

The consistent_stoat_z3n package poses a significant security risk due to its malicious code that modifies project dependencies. It is crucial to uninstall this package and monitor your application for vulnerabilities using tools like Vulert. Staying informed and proactive can help mitigate potential threats.

See every vulnerability recorded for consistent_stoat_z3n →

Share this vulnerability

FAQ

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

The vulnerability can lead to unauthorized modifications in your project's dependencies, potentially exposing sensitive data and creating security risks.

You should uninstall the consistent_stoat_z3n package immediately and monitor your project for any unauthorized changes.

You can use Vulert, which monitors your package-lock.json file for open-source vulnerabilities in real-time without requiring access to your code.

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

How To Fix

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

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