shadowscan

ShadowScan Security Link gives you ShadowScan Guard local WordPress hardening for plugin auto-updates, username enumeration reduction, version/plugin exposure reduction, sensitive-file blocking, and basic connection/self-check diagnostics.
The plugin supports dual backend pairing with both Guard and ShadowScan. Pair with Guard backend for Guard-specific features, or connect to ShadowScan Portal to sync heartbeat status and unlock managed features for sites with an active Essential or Premium plan, or an approved reviewed pricing path. Basic Hosting can stay hosting-only, while ShadowScan Guard local hardening remains available in the plugin until managed entitlements are active.
Pairing the plugin and enabling remote diagnostics each require an explicit administrator acknowledgment in WP Admin. Those checkpoints are covered by the <a href="https://shadowscan.com.au/plugin-addendum" rel="nofollow ugc">ShadowScan Plugin Addendum</a>.
ShadowScan does not install, activate, or configure third-party security tools. If another security plugin is present, the connector only records its presence as metadata.
<h3>External services</h3>
This plugin can connect to external services to sync status, process security workflows, and support optional diagnostics after an admin pairs the site to ShadowScan.
<ul>
<li>Service: ShadowScan API (hosted at Supabase Edge Functions)</li>
<li>URL: <a href="https://axuhxgeafczsoctlzycz.supabase.co/functions/v1/" rel="nofollow ugc">ShadowScan API</a></li>
<li>Used for: ShadowScan pairing, heartbeat sync, command polling, command-result upload, subscription/policy sync, and support contact submissions.</li>
<li>Data sent and when: site URL, WordPress version, PHP version, connector version, Guard Layer/control status, heartbeat timestamps, and command execution metadata whenever the connector syncs with ShadowScan; contact form fields only when an admin submits support contact.</li>
<li>Terms: <a href="https://shadowscan.com.au/terms" rel="nofollow ugc">shadowscan.com.au/terms</a></li>
<li>Privacy: <a href="https://shadowscan.com.au/privacy" rel="nofollow ugc">shadowscan.com.au/privacy</a></li>
<li>
Plugin Addendum: <a href="https://shadowscan.com.au/plugin-addendum" rel="nofollow ugc">shadowscan.com.au/plugin-addendum</a>
</li>
<li>
Service: Guard API (hosted at Supabase Edge Functions)
</li>
<li>URL: <a href="https://dzaidjskedmlrtyqdobg.supabase.co/functions/v1/" rel="nofollow ugc">Guard API</a></li>
<li>Used for: Guard pairing validation, migration token validation, and Guard backend operations.</li>
<li>Data sent and when: pairing codes, migration tokens, and site metadata only when pairing with Guard backend or processing migration scenarios.</li>
<li>Terms: <a href="https://shadowscan.com.au/terms" rel="nofollow ugc">shadowscan.com.au/terms</a></li>
<li>Privacy: <a href="https://shadowscan.com.au/privacy" rel="nofollow ugc">shadowscan.com.au/privacy</a></li>
<li>
Plugin Addendum: <a href="https://shadowscan.com.au/plugin-addendum" rel="nofollow ugc">shadowscan.com.au/plugin-addendum</a>
</li>
<li>
Service: Have I Been Pwned Passwords API
</li>
<li>URL: <a href="https://api.pwnedpasswords.com" rel="nofollow ugc">api.pwnedpasswords.com</a></li>
<li>Used for: optional breached-password checks in password policy enforcement.</li>
<li>Data sent and when: k-anonymity password hash prefix (first 5 SHA-1 characters, no raw passwords) only when a password is checked by the policy flow.</li>
<li>Terms: <a href="https://haveibeenpwned.com/TermsOfUse" rel="nofollow ugc">haveibeenpwned.com/TermsOfUse</a></li>
<li>
Privacy: <a href="https://haveibeenpwned.com/Privacy" rel="nofollow ugc">haveibeenpwned.com/Privacy</a>
</li>
<li>
Service: Sentry
</li>
<li>URL: <a href="https://sentry.io" rel="nofollow ugc">sentry.io</a></li>
<li>Used for: optional error and fatal-event telemetry to assist troubleshooting.</li>
<li>Data sent and when: error event metadata (such as exception messages, stack traces, and runtime context) only after an admin explicitly enables Sentry telemetry in plugin settings and a Sentry DSN is configured; the optional MU diagnostics helper can send early-startup fatal errors only while both Sentry telemetry and remote diagnostics are enabled.</li>
<li>Terms: <a href="https://sentry.io/terms/" rel="nofollow ugc">sentry.io/terms</a></li>
<li>Privacy: <a href="https://sentry.io/privacy/" rel="nofollow ugc">sentry.io/privacy</a></li>
</ul>
<h3>Third-Party Libraries</h3>
This plugin bundles: 
* <a href="https://github.com/antonioribeiro/google2fa" rel="nofollow ugc">pragmarx/google2fa</a> (MIT License) 
* <a href="https://github.com/Bacon/BaconQrCode" rel="nofollow ugc">bacon/bacon-qr-code</a> (BSD-2-Clause; Copyright (c) 2017-present, Ben Scholzen “DASPRiD”)
<h3>Hooks</h3>
<code>shadowscan_log</code> 
Fires when the plugin emits an internal log message. You can hook this in a must-use plugin or theme if you want to capture logs.

