Malicious Code Injection in mere_catshark_0xrequest Package

mere_catshark_0xrequest Updated 24 Nov 2025

Summary

11/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-105801: Malicious code in mere_catshark_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 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 mere_catshark_0xrequest package is part of the npm ecosystem, often utilized for various JavaScript functionalities. However, it has been identified as part of a malicious campaign that floods the npm registry with derivative packages. These packages are designed to inflate developer reputation scores for token rewards, making them a significant threat to developers and users alike.

Vulnerability Detail

The vulnerability in the mere_catshark_0xrequest package stems from its involvement in a malicious campaign that modifies the package.json file to remove private flags and alters version numbers. It generates random package names and continuously republishes variants, leading to pollution of the npm registry. This can result in developers inadvertently using compromised packages, exposing their applications to potential security risks and instability.

How To Fix

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

npm uninstall mere_catshark_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 workaround, avoid using the mere_catshark_0xrequest package and look for alternative packages that provide similar functionality without the associated risks. Always review the package's reputation and community feedback before integrating it into your project.

Conclusion

The mere_catshark_0xrequest package poses a significant threat due to its malicious code designed to manipulate npm registry entries. Developers must take proactive measures to remove this package and monitor their projects for vulnerabilities to ensure the security and integrity of their applications.

See every vulnerability recorded for mere_catshark_0xrequest →

Share this vulnerability

FAQ

It is an npm package that has been identified as part of a malicious campaign aimed at inflating developer reputation scores through the publication of compromised packages.

You can check your package-lock.json file for the mere_catshark_0xrequest entry or use tools like Vulert to monitor your dependencies for vulnerabilities.

Using this package can expose your application to security vulnerabilities, instability, and potential data breaches due to the malicious modifications it implements.

Yes, you can use Vulert, which monitors and alerts you in real-time for open-source vulnerabilities using just your package-lock.json file.

Immediately uninstall the package and replace it with a secure alternative. Review your dependencies to ensure no other malicious packages are present.

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 mere_catshark_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