Malicious Code Detected in fdgert3 Package - Security Alert

fdgert3 Updated 02 Oct 2025

Summary

14/08/2025
CRITICAL
No i
Critical
Not published

MAL-2025-20332: Malicious code in fdgert3 (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 fdgert3 package is an npm library that serves specific functionalities within JavaScript applications. It is designed to enhance development processes by providing various utilities. However, it has been identified as containing malicious code, posing a significant risk to applications that utilize it.

Vulnerability Detail

The vulnerability in the fdgert3 package stems from the inclusion of malicious code that can compromise the security of applications using this package. This code may lead to unauthorized access, data breaches, or other harmful actions within the affected systems. The issue was introduced in version 0 and persists in all subsequent versions, making it critical for users to address this vulnerability promptly.

How To Fix

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

npm uninstall fdgert3

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 isolate the usage of the fdgert3 package in a controlled environment or use a different package that provides similar functionalities without the associated risks. However, the best course of action is to remove the package entirely.

Conclusion

The fdgert3 package has been identified as containing malicious code, which poses a serious risk to applications that depend on it. It is crucial for developers to uninstall this package and seek alternatives to ensure the security of their applications. Utilizing tools like Vulert can aid in monitoring for such vulnerabilities in the future.

See every vulnerability recorded for fdgert3 →

Share this vulnerability

FAQ

fdgert3 is an npm package designed to provide various utilities for JavaScript applications.

The fdgert3 package contains malicious code that can compromise application security.

You can use Vulert's playground at Vulert Scanner to check if your application is affected by this vulnerability without needing to sign up.

You should uninstall the fdgert3 package immediately and consider using a trusted alternative.

Vulert monitors and alerts for open-source vulnerabilities in your software using just the package-lock.json file, providing real-time insights.

How To Fix

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

npm uninstall fdgert3

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