Malicious Code Injection in tadasdhi-ert-nabfa Package - npm Vulnerability

tadasdhi-ert-nabfa Updated 26 Nov 2025

Summary

12/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-166664: Malicious code in tadasdhi-ert-nabfa (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 tadasdhi-ert-nabfa package is part of a series of npm packages that emerged during the tea.xyz token reward campaign. These packages are designed to manipulate the npm registry by creating and publishing numerous derivative packages with randomized names. This behavior is intended to inflate developer reputation scores in exchange for tea protocol token rewards. The package's functionality is compromised due to its malicious intent, making it a significant risk for developers using it.

Vulnerability Detail

The vulnerability in the tadasdhi-ert-nabfa package stems from its inclusion in a campaign that floods the npm registry with malicious packages. The malicious code modifies the package.json file by removing private flags, altering version numbers, and generating random package names. This results in the continuous republishing of variants, which pollutes the npm registry and can lead to potential security risks for applications relying on these packages. The origin of this vulnerability is linked to the automated scripts (auto.js, autopublish.js, etc.) that are part of the malicious payload.

How To Fix

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

npm uninstall tadasdhi-ert-nabfa

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 tadasdhi-ert-nabfa package from your project dependencies. Use the following command to uninstall it: npm uninstall tadasdhi-ert-nabfa. Additionally, consider using tools like Vulert to monitor your package-lock.json for vulnerabilities without needing to access the code directly.

Conclusion

The tadasdhi-ert-nabfa package poses a significant risk due to its malicious code designed to manipulate the npm registry. Developers should take immediate action to remove this package and monitor their projects for vulnerabilities. Utilizing tools like Vulert can help maintain security in open-source projects.

See every vulnerability recorded for tadasdhi-ert-nabfa →

Share this vulnerability

FAQ

The tadasdhi-ert-nabfa package is an npm package that is part of a malicious campaign aimed at inflating developer reputation scores through the creation of numerous derivative packages.

The vulnerability can lead to the pollution of the npm registry, potentially introducing malicious code into your application, which can compromise security and functionality.

You should immediately uninstall the tadasdhi-ert-nabfa package and monitor your project for any other potentially malicious packages.

You can use Vulert, which monitors your package-lock.json for open-source vulnerabilities in real-time, providing alerts without requiring code access.

Yes, you can use the Vulert playground at Vulert Scanner to check if your application is affected by this vulnerability without needing to sign up.

How To Fix

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

npm uninstall tadasdhi-ert-nabfa

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