Malicious Code Injection in Teadungdang Package: A Threat to npm Ecosystem

teadungdang Updated 27 Nov 2025

Summary

11/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-98397: Malicious code in teadungdang (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

Teadungdang is an npm package that is part of the tea.xyz token reward campaign. It is designed to facilitate the generation and publication of derivative packages, often with randomized names, to inflate developer reputation scores for token rewards. This package, like others in the campaign, is susceptible to malicious exploitation, leading to potential pollution of the npm registry.

Vulnerability Detail

The vulnerability in the Teadungdang package originates from its design to automatically generate and publish derivative packages. The malicious code modifies the package.json file by removing private flags and changing version numbers, allowing it to republish variants continuously. This behavior can lead to the pollution of the npm registry with numerous unwanted packages, potentially affecting other developers and users relying on npm for package management.

How To Fix

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

npm uninstall teadungdang

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

Conclusion

The Teadungdang package presents a significant vulnerability due to its malicious code that can pollute the npm registry. It is crucial for developers to take immediate action by uninstalling the package and monitoring for updates. Utilizing tools like Vulert can help maintain the security of your projects.

See every vulnerability recorded for teadungdang →

Share this vulnerability

FAQ

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

The vulnerability can lead to the pollution of the npm registry, affecting the integrity of packages and potentially introducing malicious code into your project.

You should uninstall the Teadungdang package immediately and monitor for any updates or patches that may address the vulnerability.

Yes, you can use Vulert, which monitors and alerts for open-source vulnerabilities in your software using just package-lock.json. You can check your application for vulnerabilities without any signup at the Vulert playground.

Regularly update your packages, monitor for vulnerabilities using tools like Vulert, and review the security advisories for the packages you use.

How To Fix

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

npm uninstall teadungdang

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