Malicious Code Injection in recent_dinosaur-smiletea Package

recent_dinosaur-smiletea Updated 18 Nov 2025

Summary

11/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-107788: Malicious code in recent_dinosaur-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 recent_dinosaur-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 distribution of token rewards by generating and publishing derivative packages. However, it has been identified as containing malicious code that compromises its integrity and the security of the npm registry.

Vulnerability Detail

The vulnerability in the recent_dinosaur-smiletea package originates from its design to automatically generate and publish derivative packages with randomized names. This malicious behavior includes modifying the package.json file to remove private flags, changing version numbers, and continuously republishing variants to pollute the npm registry. The ramifications of this vulnerability include potential abuse of developer reputation scores and the introduction of insecure packages into the ecosystem, which can lead to further exploitation.

How To Fix

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

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

Currently, there are no specific workarounds to mitigate the effects of this vulnerability other than removing the affected package from your project.

Conclusion

The recent_dinosaur-smiletea package has been identified as containing malicious code that poses a significant risk to developers and the npm ecosystem. It is crucial to remove this package from your projects and monitor for any updates or patches. Utilizing tools like Vulert can help maintain the security of your applications.

See every vulnerability recorded for recent_dinosaur-smiletea →

Share this vulnerability

FAQ

The recent_dinosaur-smiletea package is part of a campaign that aims to reward developers with tokens by flooding the npm registry with derivative packages.

This vulnerability can compromise the integrity of your project by introducing malicious code and insecure packages, potentially leading to security breaches.

If you have installed the recent_dinosaur-smiletea package, you should uninstall it immediately using the command: npm uninstall recent_dinosaur-smiletea.

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

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 recent_dinosaur-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