Malicious Code Injection in rolling_clownfish_0xrequest Package

rolling_clownfish_0xrequest Updated 18 Nov 2025

Summary

11/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-108186: Malicious code in rolling_clownfish_0xrequest (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 Penetration testing for web, API and mobile Manual testing by engineers who build software, not an auditor's checklist. Trusted by teams at Swift and Google Talk to Devnack

Background

The rolling_clownfish_0xrequest package is part of the npm ecosystem, which is widely used for JavaScript package management. This package was identified as part of a larger campaign that aimed to exploit the npm registry by flooding it with malicious packages. The primary function of this package, like many others in the campaign, is to facilitate token rewards through the tea.xyz protocol. However, its malicious nature compromises the integrity of the npm ecosystem.

Vulnerability Detail

The vulnerability originates from the rolling_clownfish_0xrequest package, which contains malicious code designed to modify the package.json file. This code removes private flags, alters version numbers, and generates random package names, leading to the automatic publication of derivative packages. The ramifications include pollution of the npm registry, potential security risks for developers using these packages, and a degradation of trust in the npm ecosystem. The malicious payload is part of a broader strategy to inflate developer reputation scores for token rewards.

How To Fix

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

npm uninstall rolling_clownfish_0xrequest

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, avoid using the rolling_clownfish_0xrequest package and monitor your dependencies for any unauthorized changes. Regularly check your package.json file for any modifications that may indicate malicious activity.

Conclusion

The rolling_clownfish_0xrequest package poses a significant risk due to its malicious code designed to manipulate project files and pollute the npm registry. It is essential for developers to remove this package and monitor their dependencies to maintain the integrity of their projects.

See every vulnerability recorded for rolling_clownfish_0xrequest →

Share this vulnerability

FAQ

It is an npm package that has been identified as part of a malicious campaign to exploit the npm registry.

You can use Vulert, which monitors and alerts for open-source vulnerabilities in your software. Check your application against the vulnerability using the Vulert playground at Vulert Scanner.

Using this package can lead to unauthorized modifications of your project files and potential security vulnerabilities.

Regularly audit your dependencies and use tools like Vulert to monitor for vulnerabilities in real-time.

Uninstall the package immediately and review your project for any unauthorized changes.

How To Fix

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

npm uninstall rolling_clownfish_0xrequest

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