Malicious Code Injection in shiny_marlin_z3n Package: A Threat to npm Users

shiny_marlin_z3n Updated 27 Nov 2025

Summary

11/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-96566: Malicious code in shiny_marlin_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 shiny_marlin_z3n package is part of the npm ecosystem, which is widely used for JavaScript package management. This package is associated with the tea.xyz token reward campaign, which has been known to flood the npm registry with malicious packages. Its primary function is to facilitate the automatic generation and publication of derivative packages, often with randomized names, to inflate developer reputation scores for token rewards. The presence of such malicious packages poses a significant risk to developers and users relying on npm for secure package management.

Vulnerability Detail

The vulnerability in the shiny_marlin_z3n package stems from its malicious payload that modifies the package.json file to remove private flags, alters version numbers, and generates random package names. This behavior is designed to continuously republish variants, polluting the npm registry and potentially leading to the installation of compromised packages by unsuspecting users. The origin of this vulnerability is linked to the tea.xyz token reward campaign, which employs autopublish scripts to automate the malicious activities.

How To Fix

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

npm uninstall shiny_marlin_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, consider removing the shiny_marlin_z3n package from your project until a secure version is confirmed. You can do this by running the following command: npm uninstall shiny_marlin_z3n. Additionally, monitor your package-lock.json file for any unauthorized changes.

Conclusion

The shiny_marlin_z3n package presents a significant security risk due to its malicious code injection capabilities. Developers should take immediate action to remove this package and monitor their projects for any unauthorized changes. Utilizing tools like Vulert can help maintain the security of your npm packages.

See every vulnerability recorded for shiny_marlin_z3n →

Share this vulnerability

FAQ

shiny_marlin_z3n is an npm package associated with the tea.xyz token reward campaign, known for flooding the npm registry with malicious packages.

The vulnerability can lead to unauthorized modifications in your package.json file, potentially allowing malicious code to be executed in your project.

If you have installed shiny_marlin_z3n, it is recommended to uninstall it immediately and check for any changes in your package-lock.json file.

Yes, you can use tools like 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 by this vulnerability without requiring any signup.

How To Fix

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

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