Malicious Code Injection in missing_ladybug_z3n Package - npm Vulnerability

missing_ladybug_z3n Updated 27 Nov 2025

Summary

11/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-95505: Malicious code in missing_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 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 missing_ladybug_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 its integrity and the integrity of the npm registry.

Vulnerability Detail

The vulnerability in the missing_ladybug_z3n package stems 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 these variants, polluting the npm registry and potentially affecting other developers and users relying on the integrity of the npm ecosystem. The origin of this vulnerability is linked to the tea.xyz token reward campaign, which employs such tactics to manipulate the npm registry for personal gain.

How To Fix

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

npm uninstall missing_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 temporary workaround, you can remove the missing_ladybug_z3n package from your project by executing the following command: npm uninstall missing_ladybug_z3n. This will prevent any malicious code from executing while you seek a more permanent solution.

Conclusion

The missing_ladybug_z3n package has been identified as containing malicious code that poses a significant risk to users and the npm ecosystem. It is crucial to take immediate action by updating or removing the package to safeguard your projects and maintain the integrity of your development environment.

See every vulnerability recorded for missing_ladybug_z3n →

Share this vulnerability

FAQ

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

The vulnerability can lead to the modification of your package.json file, removal of private flags, and the generation of random package names, which can compromise the integrity of your project.

If you are using the missing_ladybug_z3n package, you should update it to a patched version or remove it entirely from your project to mitigate the risk.

You can use Vulert, which monitors and alerts in real-time for open-source vulnerabilities in your software by analyzing the package-lock.json file. You can check if your application is affected by this vulnerability using the Vulert playground.

Yes, you can use the Vulert playground at Vulert Scanner to check for vulnerabilities in your application without requiring any signup.

How To Fix

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

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