Malicious Code Injection in functional_tahr_dumbs Package

functional_tahr_dumbs Updated 24 Nov 2025

Summary

11/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-102978: Malicious code in functional_tahr_dumbs (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 MarkAI Find prospects already talking about the problem you solve AI watches the communities your customers use to find qualified prospects, then alerts you when a conversation is worth joining. See MarkAI

Background

The functional_tahr_dumbs package is part of the npm ecosystem, which is widely used for JavaScript package management. This package has been identified as part of a malicious campaign that aims to inflate developer reputation scores through the creation of numerous derivative packages. The vulnerability stems from the package's design, which allows for the automatic modification and republishing of package metadata, leading to potential abuse within the npm registry.

Vulnerability Detail

The vulnerability in functional_tahr_dumbs originates from its association with the tea.xyz token reward campaign. The package contains scripts that automatically generate and publish derivative packages with altered metadata, including the removal of private flags and changes to version numbers. This behavior can lead to pollution of the npm registry, making it difficult for developers to trust the integrity of packages. The malicious payload is designed to create random package names, which can confuse users and lead to the installation of compromised software.

How To Fix

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

npm uninstall functional_tahr_dumbs

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 functional_tahr_dumbs package until a patched version is released. Additionally, consider using alternative packages that provide similar functionality without the associated risks.

Conclusion

The functional_tahr_dumbs package poses a significant risk due to its malicious code that modifies package metadata and repackages itself. Developers should take immediate action to remove this package and monitor their applications for vulnerabilities to ensure the integrity and security of their software.

See every vulnerability recorded for functional_tahr_dumbs →

Share this vulnerability

FAQ

The functional_tahr_dumbs package is an npm package that has been identified as part of a malicious campaign to inflate developer reputation scores through the creation of numerous derivative packages.

This vulnerability can lead to the installation of compromised packages, potentially introducing malicious code into your application and affecting its security and integrity.

If you have installed the functional_tahr_dumbs package, it is crucial to remove it from your project and update to a safe version or an alternative package.

You can use tools like Vulert, which monitors your package-lock.json file to alert you in real-time for open-source vulnerabilities in your software.

Yes, you can use the Vulert playground at Vulert Scanner to check if your application is affected by this vulnerability without requiring any signup.

How To Fix

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

npm uninstall functional_tahr_dumbs

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