Critical Malicious Code Vulnerability in gfdg4t4 Package

gfdg4t4 Updated 02 Oct 2025

Summary

14/08/2025
CRITICAL
No i
Critical
Not published

MAL-2025-21388: Malicious code in gfdg4t4 (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 gfdg4t4 package is an npm library designed for specific functionalities within JavaScript applications. It is utilized for various tasks, but its integrity is compromised due to the presence of malicious code. This vulnerability poses a significant risk to applications relying on this package, as it can lead to unauthorized access or data manipulation.

Vulnerability Detail

The vulnerability in the gfdg4t4 package originates from the inclusion of malicious code that can execute harmful operations within the user's environment. This can result in data breaches, unauthorized access to sensitive information, and potential system compromise. The malicious nature of the code makes it imperative for users to take immediate action to mitigate risks associated with this vulnerability.

How To Fix

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

npm uninstall gfdg4t4

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, users can isolate the affected application from the network to prevent any potential exploitation while they seek to replace the gfdg4t4 package with a secure alternative.

Conclusion

The gfdg4t4 package contains malicious code that poses significant risks to applications using it. Immediate action is required to remove the package and replace it with a secure alternative. Utilizing tools like Vulert can help monitor and manage vulnerabilities in your software effectively.

See every vulnerability recorded for gfdg4t4 →

Share this vulnerability

FAQ

The gfdg4t4 package is an npm library used in JavaScript applications for various functionalities, but it has been found to contain malicious code.

You can use Vulert, which monitors and alerts for open-source vulnerabilities in your software. Simply upload your package-lock.json file to check for vulnerabilities.

Using the gfdg4t4 package can lead to unauthorized access, data breaches, and potential system compromise due to the malicious code it contains.

Currently, there is no patched version available for the gfdg4t4 package. It is advised to uninstall it and look for secure alternatives.

You can use the Vulert playground at Vulert Scanner to check if your application is affected by vulnerabilities without needing to sign up.

How To Fix

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

npm uninstall gfdg4t4

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