Malicious Code Injection in exact_anglerfish-smiletea Package

exact_anglerfish-smiletea Updated 24 Nov 2025

Summary

11/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-102301: Malicious code in exact_anglerfish-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 exact_anglerfish-smiletea package is part of the tea.xyz token reward campaign, which has been known to flood the npm registry with numerous packages. These packages are typically designed to inflate developer reputation scores through automated publishing scripts. The package in question is vulnerable due to its malicious payload that alters package metadata and repurposes the package for nefarious activities.

Vulnerability Detail

This vulnerability originates from a malicious payload embedded within the exact_anglerfish-smiletea package. The payload modifies the package.json file by removing private flags, changing version numbers, and generating random package names to continuously republish variants. This behavior not only pollutes the npm registry but also poses a risk to developers who may unknowingly install these compromised packages, leading to potential security breaches in their applications.

How To Fix

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

npm uninstall exact_anglerfish-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 exact_anglerfish-smiletea package and replace it with a trusted alternative. Always verify the integrity of packages before installation.

Conclusion

The exact_anglerfish-smiletea package contains a serious vulnerability that can compromise the integrity of applications using it. It is essential to remove this package and monitor your dependencies for any potential threats. Utilizing tools like Vulert can help maintain the security of your projects.

See every vulnerability recorded for exact_anglerfish-smiletea →

Share this vulnerability

FAQ

It is a package associated with the tea.xyz token reward campaign, which has been linked to malicious activities on the npm registry.

If your application uses this package, it may be at risk of having its metadata altered and could potentially be exposed to further malicious actions.

You should uninstall the exact_anglerfish-smiletea package immediately and check your application for any other compromised dependencies.

You can use tools like Vulert, which monitors your package-lock.json for open-source vulnerabilities in real-time 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 any signup.

How To Fix

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

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