Malicious Code Injection in repulsive_clownfish_z3n: A Threat to npm Packages

repulsive_clownfish_z3n Updated 27 Nov 2025

Summary

11/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-89932: Malicious code in repulsive_clownfish_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 Lume, the Habilume companion Habilume Habit tracker with a companion that grows with you Complete habits, earn Lume Points, and watch your Lume grow as you stay consistent. App Store Google Play

Background

The package 'repulsive_clownfish_z3n' is part of the npm ecosystem, which is widely used for JavaScript package management. This package is associated with the tea.xyz token reward campaign, which has been known to flood the npm registry with malicious packages. These packages often contain scripts designed to manipulate package metadata and inflate developer reputation scores, posing a significant risk to developers and users alike.

Vulnerability Detail

The vulnerability in 'repulsive_clownfish_z3n' originates from its design to include autopublish scripts that modify the package.json file. These scripts remove private flags, alter version numbers, and generate random package names, leading to the continuous republishing of variants that pollute the npm registry. This malicious behavior can compromise the integrity of the npm ecosystem, potentially leading to security risks for applications relying on these packages.

How To Fix

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

npm uninstall repulsive_clownfish_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 'repulsive_clownfish_z3n' package and look for alternative packages that provide similar functionality without the associated risks. Always verify the integrity of the packages you are using.

Conclusion

The 'repulsive_clownfish_z3n' package poses a significant threat due to its malicious code designed to manipulate npm package metadata. It is crucial for developers to remove this package and monitor their dependencies for vulnerabilities. Utilizing tools like Vulert can help in maintaining the security of your applications.

See every vulnerability recorded for repulsive_clownfish_z3n →

Share this vulnerability

FAQ

'repulsive_clownfish_z3n' is an npm package that has been identified as malicious, designed to manipulate package metadata for fraudulent purposes.

The vulnerability can lead to the introduction of malicious code into your application, potentially compromising its security and integrity.

If you have installed 'repulsive_clownfish_z3n', you should uninstall it immediately using 'npm uninstall repulsive_clownfish_z3n' and review your dependencies for any other malicious packages.

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

Yes, you should look for reputable packages that provide similar functionality but have a verified history and community support.

Sponsored Lume, the Habilume companion Habilume Habit tracker with a companion that grows with you Complete habits, earn Lume Points, and watch your Lume grow as you stay consistent. App Store Google Play

How To Fix

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

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