{"id":376829,"date":"2026-09-30T08:44:47","date_gmt":"2026-09-30T08:44:47","guid":{"rendered":"https:\/\/wordpress.org\/plugins\/exploitshield-domain-monitor\/"},"modified":"2026-09-30T08:44:30","modified_gmt":"2026-09-30T08:44:30","slug":"exploitshield-domain-monitor","status":"publish","type":"plugin","link":"https:\/\/wordpress.org\/plugins\/exploitshield-domain-monitor\/","author":17703070,"comment_status":"closed","ping_status":"closed","template":"","meta":{"version":"4.1.5","stable_tag":"4.1.5","tested":"7.1.2","requires":"6.0","requires_php":"7.4","requires_plugins":null,"header_name":"ExploitShield Domain Monitor","header_author":"ExploitShield","header_description":"Bitcoin-activated domain exploit monitoring for WordPress using the ExploitShield Flask backend.","assets_banners_color":"","last_updated":"2026-09-30 08:44:30","external_support_url":"","external_repository_url":"","donate_link":"","header_plugin_uri":"","header_author_uri":"","rating":0,"author_block_rating":0,"active_installs":0,"downloads":53,"num_ratings":0,"support_threads":0,"support_threads_resolved":0,"author_block_count":0,"sections":["description","installation","changelog"],"tags":{"4.1.5":{"tag":"4.1.5","author":"ddanchev","date":"2026-09-30 08:44:30","revision":3720724}},"upgrade_notice":[],"ratings":[],"assets_icons":[],"assets_banners":[],"assets_blueprints":{},"all_blocks":[],"tagged_versions":["4.1.5"],"block_files":[],"assets_screenshots":[],"screenshots":[]},"plugin_section":[],"plugin_tags":[1886,283623,1184,600],"plugin_category":[45,54],"plugin_contributors":[283624],"plugin_business_model":[],"class_list":["post-376829","plugin","type-plugin","status-publish","hentry","plugin_tags-bitcoin","plugin_tags-domain-monitoring","plugin_tags-malware","plugin_tags-security","plugin_category-ecommerce","plugin_category-security-and-spam-protection","plugin_contributors-ddanchev","plugin_committers-ddanchev"],"banners":[],"icons":{"svg":false,"icon":"https:\/\/s.w.org\/plugins\/geopattern-icon\/exploitshield-domain-monitor.svg","icon_2x":false,"generated":true},"screenshots":[],"raw_content":"<!--section=description-->\n<p>The SOC and Threat Intelligence Analyst at Home tab displays published analyst assessments for the protected host. Read the rationale, recommended response and dated scanner evidence. Private service drafts are never included. The tab synchronizes while open and supports manual refresh.\nReview scanner detections, reputation and DNS signals, suspicious behavior and dated evidence in a dedicated investigation workspace. Filter and export findings, compare assessments, inspect coverage, and manage local review decisions. Internal infrastructure details are not part of the client workspace.<\/p>\n\n<h3>External Services<\/h3>\n\n<p>This plugin connects to external services that are required for ExploitShield monitoring and billing.<\/p>\n\n<p>ExploitShield monitoring API<\/p>\n\n<p>This plugin connects to the ExploitShield monitoring API at https:\/\/web-md5.site and the ExploitShield customer site at https:\/\/exploitshield.io. The service is used for domain ownership verification, activation, Bitcoin checkout coordination, API credit and entitlement state, crawler scan requests, threat dashboards, analyst notes, support notices, plugin update metadata, and PDF report generation.<\/p>\n\n<p>Data sent: the protected domain or host, WordPress site URL, site verification token or DNS verification state, plugin instance identifier, contact email when configured by the site administrator, selected scan profile, API credit\/billing operation, support request content when submitted, and authenticated requests needed to retrieve reports and scan status. Data is sent when an administrator configures the plugin, checks verification, creates or checks a Bitcoin order, opens dashboard\/report pages, requests scans, syncs analyst notes, checks plugin notices, or downloads reports.<\/p>\n\n<p>Terms: https:\/\/exploitshield.io\/terms\nPrivacy: https:\/\/exploitshield.io\/privacy<\/p>\n\n<p>Blockonomics Bitcoin payment service<\/p>\n\n<p>ExploitShield uses Blockonomics on the service side to generate Bitcoin payment addresses and confirm payment status. The plugin displays the payment address, Bitcoin amount, order status, and optional Blockonomics status link returned by ExploitShield. The plugin does not send a Blockonomics API key and does not directly call the Blockonomics merchant API.<\/p>\n\n<p>Data involved: Bitcoin payment address, expected Bitcoin amount, order identifier, and payment status metadata. This data is used only for payment confirmation and activation of the purchased monitoring\/API-credit service.<\/p>\n\n<p>Terms and Privacy: https:\/\/nginx.blockonomics.co\/privacy<\/p>\n\n<p>No QR-code generator or other third-party image service is loaded by this plugin. Bitcoin payment details are displayed as copyable text.<\/p>\n\n<h3>Source Code and Build Tools<\/h3>\n\n<p>The JavaScript and CSS shipped in this plugin are the human-readable source files used by WordPress. There is no npm, webpack, Rollup, Vite, minification, transpilation, or generated asset build step for the distributed plugin package. The files in assets\/js and assets\/css can be reviewed and modified directly.<\/p>\n\n<h3>Important Limitations<\/h3>\n\n<p>No findings is not a safety guarantee. Incomplete checks and absent observations remain distinct. WordPress cron depends on site traffic or a hosting cron runner. Reports use the latest ingested snapshot, not an unfinished scan. Local review and suppression do not change service-side detection or notification verdicts.<\/p>\n\n<h3>Support<\/h3>\n\n<p>Email: dancho.danchev@hush.com\nWhatsApp: https:\/\/wa.me\/359876893890<\/p>\n\n<!--section=installation-->\n<ol>\n<li>Upload and activate exploitshield-domain-monitor.zip.<\/li>\n<li>Confirm the protected website in Settings.<\/li>\n<li>Complete ownership verification and activation in Billing.<\/li>\n<li>Refresh the assessment after monitoring starts.<\/li>\n<li>When upgrading, replace the existing plugin and refresh. A matching monitoring-service API release is required.<\/li>\n<\/ol>\n\n<!--section=changelog-->\n<h4>4.1.5<\/h4>\n\n<ul>\n<li>WordPress.org review remediation: adds the owner WordPress.org username to Contributors, documents external services, removes the third-party QR-code image service, and ships human-readable JavaScript source with no build step.<\/li>\n<\/ul>\n\n<h4>4.1.4<\/h4>\n\n<ul>\n<li>WordPress Plugin Check compliance pass: adds required license header, readme compatibility header, escaped output, safer file deletion, sanitized request handling, and normalized line endings.<\/li>\n<\/ul>\n\n<h4>4.1.3<\/h4>\n\n<ul>\n<li>Retires legacy virtual-machine module option names from the active scan controls.<\/li>\n<li>Uses Sandboxie-isolated browser collection as the required protected crawler environment for Maximum Detection.<\/li>\n<\/ul>\n\n<h4>4.1.2<\/h4>\n\n<ul>\n<li>Reflects the backend parallel Sandboxie crawler queue for concurrent protected crawl scans.<\/li>\n<li>Clarifies that Maximum Detection uses service-managed Sandboxie isolation and that each queued scan consumes one API credit.<\/li>\n<\/ul>\n\n<h4>4.0.0<\/h4>\n\n<ul>\n<li>Guided threat explanations, lifecycle pivots, persistence cells and payload evolution.<\/li>\n<li>Reversible case grouping, saved filters, searchable glossary and private case links.<\/li>\n<li>Reviewer and maintainer roles with server-enforced action permissions.<\/li>\n<li>Executive and developer-handoff reports with linked contents and assessment fingerprints.<\/li>\n<li>Opt-in overdue escalation rules, delivery preview and exact future job references.<\/li>\n<li>Explicit collection failures, bounded evidence previews and incremental refresh.<\/li>\n<\/ul>\n\n<h4>3.0.0<\/h4>\n\n<ul>\n<li>Case-based investigations with six detail sections and bulk review actions.<\/li>\n<li>Server-stored response history, bounded text attachments and consent-based support tickets.<\/li>\n<li>Artifact verdict matrices, recorded relationship views and provider context.<\/li>\n<li>Authorized verification scans and case\/date-bounded monitoring PDF reports.<\/li>\n<li>Timezone-aware service schedules with one catch-up request and durable backoff.<\/li>\n<li>Quiet hours, case subscriptions and queued\/accepted\/failed email activity.<\/li>\n<li>Admin-only client investigation dossier and attachment viewer.<\/li>\n<li>Existing individual findings and reports remain available under Evidence and Reports.<\/li>\n<\/ul>\n\n<h4>2.0.0<\/h4>\n\n<ul>\n<li>Threat inbox with saved views, date pivots, CSV export and accessible charts.<\/li>\n<li>Evidence details, scanner matches, redirect relationships and persistence matrix.<\/li>\n<li>Local review history, assignment, acknowledgement and expiring suppression.<\/li>\n<li>Assessment comparisons, coverage and qualified scan states.<\/li>\n<li>Detection presets mapped to optional service checks; mandatory collection protected.<\/li>\n<li>Notification preference synchronization and scheduled requests.<\/li>\n<li>Client-safe API projection, reports, help and diagnostics.<\/li>\n<li>Responsive layout corrections.<\/li>\n<\/ul>","raw_excerpt":"Threat-first, domain-scoped security monitoring inside WordPress.","jetpack_sharing_enabled":true,"_links":{"self":[{"href":"https:\/\/wordpress.org\/plugins\/wp-json\/wp\/v2\/plugin\/376829","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/wordpress.org\/plugins\/wp-json\/wp\/v2\/plugin"}],"about":[{"href":"https:\/\/wordpress.org\/plugins\/wp-json\/wp\/v2\/types\/plugin"}],"replies":[{"embeddable":true,"href":"https:\/\/wordpress.org\/plugins\/wp-json\/wp\/v2\/comments?post=376829"}],"author":[{"embeddable":true,"href":"https:\/\/wordpress.org\/plugins\/wp-json\/wporg\/v1\/users\/ddanchev"}],"wp:attachment":[{"href":"https:\/\/wordpress.org\/plugins\/wp-json\/wp\/v2\/media?parent=376829"}],"wp:term":[{"taxonomy":"plugin_section","embeddable":true,"href":"https:\/\/wordpress.org\/plugins\/wp-json\/wp\/v2\/plugin_section?post=376829"},{"taxonomy":"plugin_tags","embeddable":true,"href":"https:\/\/wordpress.org\/plugins\/wp-json\/wp\/v2\/plugin_tags?post=376829"},{"taxonomy":"plugin_category","embeddable":true,"href":"https:\/\/wordpress.org\/plugins\/wp-json\/wp\/v2\/plugin_category?post=376829"},{"taxonomy":"plugin_contributors","embeddable":true,"href":"https:\/\/wordpress.org\/plugins\/wp-json\/wp\/v2\/plugin_contributors?post=376829"},{"taxonomy":"plugin_business_model","embeddable":true,"href":"https:\/\/wordpress.org\/plugins\/wp-json\/wp\/v2\/plugin_business_model?post=376829"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}