Malicious Code in plain_ladybug_z3n: A Threat to npm Ecosystem

plain_ladybug_z3n Updated 18 Nov 2025

Summary

11/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-107086: Malicious code in plain_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

plain_ladybug_z3n is an npm package that is part of a broader campaign associated with the tea.xyz token reward system. This package, like others in the campaign, is designed to manipulate the npm registry by generating and publishing numerous derivative packages with randomized names. The malicious nature of this package poses a significant risk to developers and the integrity of the npm ecosystem.

Vulnerability Detail

The vulnerability in plain_ladybug_z3n stems from its inclusion in a malicious campaign that floods the npm registry with derivative packages. It contains scripts that automatically modify the package.json file, removing private flags, altering version numbers, and creating random package names. This behavior not only inflates developer reputation scores for token rewards but also pollutes the npm registry, making it difficult for developers to find legitimate packages. The origin of this vulnerability is linked to the tea.xyz token reward campaign, which exploits npm's publishing mechanisms.

How To Fix

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

npm uninstall plain_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 measure, you can avoid using the plain_ladybug_z3n package and look for alternative packages that provide similar functionality without the associated risks. Additionally, you can use the following command to uninstall the package: npm uninstall plain_ladybug_z3n.

Conclusion

The plain_ladybug_z3n package poses a significant threat to the npm ecosystem due to its malicious behavior. It is essential for developers to be aware of this vulnerability, take necessary actions to remove the package, and utilize tools like Vulert to monitor their projects for potential vulnerabilities.

See every vulnerability recorded for plain_ladybug_z3n →

Share this vulnerability

FAQ

plain_ladybug_z3n is an npm package that is part of a malicious campaign aimed at manipulating the npm registry.

This vulnerability can lead to the pollution of the npm registry, making it difficult to find legitimate packages and potentially compromising your project's integrity.

You should uninstall the plain_ladybug_z3n package immediately and look for alternative packages that do not pose a security risk.

Yes, you can use Vulert, which monitors and alerts for open-source vulnerabilities in your software using just the package-lock.json file. You can check your application for vulnerabilities using the Vulert playground without any signup.

Regularly check for updates to your dependencies, use tools like Vulert for real-time monitoring, and review the security advisories for the packages you use.

How To Fix

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

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