Malicious Code Injection in relative_toucan-smiletea Package

relative_toucan-smiletea Updated 18 Nov 2025

Summary

11/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-107844: Malicious code in relative_toucan-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 relative_toucan-smiletea package is part of the npm ecosystem and is associated with the tea.xyz token reward campaign. This package is designed to facilitate the generation and publication of derivative packages, which are often used to inflate developer reputation scores for token rewards. However, it has been identified as containing malicious code that compromises its integrity and the security of applications that depend on it.

Vulnerability Detail

The vulnerability in the relative_toucan-smiletea package stems from its malicious payload, which modifies the package.json file to remove private flags, alters version numbers, and generates random package names. This behavior is intended to continuously republish variants of the package, polluting the npm registry and potentially affecting other developers and applications. The origin of this vulnerability is linked to a campaign that floods npm with such malicious packages, making it crucial for developers to be aware of the risks associated with using this package.

How To Fix

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

npm uninstall relative_toucan-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 workaround, you can avoid using the relative_toucan-smiletea package altogether. If it is already included in your project, you can remove it using the command: npm uninstall relative_toucan-smiletea.

Conclusion

The relative_toucan-smiletea package poses a significant security risk due to its malicious code that modifies package files and repopulates the npm registry with harmful variants. It is crucial for developers to remove this package and monitor their projects for vulnerabilities using tools like Vulert.

See every vulnerability recorded for relative_toucan-smiletea →

Share this vulnerability

FAQ

It is an npm package that is part of the tea.xyz token reward campaign, designed to generate and publish derivative packages.

The malicious code can modify your package.json file and republish variants, potentially leading to security risks and pollution of the npm registry.

You should uninstall the relative_toucan-smiletea package immediately to mitigate any risks associated with its malicious behavior.

Yes, you can use Vulert, which monitors and alerts in real-time for open-source vulnerabilities using just your package-lock.json file.

Yes, you can use the Vulert playground at Vulert Scanner to check for vulnerabilities in your application without requiring any signup.

How To Fix

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

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