Malicious Code Injection in redundant_bug-smiletea Package

redundant_bug-smiletea Updated 18 Nov 2025

Summary

11/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-107794: Malicious code in redundant_bug-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 Mobile apps built by Devnack Design, build and launch iOS and Android apps with a senior product team. From idea to store release Start a project

Background

The redundant_bug-smiletea package is part of the tea.xyz token reward campaign that has infiltrated the npm ecosystem. It is designed to facilitate the automatic generation and publication of derivative packages, which can inflate developer reputation scores for token rewards. This package, like others in the campaign, is characterized by its use of scripts that automate the publishing process, potentially leading to a polluted npm registry.

Vulnerability Detail

The vulnerability in the redundant_bug-smiletea package stems from its malicious code that modifies the package.json file. It removes private flags, alters version numbers, and generates random package names, primarily themed around Indonesian culture. This behavior not only compromises the integrity of the npm registry but also poses risks to developers who may unknowingly use these compromised packages, leading to potential security breaches and reputation damage.

How To Fix

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

npm uninstall redundant_bug-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 remove the redundant_bug-smiletea package from your project by executing: npm uninstall redundant_bug-smiletea. This will prevent any malicious code from executing until a secure version is available.

Conclusion

The redundant_bug-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 take immediate action to mitigate this vulnerability by updating or removing the affected package and employing monitoring tools like Vulert to safeguard their projects.

See every vulnerability recorded for redundant_bug-smiletea →

Share this vulnerability

FAQ

It is a package associated with the tea.xyz token reward campaign, designed to automate the generation and publication of npm packages.

The vulnerability can lead to the modification of your package.json file, potentially exposing your project to security risks and affecting your reputation in the developer community.

You should uninstall the package immediately and check for any updates or patches that may address the vulnerability.

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

Regularly audit your dependencies, use tools like Vulert for monitoring, and stay updated on security advisories related to the packages you use.

How To Fix

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

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