Malicious Code Injection in full_rattlesnake_z3n Package

full_rattlesnake_z3n Updated 27 Nov 2025

Summary

11/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-94628: Malicious code in full_rattlesnake_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 full_rattlesnake_z3n package is part of the npm ecosystem and is associated with the tea.xyz token reward campaign. It is designed to facilitate the automatic generation and publication of derivative packages. This package, like others in the campaign, aims to inflate developer reputation scores for token rewards by creating numerous variants of itself with randomized names.

Vulnerability Detail

The vulnerability in the full_rattlesnake_z3n package stems from its malicious code, 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 these variants, which pollutes the npm registry and can compromise the integrity of the ecosystem. The malicious payload is part of a larger scheme to exploit the npm registry for token rewards.

How To Fix

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

npm uninstall full_rattlesnake_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 avoid using the full_rattlesnake_z3n package and monitor your project for any instances of its usage. Additionally, consider using tools like Vulert to monitor your package-lock.json for vulnerabilities in real-time.

Conclusion

The full_rattlesnake_z3n package contains malicious code that poses a significant risk to projects using it. Immediate action is required to uninstall the package and prevent further issues. Utilizing tools like Vulert can help maintain the security of your dependencies.

See every vulnerability recorded for full_rattlesnake_z3n →

Share this vulnerability

FAQ

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

The malicious code modifies your package.json, removes private flags, and creates numerous variants that can clutter the npm registry and affect your project's integrity.

You should uninstall the full_rattlesnake_z3n package immediately using the command: npm uninstall full_rattlesnake_z3n.

Yes, regularly monitor your dependencies using tools like Vulert, which can alert you to vulnerabilities in real-time without requiring code access.

You can use the Vulert playground at Vulert Scanner to check your application for vulnerabilities without needing to sign up.

How To Fix

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

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