Vidal Security Decoy Wordpress Plugin - Rating, Reviews, Demo & Download
Plugin Description
Vidal Security Decoy does not block anyone. It lies to whoever insists on guessing your password:
- An IP that accumulates several failed logins (5 by default, in 10 minutes) gets flagged.
- From that moment, its next login attempts “succeed” — into a fake wp-admin: dashboard, posts, orders, users and settings, all invented locally, with unique canary email addresses under a subdomain of your own domain.
- With the secret door disabled, valid credentials continue through normal WordPress authentication. The trap is only for guessers.
- Everything the attacker does inside the mirage is logged locally. Passwords they try are stored only as metadata (length and composition) — never in plain text, never hashed for reversal.
- A progressive slow-down (capped at 3 seconds) makes each attempt more expensive.
The bait backup
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 honeytoken_backup event. The backup is invented locally, like everything else in the mirage, and it carries marks:
- A list of canary email addresses under a subdomain of your own domain (the same canaries the fake admin shows).
- 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 — no real person’s data) and an HTML report that phones home to your own site when opened, logging a
regalo_vistoevent with the session code. The add-on is not part of this package.
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.
Real traffic: how many of your visits are people? (new in 0.3.9)
The panel now answers the question owners actually ask — “how many real people are visiting my website?” — by quietly classifying the public front-end page loads it counts locally:
- Likely person — an ordinary browser with no marks against it.
- Good bot — a known crawler, named: Googlebot, Bingbot, DuckDuckBot, Yandex, Baidu, Applebot, and other recognisable crawlers.
- Suspicious bot — a tool or library user-agent (curl, Python, scrapers), an empty one, or one no browser would send.
- Proven bad bot — 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.
What exactly is counted, and where it stays:
- 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.
- 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 — the minimum that certainly happened — never as a complete census.
- 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 — 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.
- For visitors classified as people, no IP address or personal data is stored — 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.
- This traffic data never leaves your site: it creates no decoy event and is never part of the sensor-network reports described below.
- 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.
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.
The secret door (new in 0.2)
WordPress will not let anyone rename the wp-admin folder — but the door attackers actually use is the login, and that one moves:
- You pick a secret slug (for example
/my-own-door-42). Your real login now lives there, with your usual password. - The classic
/wp-login.phpbecomes the decoy’s front door: without a real session, any password “works” — straight into the fake admin. - 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.
And the door is never advertised: with the door on, /wp-admin answers 404 to anyone without a real session (WordPress would otherwise redirect strangers straight to your secret login URL), while /wp-login.php keeps playing the decoy. If your own session expires and you land on that 404, just open your secret door directly — that is the point of it.
Off by default; multisite networks are not supported for the door (the IP trap still works there).
Honest limits
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 — what moves is the login.
External services
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:
- Service terms: https://v8.vidalbooking.com/downloads/vidal-security-decoy-terms.html
- Privacy policy: https://v8.vidalbooking.com/downloads/vidal-security-decoy-privacy.html
Installation counter and free licence (/flow/contador)
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.
What data is sent, and when:
- Activation — 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.
- Weekly heartbeat — only while a licence is active: the plugin slug, the installation ID, the licence and the current plugin version.
- Uninstall — 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.
Nothing else is sent to this service: no email addresses, no users, no content and no visitor IP addresses.
This service is provided by Vidal Digital Miami. Terms of service: https://v8.vidalbooking.com/downloads/vidal-security-decoy-terms.html — Privacy policy: https://v8.vidalbooking.com/downloads/vidal-security-decoy-privacy.html
Vidal sensor network (/flow/senuelo/reportar and /flow/senuelo/paquete)
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.
What data is sent, and when: only when an administrator turns on “Report to the network” under Vidal Decoy Settings AND a free licence is active. The setting is off by default and both conditions are required.
- 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 — never the password itself, and never data of the site’s real users). Since 0.3.7 the events also include
regalo_visto: the unique code of a bait backup copy whose HTML report was opened somewhere, together with the IP address that opened it. - 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.
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.
This service is provided by Vidal Digital Miami. Terms of service: https://v8.vidalbooking.com/downloads/vidal-security-decoy-terms.html — Privacy policy: https://v8.vidalbooking.com/downloads/vidal-security-decoy-privacy.html
Support link
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.
Screenshots
No screenshots provided
