Malicious Code Detected in gfd444 Package - Security Alert

gfd444 Updated 02 Oct 2025

Summary

14/08/2025
CRITICAL
No i
Critical
Not published

MAL-2025-21387: Malicious code in gfd444 (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 gfd444 package is an npm module that serves a specific functionality within the JavaScript ecosystem. It is utilized by developers to streamline certain tasks in their applications. However, this package has been identified as containing malicious code, posing a significant risk to users who incorporate it into their projects. The malicious nature of this package can lead to unauthorized access, data breaches, or other harmful activities.

Vulnerability Detail

The vulnerability in the gfd444 package originates from the inclusion of malicious code that can compromise the security of applications utilizing this package. This code can execute harmful actions without the user's consent, potentially leading to data theft or system corruption. The malicious code was introduced in version 0 and affects all subsequent versions, making it critical for users to take immediate action to mitigate the risk.

How To Fix

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

npm uninstall gfd444

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 workaround, users can implement the following code snippet to check for the presence of the gfd444 package in their project and remove it if found:

const { exec } = require('child_process');

exec('npm uninstall gfd444', (error, stdout, stderr) => {
  if (error) {
    console.error(`Error removing gfd444: ${error.message}`);
return;
  }
  if (stderr) {
    console.error(`stderr: ${stderr}`);
return;
  }
  console.log(`stdout: ${stdout}`);
});

Conclusion

The gfd444 package has been identified as containing malicious code, posing a significant risk to users. It is crucial to uninstall this package and monitor for vulnerabilities using tools like Vulert to ensure the security of your applications.

See every vulnerability recorded for gfd444 →

Share this vulnerability

FAQ

The gfd444 package is an npm module used in JavaScript applications, but it has been found to contain malicious code.

The malicious code can lead to unauthorized access, data breaches, or other harmful actions within your application.

You should uninstall the gfd444 package immediately and replace it with a secure alternative.

As of now, there is no patched version available for gfd444, and it is recommended to avoid using this package.

You can use Vulert, which monitors and alerts in real-time for open-source vulnerabilities using just your package-lock.json file. You can also check if your application is affected by this vulnerability using the Vulert playground without any signup.

How To Fix

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

npm uninstall gfd444

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