Malicious Code Injection in tadasdhi-dfds-teru: npm Package Vulnerability

tadasdhi-dfds-teru Updated 26 Nov 2025

Summary

12/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-166658: Malicious code in tadasdhi-dfds-teru (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 Mobile apps built by Devnack Design, build and launch iOS and Android apps with a senior product team. From idea to store release Start a project

Background

The package 'tadasdhi-dfds-teru' is part of the npm ecosystem and is associated with the tea.xyz token reward campaign. It is designed to facilitate the automatic generation and publication of derivative packages. This package is vulnerable due to its inclusion of malicious scripts that manipulate package metadata, potentially harming developers and users by inflating reputation scores fraudulently.

Vulnerability Detail

The vulnerability originates from the malicious scripts embedded within the 'tadasdhi-dfds-teru' package. These scripts, including auto.js and autopublish.js, are designed to modify the package.json file by removing private flags, altering version numbers, and generating random package names. This behavior leads to the continuous republishing of variants, polluting the npm registry and compromising the integrity of the ecosystem. The ramifications include potential security risks for applications relying on this package, as well as reputational damage for developers involved.

How To Fix

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

npm uninstall tadasdhi-dfds-teru

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 'tadasdhi-dfds-teru' package and look for alternative packages that provide similar functionality without the associated risks. Additionally, you can monitor your project for vulnerabilities using tools like Vulert, which can analyze your package-lock.json file to alert you of any open-source vulnerabilities in real-time.

Conclusion

The 'tadasdhi-dfds-teru' package poses a significant risk due to its malicious code that alters package metadata and floods the npm registry. It is crucial for developers to remove this package and monitor their projects for vulnerabilities using tools like Vulert to ensure the security and integrity of their applications.

See every vulnerability recorded for tadasdhi-dfds-teru →

Share this vulnerability

FAQ

The main issue is the presence of malicious scripts that manipulate package metadata and flood the npm registry with derivative packages.

You can use Vulert's playground at Vulert Scanner to check if your application is affected by this vulnerability without requiring any signup.

You should uninstall the package immediately using 'npm uninstall tadasdhi-dfds-teru' and look for alternative packages.

Yes, using this package can lead to security vulnerabilities in your application and damage your reputation as a developer.

Vulert uses your package-lock.json file to monitor and alert you in real-time for open-source vulnerabilities in your software.

How To Fix

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

npm uninstall tadasdhi-dfds-teru

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