Malicious Code Detected in gfyrt34 Package - Security Alert

gfyrt34 Updated 02 Oct 2025

Summary

14/08/2025
CRITICAL
No i
Critical
Not published

MAL-2025-21397: Malicious code in gfyrt34 (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 gfyrt34 package is an npm library that serves various functionalities within JavaScript applications. It is designed to facilitate specific tasks, but it has been identified as containing malicious code that poses a significant security risk to users and their applications. The presence of such code can lead to unauthorized access, data breaches, or other harmful actions.

Vulnerability Detail

The vulnerability in the gfyrt34 package originates from the inclusion of malicious code that can execute harmful operations within the user's environment. This code can compromise the integrity of applications that rely on this package, potentially leading to severe consequences such as data theft, unauthorized access to sensitive information, or even complete system compromise. Users of the package are strongly advised to take immediate action to mitigate these risks.

How To Fix

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

npm uninstall gfyrt34

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 measure, users can avoid using the gfyrt34 package and look for alternative packages that provide similar functionality without the associated risks. Additionally, ensure that your application is monitored for any suspicious activity.

Conclusion

The discovery of malicious code in the gfyrt34 package highlights the importance of vigilance in managing open-source dependencies. Users must take immediate action to protect their applications by removing the affected package and monitoring for vulnerabilities.

See every vulnerability recorded for gfyrt34 →

Share this vulnerability

FAQ

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

You can check if your application is affected by using Vulert, which monitors open-source vulnerabilities in real-time. Visit Vulert Scanner to test your application without any signup.

If you have installed gfyrt34, it is crucial to uninstall the package immediately and replace it with a secure alternative.

Currently, there is no patched version available for gfyrt34. It is recommended to remove the package entirely.

Regularly monitor your dependencies using tools like Vulert, and keep your packages updated to the latest secure versions.

How To Fix

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

npm uninstall gfyrt34

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