{"id":405970,"date":"2026-11-16T15:48:21","date_gmt":"2026-11-16T15:48:21","guid":{"rendered":"https:\/\/wordpress.org\/plugins\/vidal-security-decoy\/"},"modified":"2026-11-16T18:13:37","modified_gmt":"2026-11-16T18:13:37","slug":"vidal-security-decoy","status":"publish","type":"plugin","link":"https:\/\/wordpress.org\/plugins\/vidal-security-decoy\/","author":11950910,"comment_status":"closed","ping_status":"closed","template":"","meta":{"version":"0.6.0","stable_tag":"0.6.0","tested":"7.1.4","requires":"5.8","requires_php":"7.4","requires_plugins":null,"header_name":"Vidal Security Decoy","header_author":"Vidal Digital Miami","header_description":"Big-company deception technology for your small website. Whoever keeps guessing your password \"logs in\" \u2014 to a fake dashboard with invented data and trackable canaries \u2014 while your real admin never notices. A secret login door, honeytoken traps and an optional sensor network included.","last_updated":"2026-11-16 18:13:37","external_support_url":"","external_repository_url":"","donate_link":"","header_plugin_uri":"https:\/\/vidalforensics.com","header_author_uri":"https:\/\/vidaldigitalmiami.com","rating":0,"author_block_rating":0,"active_installs":0,"downloads":78,"num_ratings":0,"support_threads":0,"support_threads_resolved":0,"author_block_count":0,"sections":["description","installation","changelog"],"tags":{"0.5.0":{"tag":"0.5.0","author":"jmvidal2013","date":"2026-11-16 15:47:57","revision":3805496},"0.5.1":{"tag":"0.5.1","author":"jmvidal2013","date":"2026-11-16 17:40:05","revision":3805735},"0.6.0":{"tag":"0.6.0","author":"jmvidal2013","date":"2026-11-16 18:13:37","revision":3805823}},"upgrade_notice":[],"ratings":[],"assets_icons":{"icon-128x128.png":{"filename":"icon-128x128.png","revision":3805515,"resolution":"128x128","location":"assets","locale":"","width":128,"height":128},"icon-256x256.png":{"filename":"icon-256x256.png","revision":3805515,"resolution":"256x256","location":"assets","locale":"","width":256,"height":256}},"assets_banners":{"banner-1544x500.png":{"filename":"banner-1544x500.png","revision":3805526,"resolution":"1544x500","location":"assets","locale":"","width":1544,"height":500},"banner-772x250.png":{"filename":"banner-772x250.png","revision":3805526,"resolution":"772x250","location":"assets","locale":"","width":772,"height":250}},"assets_blueprints":{},"all_blocks":[],"tagged_versions":["0.5.0","0.5.1","0.6.0"],"block_files":[],"assets_screenshots":[],"screenshots":[]},"plugin_section":[],"plugin_tags":[293187,293186,598,602,600],"plugin_category":[38,54],"plugin_contributors":[274876],"plugin_business_model":[],"class_list":["post-405970","plugin","type-plugin","status-publish","hentry","plugin_tags-deception","plugin_tags-decoy","plugin_tags-honeypot","plugin_tags-login","plugin_tags-security","plugin_category-authentication","plugin_category-security-and-spam-protection","plugin_contributors-jmvidal2013","plugin_committers-jmvidal2013"],"banners":{"banner":"https:\/\/ps.w.org\/vidal-security-decoy\/assets\/banner-772x250.png?rev=3805526","banner_2x":"https:\/\/ps.w.org\/vidal-security-decoy\/assets\/banner-1544x500.png?rev=3805526","banner_rtl":false,"banner_2x_rtl":false},"icons":{"svg":false,"icon":"https:\/\/ps.w.org\/vidal-security-decoy\/assets\/icon-128x128.png?rev=3805515","icon_2x":"https:\/\/ps.w.org\/vidal-security-decoy\/assets\/icon-256x256.png?rev=3805515","generated":false},"screenshots":[],"raw_content":"<!--section=description-->\n<p>Vidal Security Decoy does not block anyone. It <strong>lies<\/strong> to whoever insists on guessing your password:<\/p>\n\n<ol>\n<li>An IP that accumulates several failed logins (5 by default, in 10 minutes) gets flagged.<\/li>\n<li>From that moment, its next login attempts \"succeed\" \u2014 into a <strong>fake wp-admin<\/strong>: dashboard, posts, orders, users and settings, all invented locally, with unique canary email addresses under a subdomain of your own domain.<\/li>\n<li>With the secret door disabled, valid credentials continue through normal WordPress authentication. The trap is only for guessers.<\/li>\n<li>Everything the attacker does inside the mirage is logged locally. Passwords they try are stored only as metadata (length and composition) \u2014 never in plain text, never hashed for reversal.<\/li>\n<li>A progressive slow-down (capped at 3 seconds) makes each attempt more expensive.<\/li>\n<\/ol>\n\n<h4>The bait backup<\/h4>\n\n<p>The mirage dangles one more prize: a \"full site backup\" download at a predictable address. Nobody legitimate has any reason to fetch it, so touching it is logged as a <code>honeytoken_backup<\/code> event. The backup is invented locally, like everything else in the mirage, and it carries marks:<\/p>\n\n<ul>\n<li>A list of canary email addresses under a subdomain of your own domain (the same canaries the fake admin shows).<\/li>\n<li>A free companion add-on, distributed through the author's own channel to licensed installs, extends this bait with a larger synthetic customer export (invented locally, with canary addresses under your own domain and structurally invalid account numbers \u2014 no real person's data) and an HTML report that phones home to <strong>your own site<\/strong> when opened, logging a <code>regalo_visto<\/code> event with the session code. The add-on is not part of this package.<\/li>\n<\/ul>\n\n<p>Those events are recorded locally like every other decoy event. They only leave your site if you turned on the optional sensor network described below.<\/p>\n\n<h4>Real traffic: how many of your visits are people? (new in 0.3.9)<\/h4>\n\n<p>The panel now answers the question owners actually ask \u2014 \"how many real people are visiting my website?\" \u2014 by quietly classifying the public front-end page loads it counts locally:<\/p>\n\n<ul>\n<li><strong>Likely person<\/strong> \u2014 an ordinary browser with no marks against it.<\/li>\n<li><strong>Good bot<\/strong> \u2014 a known crawler, named: Googlebot, Bingbot, DuckDuckBot, Yandex, Baidu, Applebot, and other recognisable crawlers.<\/li>\n<li><strong>Suspicious bot<\/strong> \u2014 a tool or library user-agent (curl, Python, scrapers), an empty one, or one no browser would send.<\/li>\n<li><strong>Proven bad bot<\/strong> \u2014 the visitor's IP is flagged by the decoy itself, or has mirage \/ bait-backup evidence in the local log. That verdict comes from this plugin's own evidence, not from a guess.<\/li>\n<\/ul>\n\n<p>What exactly is counted, and where it stays:<\/p>\n\n<ul>\n<li>Only public front-end page loads are counted. The admin area, logged-in users, feeds, the REST API, assets and the decoy's own pages are not counted.<\/li>\n<li>Visits are counted at the moment WordPress serves the page, so if a full-page cache (a caching plugin or your hosting) serves a visit without running PHP, that visit is never counted: read every figure as a floor \u2014 the minimum that certainly happened \u2014 never as a complete census.<\/li>\n<li>The counting is entirely local: daily counters per class and a per-bot summary (name, verdict, visit count, last seen, and the IP of suspicious or proven-bad bots \u2014 the same kind of attacker IP data the decoy already stores in its event log). * The aggregate lives in the same evidence store as the rest of the decoy's data: a private folder outside the public root when the server allows it, otherwise a sealed folder under uploads or wp-content. Since 0.5.0 every data file is encrypted at rest with AES-256-GCM (the key lives in a WordPress option, never in the data folder) and saved as a PHP file with a guard line, so it is protected against direct web access even on Nginx or IIS servers; files written by older versions in plain form are migrated to the encrypted form automatically on first use.<\/li>\n<li>For visitors classified as people, no IP address or personal data is stored \u2014 only an irreversible one-way hash of IP + browser string, used to estimate how many visitors return from one day to the next. Those hashes are deleted after 48 hours.<\/li>\n<li>This traffic data never leaves your site: it creates no decoy event and is never part of the sensor-network reports described below.<\/li>\n<li>The headline figure is labelled as what it is: a probable classification with a margin of error, shown next to the number in the panel. A bot disguised as a browser counts as a person until the trap catches it.<\/li>\n<\/ul>\n\n<p>The summary (people today and over 7 days, the class split, the named bot list with verdicts) is free. The Pro plan unlocks the 30-day daily history, the per-IP detail and the per-page time series for real customers.<\/p>\n\n<h4>The secret door (new in 0.2)<\/h4>\n\n<p>WordPress will not let anyone rename the wp-admin folder \u2014 but the door attackers actually use is the <strong>login<\/strong>, and that one moves:<\/p>\n\n<ol>\n<li>You pick a secret slug (for example <code>\/my-own-door-42<\/code>). Your real login now lives there, with your usual password.<\/li>\n<li>The classic <code>\/wp-login.php<\/code> becomes the decoy's front door: without a real session, any password \"works\" \u2014 straight into the fake admin.<\/li>\n<li>Already logged in? The classic door stays real for you. A rescue link (shown only in your Decoy panel) opens the real login if you ever lose the secret address, and deactivating the plugin turns the door off.<\/li>\n<\/ol>\n\n<p>And the door is never advertised: with the door on, <code>\/wp-admin<\/code> answers <strong>404<\/strong> to anyone without a real session (WordPress would otherwise redirect strangers straight to your secret login URL), while <code>\/wp-login.php<\/code> keeps playing the decoy. If your own session expires and you land on that 404, just open your secret door directly \u2014 that is the point of it.<\/p>\n\n<p>Off by default; multisite networks are not supported for the door (the IP trap still works there).<\/p>\n\n<h4>Honest limits<\/h4>\n\n<p>No tool can promise 100% security. This decoy stops and studies guessers; it does not replace updates, real passwords or two-factor authentication on your real account. The secret door covers the web login form; XML-RPC and the REST API keep existing (the IP trap still watches authentication failures there), and the wp-admin folder itself keeps its name \u2014 what moves is the login.<\/p>\n\n<h3>External services<\/h3>\n\n<p>This plugin works fully on its own. It can optionally talk to two services operated by Vidal Digital Miami on https:\/\/v8.vidalbooking.com. Both are covered by the same legal texts:<\/p>\n\n<ul>\n<li>Service terms: https:\/\/v8.vidalbooking.com\/downloads\/vidal-security-decoy-terms.html<\/li>\n<li>Privacy policy: https:\/\/v8.vidalbooking.com\/downloads\/vidal-security-decoy-privacy.html<\/li>\n<\/ul>\n\n<h4>Installation counter and free licence (\/flow\/contador)<\/h4>\n\n<p>What it is: a plain counter of the active installations of Vidal's free plugins, run by Vidal Digital Miami so the author knows how many sites run them. The plugin is fully functional whether you join or not.<\/p>\n\n<p>What data is sent, and when:<\/p>\n\n<ul>\n<li>Activation \u2014 only when an administrator clicks \"Activate FREE Licence\" in the plugin panel or the admin notice: the site URL, the plugin slug (vidal-security-decoy) and the plugin version. The service answers with an installation ID and a free licence key, which the plugin stores.<\/li>\n<li>Weekly heartbeat \u2014 only while a licence is active: the plugin slug, the installation ID, the licence and the current plugin version.<\/li>\n<li>Uninstall \u2014 only if a licence was active: the plugin slug, the installation ID and the licence, so the installation stops being counted and its counter record is deleted.<\/li>\n<\/ul>\n\n<p>Nothing else is sent to this service: no email addresses, no users, no content and no visitor IP addresses.<\/p>\n\n<p>This service is provided by Vidal Digital Miami. Terms of service: https:\/\/v8.vidalbooking.com\/downloads\/vidal-security-decoy-terms.html \u2014 Privacy policy: https:\/\/v8.vidalbooking.com\/downloads\/vidal-security-decoy-privacy.html<\/p>\n\n<h4>Vidal sensor network (\/flow\/senuelo\/reportar and \/flow\/senuelo\/paquete)<\/h4>\n\n<p>What it is: an optional, shared early-warning network among sites running Vidal decoys. Sites that opt in report decoy events to the central service and, in exchange, receive a signed daily list of the IP addresses the whole network has condemned, so those IPs are diverted to the decoy before they ever knock.<\/p>\n\n<p>What data is sent, and when: only when an administrator turns on \"Report to the network\" under Vidal Decoy \u2192 Settings AND a free licence is active. The setting is off by default and both conditions are required.<\/p>\n\n<ul>\n<li>Reports, twice a day: the site URL, the installation ID and the licence, plus the queued decoy events. Each event contains the attacking visitor's IP address, the timestamp, the event type, the username that visitor attempted, the decoy route or action involved, and password metadata (length and character classes only \u2014 never the password itself, and never data of the site's real users). Since 0.3.7 the events also include <code>regalo_visto<\/code>: the unique code of a bait backup copy whose HTML report was opened somewhere, together with the IP address that opened it.<\/li>\n<li>Quarantine download, once a day: the plugin asks the service for the signed package, sending the site URL, the installation ID and the licence. The package is verified against an HMAC signature made with your own licence before a single IP is applied. Network marks are stored separately from local marks, and your own whitelist always wins over the network list.<\/li>\n<\/ul>\n\n<p>Clear the reporting checkbox and save to stop new reports and stop applying the network list. Event reports already sent are kept by the service for up to 90 days and then deleted, as described in the privacy policy linked above.<\/p>\n\n<p>This service is provided by Vidal Digital Miami. Terms of service: https:\/\/v8.vidalbooking.com\/downloads\/vidal-security-decoy-terms.html \u2014 Privacy policy: https:\/\/v8.vidalbooking.com\/downloads\/vidal-security-decoy-privacy.html<\/p>\n\n<h4>Support link<\/h4>\n\n<p>The \"Open a support ticket\" button in the plugin panel opens https:\/\/vidalforensics.com\/decoy-support.html in your browser with the site URL, the plugin version and the form language prefilled. This happens only when you click the button; nothing is sent in the background.<\/p>\n\n<!--section=installation-->\n<ol>\n<li>In WordPress, go to Plugins \u2192 Add New \u2192 Upload Plugin, select the ZIP, and activate it.<\/li>\n<li>Open Vidal Decoy to review settings and confirm that the plugin can write its evidence store: a private folder outside the public root when the server allows it, otherwise a sealed folder under uploads or wp-content (denied to web access with an .htaccess rule and a silent index.php). The plugin needs that folder for local logging and IP marks, and it encrypts everything it stores there (AES-256-GCM; the key is kept in a WordPress option \u2014 if you ever restore a database backup without the plugin's options, old evidence can no longer be read, by design).<\/li>\n<li>If upgrading from a build that stored evidence in wp-content\/vsd-data, verify that the old directory is inaccessible over HTTP. The plugin migrates known files to the private directory when it can do so without overwriting existing evidence.<\/li>\n<\/ol>\n\n<!--section=changelog-->\n<h4>0.6.0<\/h4>\n\n<ul>\n<li>New: AI bot monitor in the traffic panel. The Decoy now names the AI crawlers that visit your site (GPTBot, OAI-SearchBot, ChatGPT-User, ClaudeBot, PerplexityBot and more), separates them by purpose \u2014 search indexing, fetched at a user's request, or training \u2014 and verifies them: anyone can claim an AI bot's name, so the panel checks the visitor IP's reverse DNS against the company's official domain and flags unverified impostors. The 7-day summary is free; Pro adds the pages each AI bot reads.<\/li>\n<\/ul>\n\n<h4>0.5.2<\/h4>\n\n<ul>\n<li>Fix: the rescue address is now always visible in the secret-door card, even while the door is off \u2014 regenerating the rescue key no longer points to an address that is nowhere on the page.<\/li>\n<\/ul>\n\n<h4>0.5.1<\/h4>\n\n<ul>\n<li>Fix: the verdict colours in the traffic panel now match the summary at the top \u2014 probable people are green, good bots are blue. Display only; the classification itself is unchanged.<\/li>\n<\/ul>\n\n<h4>0.5.0<\/h4>\n\n<ul>\n<li>One single source: the WordPress.org package and the author's own channel now ship the same code (the only difference is the channel's own updater file, which this package omits). Prefixes are vidasede everywhere, as in 0.3.7+.<\/li>\n<li>The evidence store is now encrypted at rest with AES-256-GCM: IP marks, event log, report queue and traffic aggregates. The key lives in a WordPress option, never in the data folder; if encrypted evidence exists and its key is missing, the store refuses to write rather than fall back to plain text. Plain files from older versions are read as before and rewritten encrypted automatically, and stores from both old lines (the channel's private folder outside the public root, and the uploads folder used by this line) are found and kept in place \u2014 no evidence moves or is lost on upgrade.<\/li>\n<li>FREE licence activation no longer depends on the shared counter notice: the panel's own \"Activate FREE license\" button is served by a rescue handler in the plugin itself, so another Vidal plugin registering first on the shared activation hook can no longer kill the click (\"The link you followed has expired\").<\/li>\n<li>The panel now shows your plan at a glance: a PRO \/ FREE \/ NOT ACTIVATED badge next to the licence line.<\/li>\n<li>The bait backup keeps its canary list in the core. The extended bank bait (a large synthetic customer export whose account numbers are structurally invalid, plus the call-home HTML report) now ships as a separate free companion add-on through the author's own channel, for licensed installs only; it is not part of this package.<\/li>\n<\/ul>\n\n<h4>0.4.x (author's own channel)<\/h4>\n\n<ul>\n<li>Pro plan with licence key: login shield for flagged IPs, a wp-config bait link inside the mirage, email alerts and evidence export; larger network quarantine packages for Pro installs.<\/li>\n<li>Real traffic detail levels in the panel and the plan badge.<\/li>\n<li>The network reporter sends outside the queue lock with deterministic batch IDs (the same fix shipped here as 0.3.11).<\/li>\n<\/ul>\n\n<h4>0.3.11<\/h4>\n\n<ul>\n<li>Under the hood (no visible change): the sensor-network reporter no longer holds the queue lock while it talks to the network \u2014 it prepares the batch, releases the lock, sends, and confirms in a short second step. Each batch carries a deterministic ID, so if a process dies between send and confirmation the retry re-sends the same batch with the same ID and the network can drop the duplicate instead of counting it twice.<\/li>\n<li>Data files are now stored protected against direct access on any server: they are saved as .php files with a guard line (the server executes them and outputs nothing instead of serving their contents), which closes the gap on Nginx\/IIS hosts where .htaccess rules do not apply. Plain files from older versions are read as before and rewritten in the protected form automatically.<\/li>\n<li>Real traffic counting no longer rewrites the whole aggregate file on every visit: each visit appends a tiny increment (one short locked append) and the panel consolidates increments when it is read. Same figures, same caps \u2014 but under a burst of 30 simultaneous visits the old design made each visit wait for the full aggregate transaction (~30x slower per visit); the append design does not.<\/li>\n<\/ul>\n\n<h4>0.3.10<\/h4>\n\n<ul>\n<li>Honesty fix in the Real traffic block: the headline figure is now labelled \"probable people\" (today and 7 days), matching the probable-classification note that already sits next to it. An advanced bot disguised as a browser can count as a person until the trap catches it, so the label no longer claims more certainty than the classification provides. Presentation only \u2014 the counting and classification are unchanged.<\/li>\n<\/ul>\n\n<h4>0.3.9<\/h4>\n\n<ul>\n<li>New \"Real traffic\" block in the panel: the plugin now counts public front-end page loads locally and classifies each visit as a likely person, a good bot (known crawlers, named), a suspicious bot (tool\/library user-agents) or a proven bad bot (an IP flagged by the decoy itself, or with mirage\/bait evidence). The panel leads with \"real people today\" and the 7-day figure, shows the class split and the bot list with verdicts, and labels the figure as a probable classification with a margin of error.<\/li>\n<li>The counting is local and aggregated only: no IP is stored for visitors classified as people (returning visitors are estimated with a one-way hash that is deleted after 48 hours), and no traffic data ever leaves the site \u2014 it is not part of the sensor-network reports. Full detail in the Description section.<\/li>\n<li>Pro plan: 30-day daily history, per-IP detail and per-page time series for real customers.<\/li>\n<\/ul>\n\n<h4>0.3.8<\/h4>\n\n<ul>\n<li>The panel now flags the moment of the catch: in the recent-events list, the row where a marked IP \"logged in\" to the mirage with a password (espejismo_login) is highlighted in red, with its IP in bold and an \"ENTR\u00d3 AL ESPEJISMO\" label, so the site owner spots it at a glance. Presentation only \u2014 the trap itself is unchanged.<\/li>\n<\/ul>\n\n<h4>0.3.7<\/h4>\n\n<ul>\n<li>The bait backup grows marks: it now also includes a small list of invented shop customers (all canary addresses under your own domain, generated locally \u2014 no real person's data) with one row carrying the downloading session's unique code, and an HTML customer report whose 1\u00d71 image points back to your own site. Opening that report anywhere logs a regalo_visto event (code, opener IP, time) locally; like every decoy event, it only travels to the sensor network if you opted in.<\/li>\n<li>WordPress.org review fixes: every plugin prefix renamed from the too-short vsd to vidasede (classes, constants, options, cron hooks, transients, form fields and file names), as suggested by the review team.<\/li>\n<li>The evidence store now lives in a protected folder under the WordPress uploads directory (located with wp_upload_dir()), sealed with a silent index.php and a deny-all .htaccess; records kept by earlier builds in wp-content\/vsd-data are migrated on upgrade. Uninstall cleans that same location when the full-wipe opt-in is set.<\/li>\n<\/ul>\n\n<h4>0.3.5<\/h4>\n\n<ul>\n<li>WordPress.org review fixes: every superglobal input is sanitized on receipt and the visitor IP is validated before it is stored or reported; the decoy login pages no longer carry a \"Powered by WordPress\" credit link; login URLs are built with site_url() so installs with WordPress in a subdirectory resolve correctly; uninstall uses the store path saved at activation instead of deriving it from the content directory layout.<\/li>\n<li>The External services section now documents each Vidal service separately \u2014 what it is, what data is sent and when \u2014 and links to its terms of service and privacy policy.<\/li>\n<\/ul>\n\n<h4>0.3.4<\/h4>\n\n<ul>\n<li>Uses the WordPress.org update channel.<\/li>\n<li>Requires a separate opt-in for network reports and the network IP list.<\/li>\n<li>Stores new forensic records only outside the public document root.<\/li>\n<\/ul>\n\n<h4>0.3.2<\/h4>\n\n<ul>\n<li>New Support card in the Decoy panel: one button opens the ticket form (site URL and plugin version prefilled) and support answers by email \u2014 the email-first route, inside the plugin.<\/li>\n<\/ul>\n\n<h4>0.3.1<\/h4>\n\n<ul>\n<li>The \"Activar licencia FREE\" button now lives permanently inside the Decoy panel itself (visible only while the licence is not active), instead of depending on the dismissible admin notice \u2014 the notice still appears on install day and weekly until activation, but the panel is now the always-there way in. Same one-click activation, same three data points (site URL, plugin name, version), still fully optional.<\/li>\n<\/ul>\n\n<h4>0.3.0<\/h4>\n\n<ul>\n<li>The network is live: with reporting on and a free licence active, the decoy's queued events now travel to the Vidal central twice a day (the receiver exists and only listens to valid licences).<\/li>\n<li>In exchange, this site receives the network quarantine once a day: IPs condemned by the whole network with a real signal (honeytoken touched, a canary used outside its home site, a burst of events, or activity across several sensors) get marked here too \u2014 before they ever knock. The package is signed with your own licence as the key; a tampered package is rejected whole.<\/li>\n<li>Network marks live apart from local marks: clearing your local marks never clears the network quarantine, and your own whitelisted IP always wins over the network list.<\/li>\n<\/ul>\n\n<h4>0.2.3<\/h4>\n\n<ul>\n<li>Fixed: the mirage now answers FIRST. After a fake login, WordPress used to bounce the visitor to the real login before the fake admin could render \u2014 the mirage existed but never got its turn. The decoy session is now served early, before that bounce.<\/li>\n<li>The decoy session cookie no longer depends on the visitor's IP (attackers behind NAT\/proxies rotate IPs between requests, which silently killed the mirage session); it stays bound to the browser and expires in 2 hours.<\/li>\n<\/ul>\n\n<h4>0.2.2<\/h4>\n\n<ul>\n<li>Storage hardening: file locks and atomic writes for the event log, the IP marks and the report queue (no more lost records under simultaneous hits); evidence files are 0600.<\/li>\n<li>Evidence now lives outside the public root when the server allows it (a private folder, 0700), migrating the old records without overwriting; where that is not writable it falls back to the protected wp-content folder (denied by .htaccess) \u2014 the trap never goes silent.<\/li>\n<li>Trusted IPs (whitelisted after a real login) now expire after 24 hours, and stale mark entries are cleaned up automatically.<\/li>\n<li>Door links: plain generated links to wp-login.php no longer publish the secret slug to strangers \u2014 but password-recovery links (with a key) always land on the real door, so a reset never dies in the fake login.<\/li>\n<li>Uninstall now preserves the evidence by default (it is forensic material); a full wipe requires an explicit opt-in set beforehand.<\/li>\n<li>The mirage no longer intercepts admin-ajax\/admin-post: those endpoints answer like a real logged-out WordPress.<\/li>\n<\/ul>\n\n<h4>0.2.1<\/h4>\n\n<ul>\n<li>The secret door no longer leaks: \/wp-admin without a real session returns the site's 404 instead of redirecting to the secret login URL. admin-ajax\/admin-post stay reachable and mirage visitors are unaffected.<\/li>\n<\/ul>\n\n<h4>0.2.0<\/h4>\n\n<ul>\n<li>The secret door: move your real login to a slug only you know; \/wp-login.php becomes the decoy's fake login (fake password-reset flow included). Rescue link in the owner panel, plugin deactivation always restores the classic login. Off by default; multisite not supported for the door.<\/li>\n<\/ul>\n\n<h4>0.1.0<\/h4>\n\n<ul>\n<li>First release: login trap, fake admin mirage with per-install canary data, local event log, progressive tarpit, free-licence counter, queued network reporting.<\/li>\n<\/ul>","raw_excerpt":"Detect repeated login attempts and divert them to a simulated WordPress dashboard with synthetic data.","jetpack_sharing_enabled":true,"_links":{"self":[{"href":"https:\/\/wordpress.org\/plugins\/wp-json\/wp\/v2\/plugin\/405970","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=405970"}],"author":[{"embeddable":true,"href":"https:\/\/wordpress.org\/plugins\/wp-json\/wporg\/v1\/users\/jmvidal2013"}],"wp:attachment":[{"href":"https:\/\/wordpress.org\/plugins\/wp-json\/wp\/v2\/media?parent=405970"}],"wp:term":[{"taxonomy":"plugin_section","embeddable":true,"href":"https:\/\/wordpress.org\/plugins\/wp-json\/wp\/v2\/plugin_section?post=405970"},{"taxonomy":"plugin_tags","embeddable":true,"href":"https:\/\/wordpress.org\/plugins\/wp-json\/wp\/v2\/plugin_tags?post=405970"},{"taxonomy":"plugin_category","embeddable":true,"href":"https:\/\/wordpress.org\/plugins\/wp-json\/wp\/v2\/plugin_category?post=405970"},{"taxonomy":"plugin_contributors","embeddable":true,"href":"https:\/\/wordpress.org\/plugins\/wp-json\/wp\/v2\/plugin_contributors?post=405970"},{"taxonomy":"plugin_business_model","embeddable":true,"href":"https:\/\/wordpress.org\/plugins\/wp-json\/wp\/v2\/plugin_business_model?post=405970"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}