by ITclan BD 0 (0 reviews)

IC Security Guard

Name: IC Security Guard
Author: ITclan BD

Protect your site from brute force attacks with hidden login, login lockout, Email OTP 2FA, REST API & XML-RPC hardening, and real-time email alerts.

IC Security Guard ranks #66,865 among WordPress.org plugins with 0+ active installations, is #3,732 of 4,596 in the Security category, and was last updated Aug 18, 2026. Data from WordPress.org, refreshed twice daily — see methodology.

Tested up to WP 7.0.6 (Current: 7.1.2)

v1.3.0 Current Version v1.3.0

Updated 1 month ago Last Update on 18 Aug, 2026

Refreshed 17 hours ago Last Refreshed on

#3,732 of 4,596 in Security

View on WordPress.org

Rank

#66,865

— No change

Active Installs

-100%

KW Avg Position

196

21 worse

Downloads

226

+3 today

Support Resolved

— No change

Rating

Review 0 out of 5

0 (0 reviews)

Next Milestone 10

Total Progress 0%

0+ 10+

47,125

Ranks to Climb

Growth Needed

8,000,000

Active Installs

Pro

Unlock Exact Install Count

See the precise estimated active installs for this plugin, calculated from real-time ranking data.

Exact install estimates within tiers
Track install growth over time
Milestone progress predictions

Upgrade to Pro

Need 10 more installs to reach 10+

Rank Changes

Current #66,865

Change

Best #

Upgrade to Pro

Unlock 30-day and 90-day rank history charts with a Pro subscription.

Upgrade Now

Active Installs Growth

Upgrade to Pro

Active Installs 0,000,000+

Growth +0.0%

Peak 0,000,000

Downloads Growth

Downloads

Growth

Peak

Upgrade to Pro

Unlock 30-day, 90-day, and yearly download history charts with a Pro subscription.

Upgrade Now

Reviews & Ratings

0.0

0 reviews

Overall 0%

0 (0%)

Track This Plugin

Get detailed analytics, keyword tracking, and position alerts delivered to your inbox.

Start Tracking Free

Plugin Details

Version: 1.3.0
Last Updated: Aug 18, 2026
Requires WP: 6.5+
Tested Up To: 7.0.6
PHP Version: 7.4 or higher
Author: ITclan BD

Support & Rating

Rating: ☆ ☆ ☆ ☆ ☆ 0
Reviews: 0
Support Threads: 0
Resolved: 0%

Keywords

Brute Force login security rest-api security two factor authentication

Upgrade to Pro

Unlock keyword rankings, search positions, and detailed analytics with a Pro subscription.

Upgrade Now

Similar Plugins

Adminify – White Label, Admin Menu Editor, Login Customizer

6K+ installs

#2,760

Master Addons for Elementor – Elementor Addons, Widgets, Mega Menu Builder, Popup Builder, Widget Builder & Template Kits

Akismet Anti-spam: Spam Protection

5M+ installs

Wordfence Security - Firewall, Malware Scan, and Login Security

5M+ installs

#11

Really Simple Security - Simple and Performant Security (formerly Really Simple SSL)

Limit Login Attempts Security - Login Security, 2FA, Firewall, Brute Force Prevention

View all Security-and-spam-protection plugins

Frequently Asked Questions

Common questions about IC Security Guard

You can always reach your site's database (via phpMyAdmin or your host) and update the icsegu_hidelogin_options option in the wp_options table to disable hide_login_url, restoring access to the default wp-login.php.

Logged-in users are always allowed through to /wp-admin regardless of the hidden login setting. The failed-login lockout only applies to failed authentication attempts, and resets automatically once the configured lockout duration passes.

No. Logged-in users pass through untouched. The hidden login, lockout, REST API, and XML-RPC protections only apply to unauthenticated visitors and failed authentication attempts.

Lockout state is stored per IP address using WordPress transients, so it persists across page reloads and works with whatever caching layer your site already uses. The same lockout state is shared by the login form, the REST API, and XML-RPC.

When enabled, after a user enters the correct username and password, they are redirected to a dedicated verification page and emailed a 6-digit code (sent to their WordPress account email address). The code must be entered within the configured expiry window to complete login. Codes can be resent with a short cooldown between requests, and login only completes after the correct code is verified. This step is automatically skipped for REST API and XML-RPC requests, since application passwords and API integrations authenticate programmatically and have no page to display a challenge on.

XML-RPC's system.multicall method allows an attacker to test many username/password combinations in a single HTTP request, bypassing typical per-request throttling. Enabling "Disable XML-RPC" turns off the XML-RPC endpoint entirely. If you rely on XML-RPC for a mobile app, Jetpack, or another integration, leave this option off — any failed XML-RPC login attempts are still covered by the shared lockout.

By default, WordPress's REST API exposes a list of registered usernames at /wp-json/wp/v2/users to anyone, even when logged out. Attackers use this to harvest valid usernames before a brute-force attempt. Enabling "Block REST API User Enumeration" returns an authorization error for unauthenticated requests to this endpoint, while logged-in requests are unaffected.

No. Real-time email alerts are sent once per alert type whenever an event first triggers, then suppressed for the configured cooldown period (15 minutes by default) even if the same type of event keeps happening. This keeps you informed without flooding your inbox during a sustained attack.

Those sections are currently marked "Coming soon" in the plugin settings and will be added in a future release.