Malicious Code Injection in formidable_capybara_z3n: A Threat to npm Packages

formidable_capybara_z3n Updated 27 Nov 2025

Summary

11/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-94576: Malicious code in formidable_capybara_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

formidable_capybara_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 by malicious scripts that alter its metadata and behavior.

Vulnerability Detail

The vulnerability in formidable_capybara_z3n stems from its inclusion in a campaign that deploys autopublish scripts designed to manipulate package.json files. These scripts remove private flags, alter version numbers, and generate random package names, leading to the pollution of the npm registry. This not only compromises the integrity of the package but also poses a risk to developers who may unknowingly use these malicious variants, potentially leading to security breaches and loss of trust in the npm ecosystem.

How To Fix

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

npm uninstall formidable_capybara_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 formidable_capybara_z3n package and look for alternative packages that provide similar functionality without the associated risks. Always verify the integrity of the packages you choose to include in your project.

Conclusion

The formidable_capybara_z3n package poses a significant security risk due to its malicious code injection. It is crucial for developers to be vigilant about the packages they use and to take immediate action to remove any compromised packages. Utilizing tools like Vulert can help in monitoring and maintaining the security of your projects.

See every vulnerability recorded for formidable_capybara_z3n →

Share this vulnerability

FAQ

formidable_capybara_z3n is an npm package that has been linked to a malicious campaign aimed at manipulating the npm registry.

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

You should uninstall the formidable_capybara_z3n package immediately and check your project for any potential security issues.

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

Yes, you should look for other reputable npm packages that provide similar functionality without the associated risks.

How To Fix

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

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