by Cory Marsh on WordPress.org
Real-time firewall that stops bots, malware, and hackers with real AI, file protection, and traffic analytics without slowing down your site

BitFire shows the source location, time and response for every web request to your site. See good and bad actors in real-time.
BitFire protects your website from bots, hackers, malware, and critical vulnerabilities – before they can cause damage.
This plugin brings advanced security technology used by large enterprises to your WordPress site, now available in a free version. Whether you manage a business website, blog, or WooCommerce store, BitFire gives you powerful protection and visibility into your traffic.
Most security plugins wait for updates to detect new threats. BitFire takes a different approach: it uses artificial intelligence and real-time request analysis to stop zero-day attacks, bots, and malicious users before they get access to your site.
Our AI learns what normal traffic looks like for your site and blocks anything suspicious – without you needing to configure endless rules.
“Unlike traditional firewalls that allow everything by default and react to known threats, BitFire only allows verified traffic – stopping new and unknown attacks instantly.”
BitFire includes WordPress’s first Runtime Application Self Protection (RASP) firewall.
This means BitFire watches what your plugins and code are doing in real time and blocks anything suspicious – including:
– Unauthorized file modifications (File RASP)
– Suspicious database queries (Database RASP)
– Unauthorized account creation or privilege escalation (Authentication RASP)
– Dangerous outbound network requests (Network RASP)
“It’s like a bodyguard inside your WordPress server – watching every move and stopping threats before they execute.”
Increased traffic logging and historical view to 30 days
** Independent WAF testing by Cloudbric https://labs.cloudbric.com/wafer **
BitFire [PRO] – 🇦 (94%)
BitFire is used by major organizations on our managed enterprise platform and developed by a veteran security architect with over 20 years of experience defending Fortune 500s and critical infrastructure.
This free release brings our best bot detection and traffic logging features to the WordPress community – at no cost.
Visit https://bitfire.co for:
– Full product comparison
– Malware removal services
– Pro pricing
– Support
Privacy. We take privacy very seriously. BitFire inspects all traffic going to the webserver and takes care to filter out any potentially sensitive information by replacing it with redacted. The config.ini file includes a list of common sensitive field names under the “filtered_logging” section. You can add additional fields to filter in the config file by adding a line “filtered_logging[field_name] = true” and replacing “field_name” with the name of the desired parameter to filter.
BitFire includes an error handler which monitors it’s operation. In the event an error is detected in the BitFire software; including during install, an alert can be sent to BitFire’s developer team. The development team monitors these errors in real time and includes fixes for any detected errors in each new release.
Malware scanner. BitFire sends tiny 64bit hashes (signatures, or fingerprints) of every file to our hash database. For instance, index.php may hash to the number: 812612388126487. The database is many gigabytes and centrally located on our servers. BitFire uses that information to determine if a file has been modified or is a known good file and sends the results back to your site. Client hashes are never stored off your server.
Log data and configuration data is stored locally on the filesystem in the wp-content/uploads/bitfire_RANDOM directory. This directory is unique and hidden from the Internet and protected by an .htaccess file. Web servers that are configured to allow directory listings will want to ensure that the file wp-content/uploads/index.php is present to prevent directory listings. The random directory name is 12 characters long and is generated on install. The directory is not accessible from the Internet and is protected by a .htaccess file.