Malicious Code Injection in charming_fly-smiletea: npm Package Vulnerability

charming_fly-smiletea Updated 24 Nov 2025

Summary

11/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-100345: Malicious code in charming_fly-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 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 charming_fly-smiletea package is part of the tea.xyz token reward campaign, which has been known to flood the npm ecosystem with malicious packages. These packages are designed to inflate developer reputation scores through the automatic generation and publication of derivative packages. The malicious behavior includes modifying package.json files to remove private flags and changing version numbers, leading to potential security risks for developers using this package.

Vulnerability Detail

The vulnerability stems from the presence of malicious code within the charming_fly-smiletea package. This code is designed to automatically generate and publish derivative packages with randomized names, effectively polluting the npm registry. The malicious payload alters the package.json file, removing private flags and changing version numbers, which can lead to unauthorized access and manipulation of the package ecosystem. Developers using this package may unknowingly contribute to the proliferation of these malicious variants, compromising their projects and potentially exposing sensitive information.

How To Fix

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

npm uninstall charming_fly-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 charming_fly-smiletea package and look for alternative packages that provide similar functionality without the associated risks. Additionally, you can monitor your package-lock.json file for any unauthorized changes and revert them if necessary.

Conclusion

The charming_fly-smiletea package contains malicious code that poses a significant risk to developers and their projects. It is crucial to remove this package and monitor your dependencies for any vulnerabilities. Utilizing tools like Vulert can help ensure your software remains secure.

See every vulnerability recorded for charming_fly-smiletea →

Share this vulnerability

FAQ

The charming_fly-smiletea package is part of a campaign that aims to inflate developer reputation scores through the automatic generation of derivative packages.

Using the charming_fly-smiletea package can lead to unauthorized modifications in your project, potentially exposing it to security risks and compromising its integrity.

You should remove the charming_fly-smiletea package from your project immediately and monitor for any unauthorized changes in your package-lock.json file.

Yes, you can use tools like Vulert, which monitors and alerts you in real-time for open-source vulnerabilities in your software by analyzing your package-lock.json file.

You can use the Vulert playground at Vulert Scanner to check if your application is affected by this vulnerability without requiring any signup.

How To Fix

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

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