Malicious Code Injection in formidable_bear_z3n: A Threat to npm Ecosystem

formidable_bear_z3n Updated 27 Nov 2025

Summary

11/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-94575: Malicious code in formidable_bear_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 formidable_bear_z3n package is part of a broader campaign that exploits the npm registry, specifically targeting developers involved in the tea.xyz token reward initiative. This package is designed to automate the generation and publication of derivative packages, which can mislead users and inflate developer reputation scores. Its functionality is compromised by malicious scripts that manipulate package metadata.

Vulnerability Detail

The vulnerability originates from the package's association with the tea.xyz token reward campaign, which has been identified as a source of malicious npm packages. The malicious payload in formidable_bear_z3n modifies the package.json file to remove private flags, alters version numbers, and generates random package names. This behavior leads to the continuous republishing of variants, polluting the npm registry and potentially compromising the integrity of dependent projects.

How To Fix

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

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

Conclusion

The formidable_bear_z3n package poses a significant risk due to its malicious code that alters package metadata and repopulates the npm registry with harmful variants. It is essential to take immediate action by updating or removing the package to safeguard your projects.

See every vulnerability recorded for formidable_bear_z3n →

Share this vulnerability

FAQ

formidable_bear_z3n is an npm package that has been identified as part of a malicious campaign aimed at manipulating the npm registry.

The vulnerability can lead to the injection of malicious code, which may compromise your project's integrity and security.

You should uninstall the package immediately and monitor for any updates or patches that address the vulnerability.

You can use tools like Vulert, which monitors your package-lock.json for open-source vulnerabilities in real-time. You can check your application using the Vulert playground without any signup.

Regularly updating your dependencies, using vulnerability scanning tools, and being cautious about the packages you include can help mitigate risks.

How To Fix

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

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