Malicious Code Injection in embarrassing_catshark_z3n Package

embarrassing_catshark_z3n Updated 27 Nov 2025

Summary

11/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-94231: Malicious code in embarrassing_catshark_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 embarrassing_catshark_z3n package is part of the npm ecosystem, which is widely used for JavaScript development. It is designed to facilitate various functionalities within applications. However, this package has been identified as part of a malicious campaign that exploits npm's publishing capabilities to create and distribute harmful variants, thereby compromising the integrity of the npm registry.

Vulnerability Detail

The vulnerability originates from the package being associated with a token reward campaign that floods npm with malicious packages. These packages contain scripts that automatically modify the package.json file to remove private flags, change version numbers, and generate random package names. This behavior leads to the pollution of the npm registry and can inflate developer reputation scores fraudulently, posing significant risks to developers and users relying on the integrity of npm packages.

How To Fix

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

npm uninstall embarrassing_catshark_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, avoid using the embarrassing_catshark_z3n package and consider using alternative packages that provide similar functionality without the associated risks. Additionally, regularly audit your npm packages using tools like npm audit to identify and mitigate vulnerabilities.

Conclusion

The embarrassing_catshark_z3n package poses a significant risk due to its malicious code injection capabilities. It is crucial for developers to be vigilant and remove any affected packages from their projects. Regular audits and monitoring tools like Vulert can help maintain the security of your applications.

See every vulnerability recorded for embarrassing_catshark_z3n →

Share this vulnerability

FAQ

It is an npm package that has been identified as part of a malicious campaign to flood the npm registry with harmful variants.

The vulnerability can lead to the injection of malicious code, which may compromise your application's security and integrity.

You should uninstall the embarrassing_catshark_z3n package immediately and check for any alternative packages that can fulfill your requirements.

You can use tools like npm audit or services like Vulert, which monitors your package-lock.json for vulnerabilities in real-time without requiring code access.

Yes, you can use the Vulert playground at Vulert Scanner to check if your application is affected by this vulnerability without any signup.

How To Fix

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

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