ShadowScan Security Link

ShadowScan Guard local WordPress hardening and basic diagnostics, with optional Guard or ShadowScan portal connection for managed features.

Ben Treder

Secure Login Shield helps you lock down your WordPress login page. 
By default, WordPress exposes <code>/wp-login.php</code> and <code>/wp-admin/</code>. Bots hammer these URLs every day.
This plugin gives you a private login slug (e.g. <code>/dragon-lair</code>) and hides the default login endpoint:
<ul>
<li>Defaults to <code>/wp-login.php</code> until you change it.</li>
<li>Once changed, only your custom slug works.</li>
<li>Direct access to <code>/wp-login.php</code> shows a 404 Not Found (stealth mode).</li>
<li>Logged-out visitors hitting <code>/wp-admin/</code> are redirected to the homepage.</li>
<li>Deactivate the plugin → everything reverts to normal.</li>
</ul>
Made with ❤️ by <a href="https://BenTreder.com" rel="nofollow ugc">Ben Treder</a>
<h3>Features</h3>
<ul>
<li>Private login slug (e.g. <code>/dragon-lair</code>, <code>/control-center</code>, <code>/secret-gate</code>)</li>
<li>Stealth 404 protection: Bots hitting <code>/wp-login.php</code> see “Not Found”</li>
<li>Homepage redirect: <code>/wp-admin/</code> (logged out) → homepage</li>
<li>Easy settings page under Settings → Secure Login Shield</li>
<li>Safe activation/deactivation: no core hacks, auto-reverts when disabled</li>
</ul>
<h3>Contribute & Support</h3>
<ul>
<li>Website: <a href="https://BenTreder.com" rel="nofollow ugc">BenTreder.com</a> </li>
<li>Author: <a href="https://profiles.wordpress.org/bentreder/" rel="nofollow ugc">Ben Treder</a> </li>
<li>Issues & Feature Requests: Please open a ticket on <a href="https://BenTreder.com" rel="nofollow ugc">BenTreder.com</a> </li>
<li>Like this plugin? ⭐ Leave a review and help spread the word! </li>
<li>☕ Support development: <a href="https://www.buymeacoffee.com/bentreder" rel="nofollow ugc">Buy Me a Coffee</a></li>
</ul>

Treder Secure Login Shield

Create a private login URL and hide /wp-login.php with stealth 404s. Logged-out /wp-admin/ visits redirect to your homepage.

ShadowScan Security Link vs Treder Secure Login Shield