Malicious Code Injection in outer_crocodile_z3n: A Threat to npm Packages

outer_crocodile_z3n Updated 27 Nov 2025

Summary

11/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-89334: Malicious code in outer_crocodile_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 Mobile apps built by Devnack Design, build and launch iOS and Android apps with a senior product team. From idea to store release Start a project

Background

The package 'outer_crocodile_z3n' is part of a broader ecosystem that has been exploited for malicious purposes. It is associated with the tea.xyz token reward campaign, which has led to the proliferation of numerous npm packages designed to inflate developer reputation scores. These packages often contain scripts that automate the generation and publication of derivative packages, which can lead to significant pollution of the npm registry.

Vulnerability Detail

The vulnerability in 'outer_crocodile_z3n' stems from its malicious payload that modifies the package.json file. It removes private flags, alters version numbers, and generates random package names, primarily themed around Indonesian culture. This behavior not only compromises the integrity of the package but also leads to the continuous republishing of variants, which can clutter the npm registry and mislead developers. The origin of this vulnerability is linked to the tea.xyz token reward campaign, which incentivizes such malicious activities.

How To Fix

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

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

Currently, there are no specific workarounds for this vulnerability other than removing the package from your project. It is advisable to monitor your dependencies regularly and avoid using packages that are part of the tea.xyz token reward campaign.

Conclusion

The 'outer_crocodile_z3n' package poses a significant threat due to its malicious code that modifies essential files and floods the npm registry. It is crucial for developers to be vigilant and remove any affected packages from their projects to maintain the integrity and security of their applications.

See every vulnerability recorded for outer_crocodile_z3n →

Share this vulnerability

FAQ

The main issue is that it contains malicious code that alters package.json files and floods the npm registry with derivative packages.

You can use Vulert, which monitors and alerts for open-source vulnerabilities in real-time. Visit Vulert Scanner to check your application without any signup.

You should uninstall the package immediately using 'npm uninstall outer_crocodile_z3n' and check for any other affected packages.

As of now, there are no known patches for this specific package. The best course of action is to remove it from your project.

Using this package can lead to the pollution of the npm registry, misrepresentation of developer reputation, and potential security risks for your application.

How To Fix

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

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