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.

Esteban

Aipatch Security Scanner is a modular security audit engine built for site owners, developers, and AI-powered agents who need deep visibility into WordPress security posture — without the bloat of all-in-one security suites.
<h4>Why Aipatch Security Scanner?</h4>
Most WordPress security plugins are either too simple to be useful or too heavy to be practical. Aipatch takes a different approach:
<ul>
<li>Audit-first architecture. Every check is a standalone, testable module that returns structured findings with severity, confidence, evidence, and fingerprints.</li>
<li>Built for automation. 23 MCP abilities expose the full audit, scanning, and remediation surface to external AI agents — making Aipatch the first WordPress security plugin designed for agentic workflows.</li>
<li>Zero external dependencies. Everything runs locally. No accounts, no cloud services, no API keys required.</li>
<li>Reversible by design. Every automated remediation stores rollback data so you can undo any change with one click.</li>
</ul>
<h4>Core Capabilities</h4>
36-Point Security Audit
Aipatch runs 36 automated checks across 8 categories — core, plugins, themes, users, configuration, server, access control, and malware surface:
<ul>
<li>Outdated WordPress core, plugins, and themes</li>
<li>Default admin username, excessive admin accounts, inactive admin users, user ID 1 exposure</li>
<li>XML-RPC, file editor, debug mode, debug log, REST API exposure, directory listing</li>
<li>PHP version, HTTPS, file permissions, security headers (X-Frame-Options, CSP, etc.)</li>
<li>Database prefix, sensitive files, PHP execution in uploads, auto-update configuration</li>
<li>Salt key strength, cron health, cookie security flags, CORS, application passwords</li>
<li>Exposed backup files, phpinfo files, uploads directory indexing, default login URL</li>
<li>Database credential security, file installation permissions</li>
</ul>
Every finding includes a severity (critical / high / medium / low / info), confidence score, human-readable explanation, and actionable recommendation.
Weighted Security Score (0–100)
A logarithmic scoring engine computes an overall security score and per-area breakdown across six risk dimensions: software, access control, configuration, infrastructure, malware surface, and vulnerability exposure. Severity weights and confidence multipliers ensure the score reflects actual risk, not just issue count.
Multi-Layer Malware File Scanner
A three-layer file scanner (content 55%, context 25%, integrity 20%) with 27 detection signatures, Shannon entropy analysis, and malware family classification detects:
<ul>
<li>Code execution patterns: eval(), assert(), create_function(), preg_replace /e</li>
<li>System command functions: shell_exec, exec, passthru, backtick operators</li>
<li>Obfuscation techniques: base64 encoding, hex encoding, str_rot13, gzinflate chains, chr() concatenation, variable variables, suspiciously long lines</li>
<li>Network/exfiltration: cURL execution, fsockopen, remote file_get_contents</li>
<li>Known backdoor signatures: c99, r57, WSO, b374k, weevely, FilesMan</li>
<li>WordPress-specific threats: unauthorized admin creation, critical option injection, security function removal</li>
</ul>
Scanning runs in batches via an async job system with configurable batch sizes — safe for shared hosting.
Files are classified into 11 malware families (web shell, obfuscated loader, dropper, persistence backdoor, cloaked PHP, code injector, and more) with confidence scores and remediation hints.
WordPress Core Integrity Verification
Verifies every core file against official checksums from api.wordpress.org. Detects modified core files (checksum mismatch), missing core files, and unexpected files planted in wp-admin/ or wp-includes/. Core tampering findings are automatically escalated to critical severity with zero false-positive likelihood.
File Integrity Baseline
Build a known-good hash baseline of all PHP files in your installation. Diff against it at any time to detect modified, deleted, or newly added files. Origin detection distinguishes core, plugin, theme, and upload files.
Vulnerability Intelligence
A local knowledge base of known plugin, theme, and core vulnerabilities with a database-backed caching layer for fast lookups. Provider architecture allows extending with external feeds.
One-Click Remediation with Rollback
Apply fixes directly from findings — change WordPress options, delete suspicious files, rename files, patch file contents, or add .htaccess rules. Every automated action stores a full rollback payload so you can reverse any change. Manual remediations can be logged for audit trails.
Six supported action types: <code>wp_option</code>, <code>delete_file</code>, <code>rename_file</code>, <code>file_patch</code>, <code>htaccess_rule</code>, <code>manual</code>.
Hardening Module
Five toggleable hardening rules with clear explanations and compatibility warnings:
<ul>
<li>Disable XML-RPC — blocks external XML-RPC requests and removes X-Pingback header</li>
<li>Hide WordPress Version — removes version leaks from source, RSS feeds, scripts, and styles</li>
<li>Restrict REST API — limits sensitive endpoints to authenticated users</li>
<li>Block Author Scanning — prevents user enumeration via author archives</li>
<li>Login Brute-Force Protection — rate-limits login attempts per IP with configurable thresholds and lockout duration</li>
</ul>
Persistent Findings Store
All audit findings persist in a dedicated database table with automatic deduplication by fingerprint. Track findings over time — dismissed findings stay dismissed across scans; resolved findings reopen if the issue reappears.
Security Event Logging
Every scan, hardening change, remediation, and significant event is logged to a dedicated table. Logs are filterable by severity and exportable as CSV.
WordPress Site Health Integration
Adds 6 security tests to the built-in Site Health screen: file editor, debug mode, XML-RPC, admin username, SSL, and overall security score.
Performance Diagnostics
Built-in performance profiling to identify slow queries, high memory usage, and resource bottlenecks related to security operations.
REST API
10 authenticated endpoints under the <code>aipatch-security-scanner/v1</code> namespace for triggering scans, retrieving summaries, toggling hardening, exporting logs, and running performance diagnostics.
<h4>MCP Surface for AI Agents (23 Abilities)</h4>
Aipatch exposes 23 structured abilities via the WordPress Abilities API — making your site’s security surface fully accessible to external AI agents, coding assistants, and orchestration tools:
By default, only aipatch/audit-site is enabled. You can enable additional abilities from Aipatch Security Scanner -> Settings -> MCP Abilities.
Audit & Scanning
<ul>
<li>aipatch/audit-site — Run a full 36-check security audit with scored findings</li>
<li>aipatch/audit-suspicious — Quick heuristic scan for suspicious files</li>
<li>aipatch/start-file-scan — Launch an async multi-layer malware scan job</li>
<li>aipatch/process-file-scan-batch — Process next batch of files in a running scan</li>
<li>aipatch/file-scan-progress — Check file scan progress</li>
<li>aipatch/file-scan-results — Retrieve enriched scan results with family, reasons, layer scores</li>
<li>aipatch/get-scan-summary — Comprehensive latest scan summary with classification breakdown</li>
<li>aipatch/list-suspicious-files — List suspicious files from latest scan (no job_id needed)</li>
</ul>
Integrity & Baseline
<ul>
<li>aipatch/verify-core-integrity — Verify WP core files against official api.wordpress.org checksums</li>
<li>aipatch/baseline-build — Build or refresh the known-good file hash baseline</li>
<li>aipatch/baseline-diff — Compare current filesystem against stored baseline</li>
<li>aipatch/baseline-stats — Baseline statistics by origin type</li>
<li>aipatch/get-baseline-drift — Combined baseline drift + core integrity report</li>
</ul>
Findings & Monitoring
<ul>
<li>aipatch/list-findings — Query persistent findings with status/severity/category filters</li>
<li>aipatch/findings-stats — Aggregate finding statistics</li>
<li>aipatch/findings-diff — New and resolved findings since a point in time</li>
<li>aipatch/get-file-finding-detail — Single finding with decoded metadata, layer scores, family</li>
<li>aipatch/dismiss-finding — Dismiss a finding as accepted risk</li>
</ul>
Remediation
<ul>
<li>aipatch/apply-remediation — Apply a security fix with rollback support</li>
<li>aipatch/rollback-remediation — Undo a previously applied fix</li>
<li>aipatch/list-remediations — List remediation history with filters</li>
</ul>
Jobs & Status
<ul>
<li>aipatch/list-jobs — List scan/audit jobs with filters</li>
<li>aipatch/get-async-job-status — Check async job status and retrieve results</li>
</ul>
20 abilities are read-only; only 3 (dismiss, apply-remediation, rollback) modify site state. All abilities include typed input/output schemas, permission checks (<code>manage_options</code>), and structured error responses.
<h4>What Aipatch Does NOT Do</h4>
<ul>
<li>It is NOT a firewall or WAF — it does not filter incoming traffic.</li>
<li>It does NOT intercept frontend requests or affect page load performance.</li>
<li>It does NOT phone home, require an account, or send data externally.</li>
<li>It does NOT inject ads, upsells, or nag notices.</li>
</ul>

Aipatch Security Scanner

WordPress security scanner with 36 checks, malware scanning, core integrity verification, remediation, and 23 MCP abilities.

ShadowScan Security Link vs Aipatch Security Scanner