Malicious Code Injection in outside_ladybug_z3n Package

outside_ladybug_z3n Updated 27 Nov 2025

Summary

11/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-95811: Malicious code in outside_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 MarkAI Find prospects already talking about the problem you solve AI watches the communities your customers use to find qualified prospects, then alerts you when a conversation is worth joining. See MarkAI

Background

The outside_ladybug_z3n package is part of the npm ecosystem, which is widely used for JavaScript development. This package has been identified as part of a malicious campaign that aims to manipulate the npm registry by generating and publishing numerous derivative packages. The primary function of this package appears to be linked to the tea.xyz token reward campaign, which incentivizes developers to inflate their reputation scores through dubious means.

Vulnerability Detail

The vulnerability originates from the package's design, which includes scripts that automatically modify the package.json file. This modification removes private flags, alters version numbers, and generates random package names, leading to the pollution of the npm registry. The malicious payload can significantly impact developers by compromising the integrity of the npm ecosystem and potentially introducing security risks into applications that depend on these packages.

How To Fix

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

npm uninstall outside_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 outside_ladybug_z3n package in your project. If it is already included, remove it by executing: npm uninstall outside_ladybug_z3n. This will help mitigate the risk until a proper fix is implemented.

Conclusion

The outside_ladybug_z3n package poses a significant risk due to its malicious code designed to manipulate the npm registry. Developers should take immediate action to remove this package and monitor their applications for any potential vulnerabilities. Utilizing tools like Vulert can help maintain the security of your software.

See every vulnerability recorded for outside_ladybug_z3n →

Share this vulnerability

FAQ

The outside_ladybug_z3n package is a JavaScript package in the npm ecosystem that has been linked to a malicious campaign aimed at manipulating developer reputation scores.

The vulnerability can lead to the introduction of malicious code into your application, potentially compromising its security and integrity.

You should uninstall the outside_ladybug_z3n package immediately and monitor your application for any unusual behavior.

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

Regularly update your packages, monitor for vulnerabilities using tools like Vulert, 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 outside_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