Malicious Code Injection in tadasdhi-dfds-tesru Package: A Threat to npm Users

tadasdhi-dfds-tesru Updated 26 Nov 2025

Summary

12/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-166659: Malicious code in tadasdhi-dfds-tesru (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 Lume, the Habilume companion Habilume Habit tracker with a companion that grows with you Complete habits, earn Lume Points, and watch your Lume grow as you stay consistent. App Store Google Play

Background

The tadasdhi-dfds-tesru package is part of the npm ecosystem, primarily utilized for various JavaScript applications. This package has been identified as part of a malicious campaign that aims to exploit npm's publishing capabilities. It is designed to generate and publish derivative packages with random names, thereby inflating developer reputation scores for token rewards in the tea.xyz protocol. The package's functionality is compromised due to its malicious intent, making it a significant risk for developers and users alike.

Vulnerability Detail

The vulnerability originates from the package's malicious code, which modifies the package.json file to remove private flags, alters version numbers, and generates random package names. This behavior leads to the continuous republishing of variants that pollute the npm registry, potentially causing confusion and security risks for developers who may unknowingly use these compromised packages. The malicious payload can also affect the integrity of the npm ecosystem by inflating reputation scores through deceptive practices.

How To Fix

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

npm uninstall tadasdhi-dfds-tesru

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-tesru package and look for alternative packages that provide similar functionality without the associated risks. Additionally, consider using tools like Vulert to monitor your package-lock.json for vulnerabilities in real-time.

Conclusion

The tadasdhi-dfds-tesru package poses a significant risk due to its malicious code designed to exploit npm's publishing system. Developers should take immediate action to remove this package and monitor their applications for vulnerabilities. Utilizing tools like Vulert can enhance security by providing real-time alerts for open-source vulnerabilities.

See every vulnerability recorded for tadasdhi-dfds-tesru →

Share this vulnerability

FAQ

It is an npm package that has been identified as part of a malicious campaign aimed at exploiting npm's publishing capabilities.

The vulnerability can lead to the introduction of malicious code into your application, compromising its security and integrity.

You should uninstall the tadasdhi-dfds-tesru package immediately and monitor your application for any unusual behavior.

Yes, tools like Vulert can help monitor your package-lock.json for open-source vulnerabilities in real-time.

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

Sponsored Lume, the Habilume companion Habilume Habit tracker with a companion that grows with you Complete habits, earn Lume Points, and watch your Lume grow as you stay consistent. App Store Google Play

How To Fix

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

npm uninstall tadasdhi-dfds-tesru

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