Malicious Code Injection in Tehaah-codfd-barasgewfa Package

tehaah-codfd-barasgewfa Updated 26 Nov 2025

Summary

12/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-168928: Malicious code in tehaah-codfd-barasgewfa (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

Tehaah-codfd-barasgewfa is an npm package that is part of the tea.xyz token reward campaign. This package is designed to facilitate the automatic generation and publication of derivative packages, which are often used to inflate developer reputation scores for token rewards. The package's functionality includes creating randomized package names and modifying package metadata, which can lead to significant issues in the npm ecosystem.

Vulnerability Detail

The vulnerability in the Tehaah-codfd-barasgewfa package stems from its malicious payload, which modifies the package.json file to remove private flags, changes version numbers, and generates random package names. This behavior is intended to pollute the npm registry by continuously republishing variants of the package, thereby compromising the integrity of the registry and potentially affecting other developers who rely on it.

How To Fix

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

npm uninstall tehaah-codfd-barasgewfa

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, avoid using the Tehaah-codfd-barasgewfa package and monitor your project for any dependencies that may have been affected by this malicious package. You can also use tools like Vulert to monitor your package-lock.json file for vulnerabilities.

Conclusion

The Tehaah-codfd-barasgewfa package poses a significant risk due to its malicious behavior, which can compromise the integrity of the npm registry. It is crucial to remove this package from your project and monitor for any vulnerabilities using tools like Vulert.

See every vulnerability recorded for tehaah-codfd-barasgewfa →

Share this vulnerability

FAQ

Tehaah-codfd-barasgewfa is an npm package associated with the tea.xyz token reward campaign, designed to automate the generation of derivative packages.

The vulnerability can lead to the pollution of the npm registry, potentially affecting other packages and developers who rely on the integrity of the registry.

You should uninstall the Tehaah-codfd-barasgewfa package immediately and monitor your project for any other affected dependencies.

Yes, you can use Vulert, which monitors your package-lock.json file for open-source vulnerabilities in real-time without requiring code access or installation.

You can use the Vulert playground at Vulert Scanner to check if your application is affected by this vulnerability without signing up.

How To Fix

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

npm uninstall tehaah-codfd-barasgewfa

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