Malicious Code Injection in rotten_narwhal_z3n Package

rotten_narwhal_z3n Updated 27 Nov 2025

Summary

11/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-96401: Malicious code in rotten_narwhal_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 rotten_narwhal_z3n package is part of the npm ecosystem and is associated with the tea.xyz token reward campaign. This package is designed to facilitate the automatic generation and publication of derivative packages, which can inflate developer reputation scores for token rewards. However, it has been identified as containing malicious code that compromises the integrity of the npm registry.

Vulnerability Detail

The vulnerability in the rotten_narwhal_z3n package originates from its malicious payload, which modifies the package.json file to remove private flags, alters version numbers, and generates random package names. This behavior leads to the continuous republishing of variants, effectively polluting the npm registry and potentially impacting other developers and users relying on the integrity of the npm ecosystem.

How To Fix

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

npm uninstall rotten_narwhal_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 rotten_narwhal_z3n package by using the following command to uninstall it: npm uninstall rotten_narwhal_z3n. Additionally, you can monitor your project for vulnerabilities using tools like Vulert, which can alert you in real-time for open-source vulnerabilities without requiring code access.

Conclusion

The rotten_narwhal_z3n package contains a significant vulnerability due to its malicious code, which can compromise the integrity of the npm registry. It is crucial to take immediate action by updating or removing the package and utilizing tools like Vulert for ongoing monitoring of vulnerabilities in your projects.

See every vulnerability recorded for rotten_narwhal_z3n →

Share this vulnerability

FAQ

rotten_narwhal_z3n is an npm package associated with the tea.xyz token reward campaign, designed to generate and publish derivative packages.

The malicious code modifies your package.json file and can lead to the pollution of the npm registry, affecting the integrity of your project and potentially introducing security risks.

Yes, you can use Vulert to monitor your application for vulnerabilities. You can check for affected packages using their playground at Vulert Scanner.

If no patched version is available, it is advisable to remove the rotten_narwhal_z3n package from your project to mitigate the risk.

Regularly monitor your dependencies using tools like Vulert and keep your packages updated to the latest secure versions.

How To Fix

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

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