Justin Parr

<h3>Update: 6/2015</h3>
<p>Changed e-mail token and math problem confirmation logic.  Previously, everything happened all at once, and the user would get prompted mutliple times for the math problem.<br />
Now, the user must answer the math problem first, before the e-mail token is sent.  Once the math problem is correctly answered within the session, it isn’t asked again.  The user must now enter the correct token, which results in successful registration.<br />
SPECIAL THANKS TO OLEG M. FOR HELPING ME IDENTIFY, FIX, AND TEST THE ERROR!!</p>
<h3>Update: 5/2015</h3>
<p>Added E-mail confirmation token.  Prevents registration until user enters a token sent via e-mail.</p>
<h3>Features:</h3>
<ul>
<li>Prevent users from registering, if their IP or e-mail address is listed in the “Comments” blacklist (Settings..Discussion)</li>
<li>E-mails user a 4-digit token, and requires the user to enter the token in order to register.</li>
<li>Users must solve a simple math problem (Add two one-digit numbers).</li>
<li>Places user IP address in “Website” field.</li>
</ul>
<p>This is a super-simple user registration spam countermeasure.  I searched for a plugin that was SIMPLE and EFFECTIVE.  I looked at quite a few plugins that promised the desired effect, but were either cumbersome, or included too many unneeded or unwanted features.  Likewise, there are some very simple plugins that are less-than-effective.</p>
<h3>This plugin is VERY simple:</h3>
<p>If the user’s IP or e-mail address is listed in the “Discussion” comments blacklist, it prevents the user from registering.  This functionality should really be built in to WordPress, so, you’re welcome.</p>
<p>When the user registers, they are presented with a simple math problem – adding a 3-digit number to a 1-digit number.  99% of the “user reg spam” is based on bots being able to attack the basic WordPress registration form.  By adding even a simple math problem, most bots will fail, removing your site as a target of opportunity.  Criminals go after what’s easy – if you make it slightly more difficult for them, they will go after someone else.</p>
<p>Once the user solves the math problem, they are sent a 4 digit token via e-mail, and must enter that token to continue registration.</p>
<p>Finally, knowing the location from where your users register allows you to more effectively evaluate and block the source.  This plugin adds the user’s IP address (at the time of registration)  to the “Website” field.</p>
<p>Go to http://whois.arin.net to find out who they are.  If you decide to block the IP,  add the IP address, part of the IP address, or e-mail domain to the “Discussion” comments blacklist, and ANY user registrations from an IP address matching that pattern will be blocked.</p>
<h3>Configuration</h3>
<h3>To Configure the Plugin:</h3>
<p>NOTE:  NO CONFIGURATION IS REQUIRED.  This plugin is fully-functional using the default values.</p>
<p>In the Plugins page, click “Settings” underneath the “JP User Registration Blacklist” plugin.</p>
<ul>
<li>
<p>Seed:  This value determines how the answer to the math problem is masked.  Periodically change this, to keep the spammers and criminals at bay.  The initial value is randomly-generated.</p>
</li>
<li>
<p>Failed Math Response:  Error message displayed to the user, if they fail to correctly solve the math problem.</p>
</li>
<li>
<p>Rejected IP or E-mail:  Error message displayed to the user, if their IP or e-mail is blocked.  Keep this simple and generic, to keep them from knowing why they are being blocked.</p>
</li>
<li>
<p>Form field name for math problem:  This field name contains the user’s answer to the math problem.  Periodically change this, to keep the bots away.  The initial value is randomly-generated.</p>
</li>
</ul>
<h3>To Block an IP address</h3>
<ol>
<li>In the WordPress Dashboard, go to “Settings…Discuss”</li>
<li>To block all or part of an IP address, add it on its own line to “Comments Blacklist”</li>
<li>To block all or part of an e-mail address, add it on its own line to “Comments Blacklist”</li>
<li>Click “Save”<br />
(For more details, see Examples)</li>
</ol>


JP User Registration Blacklist

Prevent User Registration Spam, and Track New User IP address

