Malicious Code Detected in ctrlform Package - Security Alert

ctrlform Updated 02 Oct 2025

Summary

14/08/2025
CRITICAL
No i
Critical
Not published

MAL-2025-17813: Malicious code in ctrlform (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 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 ctrlform package is a Node.js library designed for form handling and data processing in web applications. It provides developers with tools to easily manage user input and validate data. However, the package has been found to contain malicious code, posing a significant security risk to applications that utilize it.

Vulnerability Detail

The vulnerability in the ctrlform package arises from the inclusion of malicious code that can compromise the security of applications using this library. This code may allow unauthorized access to sensitive data, execute arbitrary commands, or facilitate other malicious activities. The issue was introduced in version 0 and affects all subsequent versions, making it critical for users to take immediate action to mitigate potential risks.

How To Fix

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

npm uninstall ctrlform

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, consider removing the ctrlform package from your project until a secure version is released. You can do this by running: 'npm uninstall ctrlform'. Additionally, review your codebase for any dependencies that may rely on this package and assess alternative libraries for form handling.

Conclusion

The ctrlform package has been identified as containing malicious code, posing a serious threat to applications that utilize it. Users are urged to take immediate action by updating or removing the package to safeguard their applications. Regular monitoring for vulnerabilities using tools like Vulert can help maintain security in open-source projects.

See every vulnerability recorded for ctrlform →

Share this vulnerability

FAQ

The ctrlform package is used for handling forms and processing user input in web applications.

The malicious code can potentially allow unauthorized access to sensitive data and execute harmful commands.

You can use Vulert to monitor and alert for open-source vulnerabilities in your software. Visit Vulert Scanner to check if your application is affected without requiring any signup.

As of now, a patched version has not been released. Users should monitor the official repository for updates.

If immediate updates are not possible, consider removing the package and using alternative libraries for form handling.

How To Fix

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

npm uninstall ctrlform

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