Malicious Code Injection in dante-teadev Package: A Threat to npm Users

dante-teadev Updated 24 Nov 2025

Summary

11/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-101205: Malicious code in dante-teadev (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 dante-teadev package is part of the npm ecosystem and is associated with the tea.xyz token reward campaign. This package is designed to facilitate certain functionalities within the npm registry but has been compromised, leading to significant security concerns. The vulnerability arises from the package's ability to execute scripts that manipulate its own metadata and create numerous derivative packages, thereby affecting the integrity of the npm registry.

Vulnerability Detail

The vulnerability in the dante-teadev package stems from malicious code that modifies the package.json file to remove private flags, alters version numbers, and generates random package names. This behavior is intended to inflate developer reputation scores for token rewards, leading to pollution of the npm registry with numerous derivative packages. The origin of this issue is linked to the tea.xyz token reward campaign, which has been known to flood the npm ecosystem with such malicious packages.

How To Fix

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

npm uninstall dante-teadev

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 dante-teadev package from your project by executing 'npm uninstall dante-teadev'. This will prevent any malicious scripts from executing until a secure version is available.

Conclusion

The dante-teadev package poses a significant security risk due to its malicious code that alters package metadata and floods the npm registry with derivative packages. It is essential 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 dante-teadev →

Share this vulnerability

FAQ

The dante-teadev package is an npm package that is part of the tea.xyz token reward campaign, designed to facilitate certain functionalities but has been compromised.

The malicious code modifies your package.json file, removes private flags, and creates numerous derivative packages, potentially leading to security vulnerabilities and pollution of the npm registry.

You should uninstall the dante-teadev 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 your application for vulnerabilities using the Vulert playground.

Regularly update your dependencies, use tools like Vulert for monitoring, and review the packages you include in your project to ensure they are from trusted sources.

How To Fix

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

npm uninstall dante-teadev

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