Protector – Malware Removal, Firewall & Core Repair
Every day, thousands of WordPress sites are hacked. Most security plugins offer protection, but they come with a massive cost: they slow down your server with bloated features and complex settings. Protector is different. It is a lightweight, AI-ready security layer that turns your WordPress site into a digital fortress without compromising speed. Whether you are trying to recover a hacked site or proactively defend your business, Protector delivers enterprise-grade security that anyone can configure. With our new 1-Click Security Overview Dashboard, you can activate all recommended protections and block 98% of automated attacks in under 8 seconds. 📖 Read the Official Documentation here 🦠 Malware Threat Scanner & Auto-Repair Don’t just find malware; destroy it. Our deep, recursive local scanner verifies your WordPress integrity without crashing your server: * Core Integrity Verification: Cross-references all Core files against the official WordPress.org checksums. * Advanced Pattern Detection: Detects suspicious code patterns (like eval, base64_decode, shell_exec) hidden in your files. * 1-Click Auto-Repair: Found a modified core file? Click “Repair” and Protector will automatically fetch a clean, original version directly from the official WP SVN and overwrite the infected file. 🛡️ Login Fortress (Brute-Force Protection) Hackers relentlessly target the wp-login.php page. We make it disappear. * Secret Login URL: Hide wp-login.php completely. Any unauthorized attempt will be instantly redirected to a custom URL of your choice. * Smart Honeypots: Inject invisible fields into your login and comment forms to trap and block spam/brute-force bots automatically. * Block Username Scanning: Prevent attackers from discovering your admin usernames via ?author=1 enumeration. 🔒 1-Click Site Hardening Lock down common vulnerabilities instantly: * Security Headers: Protect against XSS, Clickjacking, and MIME-Sniffing attacks with a single toggle. * XML-RPC Control: Disable XML-RPC completely to eliminate one of the biggest brute-force attack vectors on WordPress. * Version Obfuscation: Hide your WordPress version from the source code so hackers can’t target known exploits. * Restrict REST API: Block public access to endpoints that expose sensitive user data. 📊 Live Attack Log Peace of mind you can actually see. Monitor every blocked attack, triggered honeypot, and deleted malware in real-time straight from your dashboard. 🚀 Upgrade to KloxStudios Pro Need absolute maximum power? Protector integrates seamlessly with the KloxStudios Cloud AI. Pro users unlock Cloud AI Malware Verification for 3rd-party plugins/themes, Automatic IP Lockouts, Instant Admin Login Alerts (Email & Webhook), and 2FA.
XML-RPC Settings
XML-RPC Settings Configure XML-RPC methods to increase the security of your website: Build-in features could be used for malicious purposes and cannot be disabled by default. Disable GET access XML-RPC API only responds to POST requests. Direct GET access is not needed and can be used to fingerprint websites and use them as XML-RPC zombies in later attacks. Disable system.multicall system.multicall method can be misused for amplification attacks. Disable system.listMethods system.listMethods method can be used for verifying attack scope. Prevent malicious actors from enumerating usernames and credentials. Disable authenticated methods Methods requiring authentication, such as wp.getUsersBlogs, are often used to brute-force your passwords. Pingbacks are a helpful feature to discover back-links to your posts but can be misused for DDoS attacks or allow fingerprinting your WP version. Disable pingbacks Pingbacks are generally safe, but are often used for DDoS attacks via system.multicall. Remove X-Pingback header If you decide to disable pingbacks, it’s a good practice to remove the X-Pingback header return by your posts. Hide WordPress version when verifying pingbacks Pingbacks’ user-agent can reveal your exact WordPress version, even when hidden by other plugins. Hide WordPress version when sending pingbacks Pingbacks’ user-agent can reveal your exact WordPress version, even when hidden by other plugins. Unnecessary XML-RPC API, leave enabled if you are not sure. Disable Demo API Remove demo.sayHello and demo.addTwoNumbers methods, as they are not needed. Disable Blogger API WordPress supports the Blogger XML-RPC API methods. Disable MetaWeblog API WordPress supports the metaWeblog XML-RPC API. Disable MovableType API WordPress supports the MovableType XML-RPC API. If you are using some integrations or WP mobile applications, it might be a good idea to allow XML-RPC only to specific IPs. Allow XML-RPC only for IP comma separated eg. 192.168.10.242, 192.168.10.241 It is possible to hide a message between the allowed methods when system.listMethods is called (not recommended). Add message to XML-RPC methods We are hiring! Check jobs.yourdomains.com
