Malicious Code in jotform-webhook-test (npm)

jotform-webhook-test Updated 02 Oct 2025

Summary

05/11/2023
CRITICAL
No i
Critical
Not published

MAL-2023-8438: Malicious code in jotform-webhook-test (npm). Affects jotform-webhook-test versions 1.0.0. 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 jotform-webhook-test package is an npm package used for testing webhooks in JotForm, a popular online form builder. It provides functionality to simulate webhook requests and verify the responses. This package is widely used by developers to ensure the proper functioning of their JotForm integrations.

Vulnerability Detail

The jotform-webhook-test package has been identified as malicious by the OpenSSF Package Analysis project. The package communicates with a domain associated with malicious activity. This indicates that the package may be compromised and could potentially perform unauthorized actions or collect sensitive information from the user's system. It is crucial to take immediate action to mitigate the risk of using this package.

How To Fix

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

npm uninstall jotform-webhook-test

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

There is no specific workaround available for this vulnerability. It is essential to remove the malicious package and take necessary precautions to prevent any potential security breaches.

Conclusion

The jotform-webhook-test package has been identified as malicious, and it is crucial to remove it from your project to mitigate potential security risks. Regularly reviewing and updating dependencies can help maintain the security of your application. For further support on vulnerability remediation, you can reach out to DevNack.com.

See every vulnerability recorded for jotform-webhook-test →

Share this vulnerability

FAQ

The jotform-webhook-test package is an npm package used for testing webhooks in JotForm.

The package has been identified to communicate with a domain associated with malicious activity, indicating potential compromise and security risks.

Using the malicious package can lead to unauthorized actions being performed or sensitive information being collected from the user's system.

To fix the vulnerability, uninstall the jotform-webhook-test package and review the dependencies of your project to ensure they are from trusted sources.

No, there is no specific workaround available. Removing the malicious package is the recommended course of action.

How To Fix

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

npm uninstall jotform-webhook-test

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