Malicious Code Injection in rational_ladybug_z3n: A Threat to npm Packages

rational_ladybug_z3n Updated 27 Nov 2025

Summary

11/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-98900: Malicious code in rational_ladybug_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 Mobile apps built by Devnack Design, build and launch iOS and Android apps with a senior product team. From idea to store release Start a project

Background

The package 'rational_ladybug_z3n' is part of the npm ecosystem and is associated with the tea.xyz token reward campaign. This package is designed to interact with the npm registry, potentially inflating developer reputation scores through automated publishing of derivative packages. Its functionality is compromised due to the presence of malicious scripts that manipulate package metadata.

Vulnerability Detail

The vulnerability originates from a malicious payload embedded within the 'rational_ladybug_z3n' package. This payload modifies the package.json file by removing private flags, altering version numbers, and generating random package names. The scripts are designed to continuously republish these variants, leading to pollution of the npm registry and potential exploitation of developers' reputations. The malicious nature of this package poses significant risks, including unauthorized access to sensitive data and disruption of the npm ecosystem.

How To Fix

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

npm uninstall rational_ladybug_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 workaround, you can prevent the installation of this malicious package by using npm's package-lock.json to monitor dependencies. Ensure that your project does not include 'rational_ladybug_z3n' in its dependencies. You can also use tools like Vulert to check for vulnerabilities in your package-lock.json without requiring code access. Visit https://vulert.com/scanner to utilize the Vulert playground for real-time monitoring.

Conclusion

The 'rational_ladybug_z3n' package poses a significant threat due to its malicious code designed to manipulate npm package metadata. It is essential to remove this package from your project and utilize tools like Vulert for ongoing monitoring of vulnerabilities. Staying informed and proactive is key to maintaining the security of your software.

See every vulnerability recorded for rational_ladybug_z3n →

Share this vulnerability

FAQ

It is an npm package associated with the tea.xyz token reward campaign, designed to automate the publishing of derivative packages.

The vulnerability can lead to unauthorized modifications of your package.json file, potentially compromising your project's integrity and reputation.

You should immediately uninstall the 'rational_ladybug_z3n' package and monitor your project for any unauthorized changes.

Yes, you can use tools like Vulert to monitor your package-lock.json for vulnerabilities in real-time without needing to access your code.

Regularly audit your dependencies, use trusted sources for packages, and utilize vulnerability monitoring tools like Vulert.

How To Fix

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

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