Joris Le Blansch

I like to use Contact Form 7 on most of my WordPress sites. It’s a powerful form manager that suits all my needs. I don’t like to use external calls to protect the forms from spam submissions though (like reCaptcha or hCaptcha) and don’t want to present a manual captcha to a user (math or other puzzle). Since I couldn’t find a really basic honeypot script that works on most entries, I created one here. Hopefully it’s useful to someone else also.
<h3>Setup</h3>
<ul>
<li>Install the plugin using the regular plugin setup routine or upload the entire apiosys-honeypot-cf7 folder to the /wp-content/plugins/ directory.</li>
<li>Activate the plugin through the “Plugins” menu in WordPress, you MUST have Contact Form 7 AND Flamingo installed and enabled.</li>
<li>Add the following shortcodes to your Contact Form 7 forms:</li>
</ul>
[honeypot] – Adds the hidden honeypot field 
[timestamp] – Adds time-based validation
<ul>
<li>Complete the rest of the options which you can find in Admin > Contact > Honeypot. A generally good working set of values is enabled by default there.</li>
</ul>
<h3>What tests are used?</h3>
<ul>
<li>A Honeypot Field</li>
<li>A Checkbox Trap</li>
<li>Time-Based Validation</li>
<li>Email domain Check</li>
<li>Basic Content Analysis</li>
</ul>
<h3>Does it really work?</h3>
It has been tested on several high-traffic WP sites. I see a return of ~ 1 ‰ (i.e. 1 in a thousand) of spam going through. That usually corresponds to humans paid to fill forms or sophisticated bots. Please feel free to contribute to make it even better. You can contribute directly <a href="https://github.com/apio-sys/apiosys-honeypot-cf7" rel="nofollow ugc">here</a>.

Apio systems – Honeypot for Contact Form 7

Basic Honeypot plugin for Contact Form 7 to drastically reduce spam on form submissions without user interaction.

Team beta version

