Malicious Code Detected in gformjs Package - Security Alert

gformjs Updated 02 Oct 2025

Summary

14/08/2025
CRITICAL
No i
Critical
Not published

MAL-2025-21392: Malicious code in gformjs (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 gformjs package is an npm library designed for form handling in JavaScript applications. It provides developers with tools to easily manage form submissions, validations, and data processing. However, recent findings have revealed that this package contains malicious code, posing significant security risks to applications that utilize it.

Vulnerability Detail

The vulnerability in the gformjs package arises from the inclusion of malicious code that can compromise the security of applications using this library. This code may lead to unauthorized access, data breaches, or other malicious activities. The issue is rooted in the package's version 0 and has been flagged by security researchers, indicating a serious threat to users who have integrated this package into their projects.

How To Fix

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

npm uninstall gformjs

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 gformjs package entirely and implement custom form handling logic in your application. This will mitigate the risk of exposure to the malicious code present in the package.

Conclusion

The discovery of malicious code in the gformjs package highlights the importance of regularly auditing dependencies in software projects. Developers should take immediate action to remove this package and consider alternative solutions to ensure the security of their applications.

See every vulnerability recorded for gformjs →

Share this vulnerability

FAQ

gformjs is an npm library designed for managing form submissions and validations in JavaScript applications.

The gformjs package was found to contain malicious code that poses security risks to applications using it.

You can use Vulert, a tool that monitors open-source vulnerabilities in real-time. Visit Vulert Scanner to check if your application is affected without any signup.

It is recommended to remove the gformjs package from your project and look for secure alternatives or implement custom form handling.

As of now, there is no patched version available. It is best to remove the package until a secure version is released.

How To Fix

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

npm uninstall gformjs

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