Malicious Code Injection in financial_alligator_z3n Package

financial_alligator_z3n Updated 24 Nov 2025

Summary

11/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-102714: Malicious code in financial_alligator_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 Your last release was probably never penetration tested Manual testing by engineers who build software, not an auditor's checklist. Trusted by teams at Swift and Google Talk to Devnack

Background

The financial_alligator_z3n package is part of the npm ecosystem, often used in JavaScript applications. It is designed to facilitate various functionalities within the npm framework. However, this package has been identified as part of a malicious campaign that exploits npm's publishing capabilities, leading to potential security risks for developers and their applications.

Vulnerability Detail

The vulnerability in the financial_alligator_z3n package stems from its association with the tea.xyz token reward campaign. This campaign has been known to flood the npm registry with packages that contain malicious scripts. Specifically, the package includes autopublish scripts that modify the package.json file, removing private flags, altering version numbers, and generating random package names. This behavior can lead to the pollution of the npm registry and inflate developer reputation scores fraudulently. The malicious payload poses significant 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 financial_alligator_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 workaround, you can temporarily avoid using the financial_alligator_z3n package and look for alternative packages that provide similar functionality without the associated risks. Additionally, ensure that your package-lock.json is monitored for any unauthorized changes.

Conclusion

The financial_alligator_z3n package poses a significant security risk due to its malicious code designed to exploit npm's publishing capabilities. Immediate action is required to remove this package and monitor your application for any unauthorized changes. Utilizing tools like Vulert can assist in maintaining the security of your open-source dependencies.

See every vulnerability recorded for financial_alligator_z3n →

Share this vulnerability

FAQ

The financial_alligator_z3n package is an npm package that has been identified as part of a malicious campaign, designed to exploit npm's publishing features.

This vulnerability can lead to unauthorized modifications in your package.json file, potentially exposing your application to further security risks and malicious activities.

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

Yes, tools like Vulert can monitor your package-lock.json file for open-source vulnerabilities in real-time without requiring code access or installation.

You can use the Vulert playground at Vulert Scanner to check if your application is affected by this vulnerability without needing to sign up.

How To Fix

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

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