Erik

gardenboi

<p>Are you unsatisfied with your current antispam solution for Contact Form 7? It might be using an ineffective method to combat the specific type of bot attacks you’re facing. Fortunately, I have a solution for you!<br />
Antispam for Contact Form 7 is a simple yet highly effective plugin that protects your mailbox from bot flooding. Say goodbye to tedious configurations and captchas, which often lead to reduced conversions and inconvenience for genuine users. Our plugin utilizes a combination of on-page and off-page bot traps, along with an auto-learning mechanism powered by a statistical “Bayesian” spam filter called B8.<br />
CF7-AntiSpam seamlessly integrates with <a href="https://wordpress.org/plugins/flamingo/" rel="ugc">Flamingo</a> and enhances its functionality. When both plugins are installed, Flamingo gains additional controls, and an extra dashboard widget is enabled.</p>
<h3>SETUP</h3>
<p>Basic – Install and go! No configuration, keys, or registrations are required to activate the antispam protection. In this case, some protections, such as fingerprinting, language checks, and honeypots, will be enabled.<br />
Advanced – For CF7A to properly analyze the email content using its dictionary, it needs to parse the input message field of your form. To notify the antispam to check this field, you’ll need to add a “marker” to each contact form on your website. Simply add ‘flamingo_message: “[your-message]”‘ in the additional settings panel of each contact form you want to secure. This process follows the same method used with Flamingo. While this step may seem tedious, it is required for advanced text statistical analysis. Without it, the B8 filter cannot be enabled.<br />
GeoIP – (Optional) If you need to restrict which countries or languages can email you, you can enable this functionality. To enable GeoIP, you’ll need to agree to the GeoLite2 End User License Agreement and sign up for GeoLite2 Downloadable Databases. This will provide you with the required key to download the database. For detailed instructions, please refer to the dedicated section in the cf7-antispam plugin settings.</p>
<h3>Antispam Available Tests</h3>
<p>✅ Browser Fingerprinting<br />
✅ Language checks (Geo-ip, http headers and browser)<br />
✅ Honeypot<br />
️🆕 Honeyform*<br />
✅ Domain Name System Blackhole List (aka DNSBL)<br />
✅ blocklists (with automatic ban after N failed attempts, user defined ip exclusion list)<br />
✅ Hidden fields with encrypted unique hash<br />
✅ Time elapsed (with min/max values)<br />
✅ Prohibited words in message/email and user agent<br />
✅ B8 statistical “Bayesian” spam filter<br />
✅ Identity protection<br />
✅ Webmail protection</p>
<h3>Extends Flamingo and turns it into a spam manager!</h3>
<p>With this plugin, you can now review emails and train B8 to identify spam and legitimate messages. This feature proves useful, especially during the initial stages when some spam emails may slip through.<br />
Already using Flamingo? Even better! Just remember to add ‘flamingo_message: “[your-message]”‘ to the advanced settings (similar to other Flamingo labels) before activating the plugin. Alternatively, you can explore the advanced options and select “rebuild dictionary.”<br />
Upon activating CF7A, all previously collected emails will be parsed, and B8 will learn and develop its vocabulary. This pre-trained algorithm gives you a head start. How cool is that?<br />
Additional Notes:<br />
– A new column has been added to the right side of the Flamingo inbound page, displaying the level of spaminess for each email.<br />
– If you unban an email on the Flamingo “inbound” page, the corresponding IP will be removed from the blocklist. However, marking an email as spam will not blocklist the IP again.<br />
– Before activating this plugin, please make sure to mark all spam emails as spam in the Flamingo inbound section. This auto-training process will help the B8 algorithm.<br />
– If you receive a spam message, please avoid deleting it from the “ham” section. Instead, place it in the spam section to teach B8 how to differentiate between spam and legitimate messages.</p>
<h3>B8 statistical “Bayesian” Filter</h3>
<p>Originally created by <a href="https://en.wikipedia.org/wiki/Gary_Robinson" rel="nofollow ugc">Gary Robinson</a> <a href="https://www.linuxjournal.com/article/6467" rel="nofollow ugc">b8 is a statistical “Bayesian”</a> spam filter implemented in PHP.<br />
The B8 filter is a foundational example of <strong>Machine Learning (ML)</strong> for text classification, representing an early, yet powerful, statistical approach in Natural Language Processing (NLP). This approach precedes feature-weighting methods like <strong>TF-IDF</strong>, which in turn paved the way for modern deep learning architectures, such as <strong>Transformers</strong> and <strong>GPT</strong>.<br />
The filter tells you whether a text is spam or not, using statistical text analysis. What it does is: you give b8 a text and it returns a value between 0 and 1, saying it’s ham when it’s near 0 and saying it’s spam when it’s near 1. See <a href="https://nasauber.de/opensource/b8/readme.html#how-does-it-work" rel="nofollow ugc">How does it work?</a> for details about this.<br />
To be able to distinguish spam and ham (non-spam), b8 first has to learn some spam and some ham texts. If it makes mistakes when classifying unknown texts or the result is not distinct enough, b8 can be told what the text actually is, getting better with each learned text.<br />
This takes place on your own server without relying on third-party services.<br />
More info: <a href="https://nasauber.de/opensource/b8/" rel="nofollow ugc">nasauber.de</a></p>
<h3>Identity protection</h3>
<p>To fully protect the forms, it may be necessary to enable a couple of additional controls, because bots use the public data of the website to spam on it.<br />
– The first is user related and denies those who are not logged in the possibility of asking (sensitive) information about the user via wp-api and the protection for the xmlrpc exploit wordpress.<br />
– The second one is the WordPress protection that will obfuscate sensitive WordPress and server data, adding some headers in order to enhance security against xss and so on.<br />
Will be hidden the WordPress and WooCommerce version (wp_generator, woo_version), pingback (X-Pingback), server (nginx|apache|…) and php version (X-Powered-By), enabled xss protection headers (X-XSS-Protection), removes rest api link from header (but it will only continue to work if the link is not made public).</p>
<h3>Mailbox Protection (Multiple Send)</h3>
<p>Enhance email security by enabling the “Multiple Send” feature, which prevents consecutive email submissions to the user’s mailbox. This measure is effective in thwarting automated spam attempts and ensures a secure communication environment.</p>
<h3>Security & Privacy: A Local-First Approach</h3>
<p>AntiSpam for Contact Form 7 is built with your security and privacy as the <strong>top priority</strong>. Unlike many modern anti-spam solutions that rely on external cloud services or third-party subscriptions, our plugin is designed to run <strong>entirely on your own WordPress installation</strong>.</p>
<ul>
<li><strong>100% Local Processing:</strong> All anti-spam logic, checks, and data processing are performed directly on your server. <strong>No data is ever sent to, or stored by, any external third-party service</strong> (including ours).</li>
<li><strong>Not a Software as a Service (SaaS):</strong> This plugin is a standalone, self-contained software solution, not an interface to a paid or subscription-based external service. Once installed, it works autonomously.</li>
<li><strong>Enhanced Security:</strong> Since there is <strong>no central server or external API endpoint</strong> to communicate with, your website is immune to potential risks associated with centralized services, such as Single Point of Failure or data breach risks.</li>
</ul>
<p>You retain complete control and ownership over the security of your Contact Form 7 submissions.</p>
<h3>Privacy Notices</h3>
<p>AntiSpam for Contact Form 7 only processes the IP but doesn’t store any personal data directly from the user input. However, it creates a dictionary of spam and ham (non-spam) words in the WordPress database.<br />
This dictionary is built from words found in the submitted messages, meaning it <strong>may contain words that were part of the user’s e-mail message or personal data</strong>. This data is “degenerated,” which means the words might be normalized or altered before being stored.<br />
The sole purpose of this word collecting is to build a dictionary used for local, decentralized spam detection.</p>
<h3>Support</h3>
<p>Community support: via the <a href="https://wordpress.org/support/plugin/contact-form-7-antispam/" rel="ugc">support forums</a> on wordpress.org<br />
Bug reporting (preferred): file an issue on <a href="https://github.com/erikyo/contact-form-7-antispam" rel="nofollow ugc">GitHub</a></p>
<h4>Contribute</h4>
<p>We love your input! We want to make contributing to this project as easy and transparent as possible, whether it’s:</p>
<ul>
<li>Reporting a bug</li>
<li>Testing the plugin with different user agent and report fingerprinting failures</li>
<li>Discussing the current state, features, improvements</li>
<li>Submitting a fix or a new feature</li>
</ul>
<p>We use GitHub to host code, to track issues and feature requests, as well as accept pull requests.<br />
By contributing, you agree that your contributions will be licensed under its GPLv2 License.</p>
<p>My goal is to create an antispam that protects cf7 definitively without relying on external services. And free for everyone.<br />
if you want to help me, <a href="https://github.com/erikyo/contact-form-7-antispam" rel="nofollow ugc">GitHub</a> is the right place 😉</p>
<h3>copyright</h3>
<p>AntiSpam for Contact Form 7, Copyright 2021 Codekraft Studio<br />
AntiSpam for Contact Form 7 is distributed under the terms of the GNU GPL</p>
<p>This program is free software: you can redistribute it and/or modify<br />
it under the terms of the GNU General Public License as published by<br />
the Free Software Foundation, either version 3 of the License, or<br />
(at your option) any later version.</p>
<p>This program is distributed in the hope that it will be useful,<br />
but WITHOUT ANY WARRANTY; without even the implied warranty of<br />
MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.<br />
See the LICENSE file for more details.</p>
<h4>Resources</h4>
<ul>
<li>Contact Form 7 and Flamingo © 2021 Takayuki Miyoshi,<a href="https://it.wordpress.org/plugins/contact-form-7/" rel="nofollow ugc">LGPLv3 or later</a></li>
<li>B8 https://nasauber.de/opensource/b8/, © 2021 Tobias Leupold, <a href="https://gitlab.com/l3u/b8/-/tree/ab26daa6b293e6aa059d24ce7cf77af6c8b9b052/LICENSES" rel="nofollow ugc">LGPLv3 or later</a></li>
<li>GeoLite2 <a href="https://www.maxmind.com/en/geolite2/eula" rel="nofollow ugc">license</a></li>
<li>GeoIP2 PHP API <a href="https://github.com/maxmind/GeoIP2-php" rel="nofollow ugc">GeoIP2-php</a></li>
<li>chart.js https://www.chartjs.org/, © 2021 Chart.js <a href="https://github.com/chartjs/Chart.js/graphs/contributors" rel="nofollow ugc">contributors</a>, <a href="https://github.com/chartjs/Chart.js/blob/master/LICENSE.md" rel="nofollow ugc">MIT</a></li>
<li>Sudden Shower in the Summer, Public domain, Wikimedia Commons https://commons.wikimedia.org/wiki/File:Sudden_Shower_in_the_Summer_(5759500422).jpg</li>
</ul>
<h3>Contibutions</h3>
<p>Mirek Długosz – <a href="https://github.com/erikyo/cf7-antispam/pull/30" rel="nofollow ugc">#30</a> fixes a crash that occurred when analysing flamingo metadata<br />
MeliEve – <a href="https://github.com/wp-blocks/cf7-antispam/pull/42" rel="nofollow ugc">#42</a> Fix “internal_server_error” when message is empty<br />
MeliEve – <a href="https://github.com/wp-blocks/cf7-antispam/pull/61" rel="nofollow ugc">#61</a>  Handle deferrer script loading<br />
Zodiac1978 – <a href="https://github.com/wp-blocks/cf7-antispam/pull/67" rel="nofollow ugc">#67</a> Remove warning for unsafe email configuration w/o protection<br />
JohnHooks – <a href="https://github.com/wp-blocks/cf7-antispam/pull/61" rel="nofollow ugc">#66</a> Readme + plugin env<br />
sdellenb – <a href="https://github.com/wp-blocks/cf7-antispam/pull/163" rel="nofollow ugc">#66</a> Fix $reason parameter for calling cf7a_ban_by_ip</p>
<h3>Special thanks</h3>
<p>This project is tested with BrowserStack. <a href="https://www.browserstack.com/" rel="nofollow ugc">Browserstack</a></p>
<h3>MaxMind GeoIP2</h3>
<p>This plugin on demand can enable GeoLite2 created by MaxMind, available from <a href="https://www.maxmind.com" rel="nofollow ugc">https://www.maxmind.com</a><br />
While enabled you may <strong>have to mention it in the privacy policy</strong> of your site, depending on the law regulating privacy in your state!<br />
* GeoIP2 databases <a href="https://www.maxmind.com/en/accounts/current/geoip/downloads" rel="nofollow ugc">GeoLite2 Country</a></p>
<h3>DNSBL servers privacy policies</h3>
<ul>
<li>dnsbl-1.uceprotect.net <a href="http://www.uceprotect.net/en/index.php?m=13&s=0" rel="nofollow ugc">www.uceprotect.net license</a></li>
<li>dnsbl-2.uceprotect.net <a href="http://www.uceprotect.net/en/index.php?m=13&s=0" rel="nofollow ugc">www.uceprotect.net license</a></li>
<li>dnsbl-3.uceprotect.net <a href="http://www.uceprotect.net/en/index.php?m=13&s=0" rel="nofollow ugc">www.uceprotect.net license</a></li>
<li>dnsbl.sorbs.net <a href="http://www.sorbs.net/information/faq/" rel="nofollow ugc">sorbs.net license</a></li>
<li>zen.spamhaus.org <a href="https://www.spamhaus.org/organization/dnsblusage/" rel="nofollow ugc">spamhaus.org license</a></li>
<li>bl.spamcop.net <a href="https://www.spamcop.net/fom-serve/cache/297.html" rel="nofollow ugc">spamcop.net license</a></li>
<li>b.barracudacentral.org <a href="https://www.barracuda.com/company/legal/trust-center/data-privacy/privacy-policy" rel="nofollow ugc">barracudacentral.org privacy-policy</a></li>
<li>dnsbl.dronebl.org <a href="https://dronebl.org/docs/faq" rel="nofollow ugc">dronebl.org</a></li>
<li>all.spamrats.com <a href="https://spamrats.com/tos.php" rel="nofollow ugc">spamrats.com tos</a></li>
<li>bl.ipv6.spameatingmonkey.net <a href="https://spameatingmonkey.com/faq" rel="nofollow ugc">spameatingmonkey.net</a></li>
</ul>
<h3>Inspirations, links</h3>
<ul>
<li>Nikolai Tschacher <a href="https://incolumitas.com/pages/BotOrNot/" rel="nofollow ugc">incolumitas.com</a></li>
<li>Antoine Vastel <a href="https://github.com/antoinevastel/fpscanner" rel="nofollow ugc">fp-scanner</a>/<a href="https://github.com/antoinevastel/fp-collect" rel="nofollow ugc">fp-collect</a></li>
<li>Niespodd <a href="https://github.com/niespodd/browser-fingerprinting" rel="nofollow ugc">niespodd</a></li>
<li>Thomas Breuss <a href="https://gist.github.com/tbreuss/74da96ff5f976ce770e6628badbd7dfc" rel="nofollow ugc">tbreuss</a></li>
<li>Domain Name System-based blackhole list <a href="https://en.wikipedia.org/wiki/Domain_Name_System-based_blackhole_list" rel="nofollow ugc">wiki</a></li>
<li>dnsbl list <a href="https://en.wikipedia.org/wiki/Comparison_of_DNS_blacklists" rel="nofollow ugc">wiki</a></li>
</ul>


AntiSpam for Contact Form 7

A trustworthy antispam plugin for Contact Form 7. Wave goodbye to spam and keep your inbox clean!

JP User Registration Blacklist vs AntiSpam for Contact Form 7