Malicious Code Injection in super_manatee_z3n Package - npm Vulnerability

super_manatee_z3n Updated 27 Nov 2025

Summary

11/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-90798: Malicious code in super_manatee_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 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 super_manatee_z3n package is part of the npm ecosystem, primarily used for JavaScript development. It is often involved in various projects requiring package management and dependency handling. However, this package has been identified as part of a malicious campaign that exploits npm's publishing mechanisms, leading to significant security risks for developers and their applications.

Vulnerability Detail

The vulnerability in the super_manatee_z3n package stems from its association with a malicious campaign that floods the npm registry with derivative packages. These packages contain scripts designed to modify the package.json file, removing private flags and changing version numbers. This allows the package to continuously republish variants, polluting the npm registry and potentially compromising the integrity of applications that depend on it. The malicious payload can lead to unauthorized access, data breaches, and a loss of developer reputation.

How To Fix

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

npm uninstall super_manatee_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 prevent the installation of the super_manatee_z3n package by adding it to your project's .npmrc file with the following line: 'package-lock=false'. This will help avoid pulling in this malicious package until a fix is implemented.

Conclusion

The super_manatee_z3n package poses a significant security risk due to its malicious code that alters package metadata and repopulates the npm registry with compromised versions. It is essential for developers to take immediate action by removing the package and monitoring their projects for vulnerabilities.

See every vulnerability recorded for super_manatee_z3n →

Share this vulnerability

FAQ

The super_manatee_z3n package is an npm package used in JavaScript development, but it has been identified as part of a malicious campaign.

This vulnerability can lead to unauthorized modifications in your package.json file, potentially compromising your application's security and integrity.

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

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

You can use the Vulert playground at Vulert Scanner to check if your application is affected without needing to sign up.

How To Fix

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

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