Note: This plugin requires HTTPS to function (due to Web Crypto API usage).
The Story: The Forging of the Ultimate Defense
This project began with a simple goal: to create a lightweight honeypot trap to catch basic bots. But during development, we faced a harsh reality: Simple traps are obsolete. Modern AI bots and headless browsers can easily step over traditional defenses. A basic trap was no longer enough; we needed a fortress.
So, we forged a completely new architecture. We added Proof of Work, Behavioral Analysis, and Rate Limiting. What started as a simple honeypot evolved into a 15-layer invisible firewall. Like a samurai’s blade, it operates with absolute precision—completely invisible to your real customers, yet ruthlessly executing a “Silent Kill” on spam bots before they ever reach your inbox or database.
Samurai Honeypot protects every Contact Form 7 and WPForms form with fifteen independent defense layers. 
Each layer contributes a score, and blocked submissions are handled by a 3-Tier Triage System:
<h4>3-Tier Triage System</h4>
<ul>
<li>Tier 1 (Pass): Score below the threshold (default 50) — email is sent normally.</li>
<li>Tier 2 (Quarantine): Score between the threshold and 99 — email is silently suppressed (Silent Kill) and the submission is saved to the built-in Quarantine Log for admin review.</li>
<li>Tier 3 (Drop / Instant Kill): Score of 100 or higher — email is silently suppressed and the submission is permanently dropped without logging. This protects your database from bloat during DDoS or mass bot attacks.</li>
</ul>
Warning — False Positives: Depending on your environment, legitimate emails may occasionally be flagged as spam. Enterprise proxies, strict corporate firewalls, outdated browsers, VPNs, and unusual network configurations can trigger detection layers. You MUST check the Quarantine Log periodically to identify and recover any false positives. The plugin cannot distinguish all edge cases automatically.
<h4>Defense Layers</h4>
<ol>
<li>JS Injection Gate — Blocks bots that cannot execute JavaScript. Tokens are fetched via REST API for full page-cache compatibility.</li>
<li>Polymorphic Honeypot — Decoy field name is cryptographically derived per token (not exposed in the API response), hidden from humans via CSS.</li>
<li>Token Signature — HMAC-SHA256 signed stateless token with IP and Form ID binding.</li>
<li>Time Trap — Detects impossibly fast submissions. Browser autofill is automatically exempt.</li>
<li>Proof of Work — SHA-256 computational challenge via Web Crypto API that forces CPU cost on bots.</li>
<li>Behavioral Entropy — Hash-verified human-like event counters: mouse, keyboard, touch, scroll. Uniqueness tracking detects script reuse.</li>
<li>Headless UA Block — Server-side User-Agent check instantly blocks known headless browsers and automated tools (Headless Chrome, Puppeteer, PhantomJS, Selenium, Playwright, Nightmare, Electron). Toggleable in settings for E2E testing compatibility.</li>
<li>Headless Detection — Detects automated browser environments (navigator.webdriver, plugin count, window.chrome, language count).</li>
<li>UA Age Detection — Scores based on Chrome version age. 2+ years: +10, 3+ years: +20, 4+ years: +30. Bots often use hardcoded old User-Agent strings that never update.</li>
<li>Rate Limiting — Per-IP submission rate limiting with IPv6 /64 normalization.</li>
<li>Replay Protection — Atomic token consumption (INSERT IGNORE) + TTL expiry enforcement.</li>
<li>IP Blacklist — Manually configured IP/CIDR blacklist for known bad actors.</li>
<li>Content: URL Limit — Flags messages containing more URLs than the configured threshold.</li>
<li>Content: BBCode — Detects BBCode link syntax (<code>[url=...]</code>) that never appears in legitimate form submissions.</li>
<li>Content: Denylist — Matches against WordPress Disallowed Comment Keys (Settings > Discussion).</li>
</ol>
<h4>Key Features</h4>
<ul>
<li>3-Tier Triage — Pass, Quarantine (with local log), or Drop. No legitimate message is lost without a trace — quarantined submissions are saved for admin review.</li>
<li>Built-in Quarantine Log — Blocked Tier 2 submissions are saved to a local database table (up to 1,000 entries, FIFO). View date, score, trigger reasons, and full form data from the admin panel. No external plugin required.</li>
<li>DDoS-Resilient Tier 3 Drop — Submissions scoring 100+ are immediately dropped from memory without any database write. This prevents database exhaustion during mass bot attacks.</li>
<li>GDPR Compliant — No cookies, no external service calls, no plugin-specific PII stored. IP addresses are one-way hashed with a site-specific salt before any storage — raw IPs never touch the database. No consent banner required.</li>
<li>Stateless Tokens — No database writes for token generation; prevents DoS via DB bloat.</li>
<li>Zero Trust Client — All client-submitted data is verified server-side with HMAC signatures and hash integrity checks.</li>
<li>Zero Configuration — Activate and all Contact Form 7 / WPForms forms are protected automatically.</li>
<li>Cache Compatible — Tokens are fetched via REST API, so page caching works fine.</li>
<li>Multiple Forms — Works correctly with multiple forms on the same page.</li>
<li>IP Whitelist / Blacklist — Whitelist trusted IPs or CIDR ranges to skip all scoring. Blacklist known bad IPs to add +100 score instantly. Optionally whitelist all logged-in WordPress users.</li>
<li>Headless Browser Blocking — Server-side User-Agent check instantly blocks Headless Chrome, Puppeteer, Selenium, and other automated browsers (+100 score). Enabled by default; can be toggled off for E2E testing.</li>
<li>Content Rules — Detect spam patterns in form content: excessive URLs, BBCode link syntax, and WordPress Disallowed Comment Keys matching.</li>
<li>Trusted Proxy Support — Optional mode for Cloudflare and reverse proxy environments with IP range validation.</li>
<li>Lightweight — Three PHP files, no external dependencies, no jQuery.</li>
</ul>

Samurai Honeypot for Forms

Invisible 15-layer anti-spam for Contact Form 7 & WPForms. Score-based 3-Tier Triage silently blocks bots — no CAPTCHA, no user friction.

Apio systems – Honeypot for Contact Form 7 vs Samurai Honeypot for Forms