Malicious Code Injection in naval_ladybug-smiletea Package

naval_ladybug-smiletea Updated 24 Nov 2025

Summary

11/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-106211: Malicious code in naval_ladybug-smiletea (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 Your last release was probably never penetration tested Manual testing by engineers who build software, not an auditor's checklist. Trusted by teams at Swift and Google Talk to Devnack

Background

The naval_ladybug-smiletea package is part of the tea.xyz token reward campaign, which has been associated with a surge of malicious packages on npm. This package is designed to facilitate token rewards by generating and publishing derivative packages with randomized names. Its primary function is to inflate developer reputation scores within the tea protocol ecosystem, but it has been compromised to include harmful scripts.

Vulnerability Detail

The vulnerability in naval_ladybug-smiletea originates from its malicious payload, which modifies the package.json file to remove private flags and alters version numbers. It generates random package names, often themed around Indonesian culture, and continuously republishes these variants to pollute the npm registry. This behavior not only compromises the integrity of the npm ecosystem but also poses risks to developers who may unknowingly use these tainted packages.

How To Fix

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

npm uninstall naval_ladybug-smiletea

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 naval_ladybug-smiletea package altogether. If it is already included in your project, remove it by running: npm uninstall naval_ladybug-smiletea. Additionally, consider using tools like Vulert to monitor your project for vulnerabilities. Vulert can analyze your package-lock.json file to alert you in real-time about any open-source vulnerabilities.

Conclusion

The naval_ladybug-smiletea package poses a significant risk due to its malicious code that alters package metadata and floods the npm registry with compromised packages. It is crucial for developers to remove this package and monitor their dependencies for vulnerabilities to maintain the security of their projects.

See every vulnerability recorded for naval_ladybug-smiletea →

Share this vulnerability

FAQ

It is a package associated with the tea.xyz token reward campaign, designed to inflate developer reputation scores by generating and publishing derivative packages.

The vulnerability can lead to the inclusion of malicious code in your project, compromising its integrity and potentially exposing it to security risks.

You should uninstall the naval_ladybug-smiletea package immediately and monitor your project for any further vulnerabilities.

You can use Vulert, which analyzes your package-lock.json file to provide real-time alerts for open-source vulnerabilities without requiring code access.

Yes, you can use the Vulert playground at Vulert Scanner to check if your application is affected by this vulnerability without needing to sign up.

How To Fix

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

npm uninstall naval_ladybug-smiletea

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