Malicious Code Injection in digital_minnow-smiletea Package

digital_minnow-smiletea Updated 24 Nov 2025

Summary

11/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-101573: Malicious code in digital_minnow-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 digital_minnow-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 can inflate developer reputation scores for token rewards. However, it has been compromised to include malicious scripts that alter its functionality and impact the integrity of the npm registry.

Vulnerability Detail

The vulnerability originates from the malicious code embedded in the digital_minnow-smiletea package. This code modifies the package.json file to remove private flags, alters version numbers, and generates random package names, leading to the continuous republishing of variants. The ramifications include pollution of the npm registry, potential security risks for developers using these packages, and damage to the reputation of the npm ecosystem.

How To Fix

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

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

Conclusion

The digital_minnow-smiletea package has been compromised with malicious code that poses significant risks to developers and the npm ecosystem. It is crucial to take immediate action by updating or removing the package and utilizing tools like Vulert to monitor for vulnerabilities in your projects.

See every vulnerability recorded for digital_minnow-smiletea →

Share this vulnerability

FAQ

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

The malicious code modifies your package.json file, removes private flags, and can lead to the pollution of the npm registry, potentially affecting your project's integrity.

You should uninstall the package immediately and monitor for any updates or patches that may be released.

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

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

How To Fix

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

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