diff --git a/cdn-files/plugin-info.json b/cdn-files/plugin-info.json
index 359f0c0..326a0ec 100644
--- a/cdn-files/plugin-info.json
+++ b/cdn-files/plugin-info.json
@@ -1,17 +1,17 @@
{
"name": "WebDecoy Bot Detection",
"slug": "webdecoy",
- "version": "2.13.0",
+ "version": "2.13.1",
"author": "WebDecoy",
"author_profile": "https://webdecoy.com",
"requires": "6.1",
"tested": "7.1",
"requires_php": "7.4",
- "download_url": "https://cdn.webdecoy.com/wordpress/webdecoy-2.13.0.zip",
+ "download_url": "https://cdn.webdecoy.com/wordpress/webdecoy-2.13.1.zip",
"sections": {
"description": "
See the AI side of your traffic. WebDecoy shows which AI crawlers, AI agents and other bots read your site, whether they are who they say they are, and which AI assistants send people to your pages. Then choose what they may access. Free, on your own server, with no account.
Key Features
- AI crawler and bot counts on the dashboard and Statistics page, with DNS verification for major crawlers
- Visits sent by ChatGPT, Perplexity, Claude, Gemini, Copilot and other AI assistants, by AI product and landing page
- Automatic robots.txt: keep whole categories of bots out, kept current with each plugin update
- Block AI crawlers outright, with search engines unaffected
- Invisible form protection, hidden bot traps and WooCommerce card-testing protection
- Monitor mode by default: see what it would block before it blocks
",
"installation": "- Upload the plugin files to
/wp-content/plugins/webdecoy - Activate the plugin through the Plugins menu
- Tripwires and local protection are active out of the box — no API key required
- Optionally go to WebDecoy > Settings > WebDecoy Cloud to connect for centralized monitoring and enforcement
",
- "changelog": "2.13.0
- New: see which AI assistants send you visitors. Page visits from a link in ChatGPT, Perplexity, Claude, Gemini, Copilot and other AI products are counted by AI product and landing page, on the dashboard (7 days) and the Statistics page (30 days), with no account. Only counts are kept, nothing about the visitor.
- New: automatic robots.txt. Under Settings > Good Bots, choose categories of bots to keep out (AI training crawlers, SEO tools, scrapers and more) and WebDecoy adds a rule for every known crawler in them to the robots.txt WordPress serves. The list updates with each plugin release. Off until you choose categories.
- Changed: the plugin description now leads with AI crawler analytics, AI assistant visits and robots.txt.
- Fixed: uninstalling on multisite now also removes the crawler visit counters.
2.12.0
- Added: separate request counters on Dashboard and Statistics for WebDecoy blocks (HTTP 403), throttles (429), challenges and decisions withheld by monitor mode or safety checks. Repeated blocks count even when no new detection row is saved.
- Added: Today, 7-day and 30-day UTC calendar comparisons, with the tracking start time shown. Counts start after upgrade; historical requests are not reconstructed.
- Privacy: request counters keep only an hourly bucket, outcome and count for 30 UTC calendar days. Requests stopped by another firewall or served before WordPress are outside these counters.
- Fixed: counter storage failures do not alter the protection response or display database errors.
2.11.4
- Added: after a week on your site, WebDecoy asks once for a review on WordPress.org, naming how many bot visits it counted. Only administrators see it, only on the dashboard and WebDecoy pages, and only when bots were counted. Choose Leave a review, Maybe later or Don't ask again.
2.11.3
- Added: 14 more crawlers and bots are recognised (235 in total), including RiverBot, IsonSearchBot, Barkrowler, Stripebot, Brightbot, Cloudflare's crawl service, and security scanners from Palo Alto Networks, Recorded Future and VirusTotal.
2.11.2
- Added: 29 more crawlers and AI agents are recognised (221 in total), including Bravebot, Coc Coc, YisouSpider, KimiBot, Kimi-SearchBot, GrokBot, ElevenlabsCrawler, OAI-AdsBot, AdsBot-Google and Meta's ads crawler. Qwant and Ibou are now recognised by their current names (Qwantbot, ibou-search).
2.11.1
- Added: six more crawlers and AI agents are recognised (192 in total): PetalBot (Huawei's Petal Search), Meta-WebIndexer and ShapBot as search crawlers, ExaUser and Shap-User as AI assistants, and Manus-User as an AI agent. Exa's crawler now matches on its product token, so ExaUser is no longer counted as Exa's search crawler.
2.11.0
- New: the dashboard widget and Statistics page show the bots and AI crawlers seen on your site in the last 24 hours, split into verified, claimed and failed verification, with no account needed. Only counts are kept, never visitor addresses or user agents.
- New: the Detections page explains each decoy hit in one plain sentence.
- Changed: the plugin description now leads with card testing and fake WooCommerce orders, and no longer claims indefinite retention or that "Block AI crawlers" blocks AI search crawlers such as PerplexityBot.
- Fixed: the AI referrals table is now created on sites that upgraded past 2.10.0 instead of only on fresh activation.
2.10.6
- Fixed: classic WooCommerce checkout protection and attempt tracking now register after all plugins load. Previously, loading WebDecoy before WooCommerce silently skipped these hooks.
2.10.5
- Fixed: the warning that WebDecoy is not blocking because the site is behind an unconfigured proxy no longer appears on hosts that already pass the visitor's real address to WordPress, such as WordPress.com. On those sites blocking was being withheld for no reason.
- Fixed: the warning's "Configure trusted proxies" button, and the monitor-mode "Review and turn on blocking" button, led to a "not allowed to access this page" error. They now open the settings page.
2.10.4
- Security: good bots such as Googlebot are now verified against the visitor's real address. A visitor could previously choose the address that was checked by sending a forged forwarding header, and on sites behind Cloudflare, WooCommerce checkout checked Cloudflare's address instead of the visitor's.
- Added: the WebDecoy Cloud tab shows whether Slack and webhook alerts are on for your plan, and where to configure them.
- Changed: corrected descriptions of what WebDecoy Cloud does.
2.10.3
- Fixed: rule violations are no longer sent twice or lost while WebDecoy is briefly unavailable, and AI referral counts refused while WebDecoy was busy are kept and sent later.
2.10.2
- Fixed: pages no longer wait up to 20 seconds when WebDecoy Cloud is slow or unreachable. Detections are sent after the page is delivered, and cloud calls pause for a minute while WebDecoy is unavailable.
2.10.1
- Fixed: 2.10.0 stopped sites loading with a fatal error, "Class WebDecoy_AI_Referrals not found".
2.10.0
- Added: when connected to WebDecoy Cloud, the plugin counts visits that AI products such as ChatGPT, Claude, Perplexity and Gemini send to your site, for your AI Traffic page. Only the product name, the landing path and a count are sent; nothing about the visitor.
2.9.1
- Fixed: AI search crawlers and assistants fetching a page for a person are no longer identified as AI training crawlers (Claude-User, Claude-SearchBot, MistralAI-User; PerplexityBot is now a search crawler, as Perplexity documents it).
- Changed: with Block AI crawlers on, PerplexityBot and Claude-SearchBot are let through like other AI search crawlers. Assistants fetching for a person, such as ChatGPT-User and Claude-User, are still refused.
- Added: Perplexity-User, MistralAI-User, Meta-ExternalFetcher and Claude-SearchBot are recognised (186 crawlers).
2.9.0
- Added: per-path crawler rules set in WebDecoy Cloud now apply in WordPress too, by the same rule the edge sensor uses. Cloud rules can only refuse, never allow.
- Changed: crawlers are identified from the shared WebDecoy registry (182, was 54); with Block AI crawlers on, AI agents and assistants are refused along with training crawlers.
2.3.1
- Fixed: Detections forwarded from your site are now identified by the visitor's own request signature. Previously they were identified by your server's outgoing connection, which is the same for every visitor — so every visitor a site reported was grouped into a single "actor" in the dashboard. Only request header names plus Accept-Language and Accept-Encoding are sent; no header values leave your site.
2.3.0
- One-click WebDecoy Cloud connect with automatic key provisioning
- Monthly security report opt-in
- Plan entitlements sync (fails open to free)
- Fixed: Statistics charts growing unbounded with detection data
2.1.0
- JS execution verification to catch non-JS HTTP scrapers
- Challenge token meta tag on page serve; automatic page-serve reporting
2.0.0
- All detection and protection now works locally — no API key required
- Invisible proof-of-work challenge system (SHA-256, no external service)
- Behavioral scoring, statistics page, enhanced detections page
1.3.0
- Bulk IP blocking/unblocking; enhanced good bot detection (60+ bots)
",
+ "changelog": "2.13.1
- Added: 10 more crawlers and tools are recognised (245 in total), including TalarionSearchBot, UnfragileBot, Aranet-SearchBot, CrolBot, SperidLabsResearchCrawler, AbliterantBot, TokenFoundryBot, TernCrawler and the ARTEX penetration-testing probe. With automatic robots.txt on, the new crawlers in your chosen categories are added to it.
- Fixed: block pages and challenge responses now tell page caches not to store them, and the clearance cookie is sent with SameSite=Lax.
- Changed: dashboard and Statistics figures can be up to a minute old. Protection decisions still use live counts.
- Changed: on WordPress VIP, calls to WebDecoy use VIP's request helpers, and changing automatic robots.txt categories clears VIP's cached robots.txt.
- Changed: WebDecoy writes to the PHP error log only when WP_DEBUG is on, and then only a short event code.
- Fixed: spacing of the AI assistant visits section in the dashboard widget.
2.13.0
- New: see which AI assistants send you visitors. Page visits from a link in ChatGPT, Perplexity, Claude, Gemini, Copilot and other AI products are counted by AI product and landing page, on the dashboard (7 days) and the Statistics page (30 days), with no account. Only counts are kept, nothing about the visitor.
- New: automatic robots.txt. Under Settings > Good Bots, choose categories of bots to keep out (AI training crawlers, SEO tools, scrapers and more) and WebDecoy adds a rule for every known crawler in them to the robots.txt WordPress serves. The list updates with each plugin release. Off until you choose categories.
- Changed: the plugin description now leads with AI crawler analytics, AI assistant visits and robots.txt.
- Fixed: uninstalling on multisite now also removes the crawler visit counters.
2.12.0
- Added: separate request counters on Dashboard and Statistics for WebDecoy blocks (HTTP 403), throttles (429), challenges and decisions withheld by monitor mode or safety checks. Repeated blocks count even when no new detection row is saved.
- Added: Today, 7-day and 30-day UTC calendar comparisons, with the tracking start time shown. Counts start after upgrade; historical requests are not reconstructed.
- Privacy: request counters keep only an hourly bucket, outcome and count for 30 UTC calendar days. Requests stopped by another firewall or served before WordPress are outside these counters.
- Fixed: counter storage failures do not alter the protection response or display database errors.
2.11.4
- Added: after a week on your site, WebDecoy asks once for a review on WordPress.org, naming how many bot visits it counted. Only administrators see it, only on the dashboard and WebDecoy pages, and only when bots were counted. Choose Leave a review, Maybe later or Don't ask again.
2.11.3
- Added: 14 more crawlers and bots are recognised (235 in total), including RiverBot, IsonSearchBot, Barkrowler, Stripebot, Brightbot, Cloudflare's crawl service, and security scanners from Palo Alto Networks, Recorded Future and VirusTotal.
2.11.2
- Added: 29 more crawlers and AI agents are recognised (221 in total), including Bravebot, Coc Coc, YisouSpider, KimiBot, Kimi-SearchBot, GrokBot, ElevenlabsCrawler, OAI-AdsBot, AdsBot-Google and Meta's ads crawler. Qwant and Ibou are now recognised by their current names (Qwantbot, ibou-search).
2.11.1
- Added: six more crawlers and AI agents are recognised (192 in total): PetalBot (Huawei's Petal Search), Meta-WebIndexer and ShapBot as search crawlers, ExaUser and Shap-User as AI assistants, and Manus-User as an AI agent. Exa's crawler now matches on its product token, so ExaUser is no longer counted as Exa's search crawler.
2.11.0
- New: the dashboard widget and Statistics page show the bots and AI crawlers seen on your site in the last 24 hours, split into verified, claimed and failed verification, with no account needed. Only counts are kept, never visitor addresses or user agents.
- New: the Detections page explains each decoy hit in one plain sentence.
- Changed: the plugin description now leads with card testing and fake WooCommerce orders, and no longer claims indefinite retention or that "Block AI crawlers" blocks AI search crawlers such as PerplexityBot.
- Fixed: the AI referrals table is now created on sites that upgraded past 2.10.0 instead of only on fresh activation.
2.10.6
- Fixed: classic WooCommerce checkout protection and attempt tracking now register after all plugins load. Previously, loading WebDecoy before WooCommerce silently skipped these hooks.
2.10.5
- Fixed: the warning that WebDecoy is not blocking because the site is behind an unconfigured proxy no longer appears on hosts that already pass the visitor's real address to WordPress, such as WordPress.com. On those sites blocking was being withheld for no reason.
- Fixed: the warning's "Configure trusted proxies" button, and the monitor-mode "Review and turn on blocking" button, led to a "not allowed to access this page" error. They now open the settings page.
2.10.4
- Security: good bots such as Googlebot are now verified against the visitor's real address. A visitor could previously choose the address that was checked by sending a forged forwarding header, and on sites behind Cloudflare, WooCommerce checkout checked Cloudflare's address instead of the visitor's.
- Added: the WebDecoy Cloud tab shows whether Slack and webhook alerts are on for your plan, and where to configure them.
- Changed: corrected descriptions of what WebDecoy Cloud does.
2.10.3
- Fixed: rule violations are no longer sent twice or lost while WebDecoy is briefly unavailable, and AI referral counts refused while WebDecoy was busy are kept and sent later.
2.10.2
- Fixed: pages no longer wait up to 20 seconds when WebDecoy Cloud is slow or unreachable. Detections are sent after the page is delivered, and cloud calls pause for a minute while WebDecoy is unavailable.
2.10.1
- Fixed: 2.10.0 stopped sites loading with a fatal error, "Class WebDecoy_AI_Referrals not found".
2.10.0
- Added: when connected to WebDecoy Cloud, the plugin counts visits that AI products such as ChatGPT, Claude, Perplexity and Gemini send to your site, for your AI Traffic page. Only the product name, the landing path and a count are sent; nothing about the visitor.
2.9.1
- Fixed: AI search crawlers and assistants fetching a page for a person are no longer identified as AI training crawlers (Claude-User, Claude-SearchBot, MistralAI-User; PerplexityBot is now a search crawler, as Perplexity documents it).
- Changed: with Block AI crawlers on, PerplexityBot and Claude-SearchBot are let through like other AI search crawlers. Assistants fetching for a person, such as ChatGPT-User and Claude-User, are still refused.
- Added: Perplexity-User, MistralAI-User, Meta-ExternalFetcher and Claude-SearchBot are recognised (186 crawlers).
2.9.0
- Added: per-path crawler rules set in WebDecoy Cloud now apply in WordPress too, by the same rule the edge sensor uses. Cloud rules can only refuse, never allow.
- Changed: crawlers are identified from the shared WebDecoy registry (182, was 54); with Block AI crawlers on, AI agents and assistants are refused along with training crawlers.
2.3.1
- Fixed: Detections forwarded from your site are now identified by the visitor's own request signature. Previously they were identified by your server's outgoing connection, which is the same for every visitor — so every visitor a site reported was grouped into a single "actor" in the dashboard. Only request header names plus Accept-Language and Accept-Encoding are sent; no header values leave your site.
2.3.0
- One-click WebDecoy Cloud connect with automatic key provisioning
- Monthly security report opt-in
- Plan entitlements sync (fails open to free)
- Fixed: Statistics charts growing unbounded with detection data
2.1.0
- JS execution verification to catch non-JS HTTP scrapers
- Challenge token meta tag on page serve; automatic page-serve reporting
2.0.0
- All detection and protection now works locally — no API key required
- Invisible proof-of-work challenge system (SHA-256, no external service)
- Behavioral scoring, statistics page, enhanced detections page
1.3.0
- Bulk IP blocking/unblocking; enhanced good bot detection (60+ bots)
",
"faq": "Does WebDecoy slow down my site?
No. WebDecoy adds negligible latency; tripwire checks are a fast path lookup and clearance minting is idle-deferred.
Will it block search engines?
No. WebDecoy automatically allows 60+ known good bots including all major search engines, and tripwires only fire on hidden paths no legitimate crawler follows.
"
},
"icons": {
diff --git a/changelog.txt b/changelog.txt
index c25d19c..c93aa43 100644
--- a/changelog.txt
+++ b/changelog.txt
@@ -1,5 +1,13 @@
*** WebDecoy Bot Detection Changelog ***
+= 2.13.1 - 2026-11-16 =
+* Added: 10 more crawlers and tools are recognised (245 in total), including TalarionSearchBot, UnfragileBot, Aranet-SearchBot, CrolBot, SperidLabsResearchCrawler, AbliterantBot, TokenFoundryBot, TernCrawler and the ARTEX penetration-testing probe. With automatic robots.txt on, the new crawlers in your chosen categories are added to it.
+* Fixed: block pages and challenge responses now tell page caches not to store them, and the clearance cookie is sent with SameSite=Lax.
+* Changed: dashboard and Statistics figures can be up to a minute old. Protection decisions still use live counts.
+* Changed: on WordPress VIP, calls to WebDecoy use VIP's request helpers, and changing automatic robots.txt categories clears VIP's cached robots.txt.
+* Changed: WebDecoy writes to the PHP error log only when WP_DEBUG is on, and then only a short event code.
+* Fixed: spacing of the AI assistant visits section in the dashboard widget.
+
= 2.13.0 - 2026-11-16 =
* New: see which AI assistants send you visitors. Page visits from a link in ChatGPT, Perplexity, Claude, Gemini, Copilot and other AI products are counted by AI product and landing page, on the dashboard (7 days) and the Statistics page (30 days), with no account. Only counts are kept, nothing about the visitor.
* New: automatic robots.txt. Under Settings > Good Bots, choose categories of bots to keep out (AI training crawlers, SEO tools, scrapers and more) and WebDecoy adds a rule for every known crawler in them to the robots.txt WordPress serves. The list updates with each plugin release. Off until you choose categories.
diff --git a/readme.txt b/readme.txt
index 4706e9f..c88999c 100644
--- a/readme.txt
+++ b/readme.txt
@@ -4,7 +4,7 @@ Donate link: https://webdecoy.com
Tags: ai crawlers, robots.txt, bot analytics, geo, bot detection
Requires at least: 6.1
Tested up to: 7.1
-Stable tag: 2.13.0
+Stable tag: 2.13.1
Requires PHP: 7.4
License: GPLv2 or later
License URI: https://www.gnu.org/licenses/gpl-2.0.html
@@ -332,6 +332,14 @@ The bundled good-bot list (sdk/src/GoodBotList.php) stores a documentation URL f
== Changelog ==
+= 2.13.1 =
+* Added: 10 more crawlers and tools are recognised (245 in total), including TalarionSearchBot, UnfragileBot, Aranet-SearchBot, CrolBot, SperidLabsResearchCrawler, AbliterantBot, TokenFoundryBot, TernCrawler and the ARTEX penetration-testing probe. With automatic robots.txt on, the new crawlers in your chosen categories are added to it.
+* Fixed: block pages and challenge responses now tell page caches not to store them, and the clearance cookie is sent with SameSite=Lax.
+* Changed: dashboard and Statistics figures can be up to a minute old. Protection decisions still use live counts.
+* Changed: on WordPress VIP, calls to WebDecoy use VIP's request helpers, and changing automatic robots.txt categories clears VIP's cached robots.txt.
+* Changed: WebDecoy writes to the PHP error log only when WP_DEBUG is on, and then only a short event code.
+* Fixed: spacing of the AI assistant visits section in the dashboard widget.
+
= 2.13.0 =
* New: see which AI assistants send you visitors. Page visits from a link in ChatGPT, Perplexity, Claude, Gemini, Copilot and other AI products are counted by AI product and landing page, on the dashboard (7 days) and the Statistics page (30 days), with no account. Only counts are kept, nothing about the visitor.
* New: automatic robots.txt. Under Settings > Good Bots, choose categories of bots to keep out (AI training crawlers, SEO tools, scrapers and more) and WebDecoy adds a rule for every known crawler in them to the robots.txt WordPress serves. The list updates with each plugin release. Off until you choose categories.
diff --git a/sdk/src/registry/agents.generated.php b/sdk/src/registry/agents.generated.php
index b65fc83..ae71625 100644
--- a/sdk/src/registry/agents.generated.php
+++ b/sdk/src/registry/agents.generated.php
@@ -14,9 +14,48 @@
return [
'schema' => 2,
- 'agent_count' => 235,
+ 'agent_count' => 245,
'categories' => ['training_crawler', 'ai_search_crawler', 'ai_agent', 'ai_assistant', 'search_crawler', 'seo_crawler', 'security_scanner', 'generic_scraper', 'archiver', 'fetcher', 'monitoring', 'headless_browser', 'feed_reader', 'commercial_scraper', 'none'],
'agents' => [
+ [
+ 'id' => 'speridlabsresearchcrawler',
+ 'name' => 'SperidLabsResearchCrawler',
+ 'category' => 'training_crawler',
+ 'behavior' => 'training',
+ 'organization' => 'Speridlabs',
+ 'patterns' => ['speridlabsresearchcrawler'],
+ 'robots_name' => 'SperidLabsResearchCrawler',
+ 'website' => 'https://speridlabs.com',
+ 'base_score' => 75,
+ 'respects_robots' => false,
+ 'http_client' => false,
+ ],
+ [
+ 'id' => 'abliterantbot',
+ 'name' => 'AbliterantBot',
+ 'category' => 'training_crawler',
+ 'behavior' => 'training',
+ 'organization' => 'Abliterant',
+ 'patterns' => ['abliterantbot'],
+ 'robots_name' => 'AbliterantBot',
+ 'website' => 'https://abliterant.ai',
+ 'base_score' => 75,
+ 'respects_robots' => false,
+ 'http_client' => false,
+ ],
+ [
+ 'id' => 'tokenfoundrybot',
+ 'name' => 'TokenFoundryBot',
+ 'category' => 'training_crawler',
+ 'behavior' => 'training',
+ 'organization' => 'Unknown',
+ 'patterns' => ['tokenfoundrybot'],
+ 'robots_name' => 'TokenFoundryBot',
+ 'website' => '',
+ 'base_score' => 75,
+ 'respects_robots' => false,
+ 'http_client' => false,
+ ],
[
'id' => 'reflectionbot',
'name' => 'Reflectionbot',
@@ -433,6 +472,45 @@
'respects_robots' => false,
'http_client' => false,
],
+ [
+ 'id' => 'talarionsearchbot',
+ 'name' => 'TalarionSearchBot',
+ 'category' => 'ai_search_crawler',
+ 'behavior' => 'search',
+ 'organization' => 'Talarion',
+ 'patterns' => ['talarionsearchbot'],
+ 'robots_name' => 'TalarionSearchBot',
+ 'website' => 'https://talarion.tech',
+ 'base_score' => 65,
+ 'respects_robots' => false,
+ 'http_client' => false,
+ ],
+ [
+ 'id' => 'unfragilebot',
+ 'name' => 'UnfragileBot',
+ 'category' => 'ai_search_crawler',
+ 'behavior' => 'search',
+ 'organization' => 'Unfragile',
+ 'patterns' => ['unfragilebot'],
+ 'robots_name' => 'UnfragileBot',
+ 'website' => 'https://unfragile.ai/bot',
+ 'base_score' => 65,
+ 'respects_robots' => true,
+ 'http_client' => false,
+ ],
+ [
+ 'id' => 'aranet-searchbot',
+ 'name' => 'Aranet-SearchBot',
+ 'category' => 'ai_search_crawler',
+ 'behavior' => 'search',
+ 'organization' => 'Aranet',
+ 'patterns' => ['aranet-searchbot'],
+ 'robots_name' => 'Aranet-SearchBot',
+ 'website' => 'https://aranet.ai/bot',
+ 'base_score' => 65,
+ 'respects_robots' => false,
+ 'http_client' => false,
+ ],
[
'id' => 'duckassistbot',
'name' => 'DuckAssistBot',
@@ -1122,6 +1200,19 @@
'respects_robots' => true,
'http_client' => false,
],
+ [
+ 'id' => 'crolbot',
+ 'name' => 'CrolBot',
+ 'category' => 'seo_crawler',
+ 'behavior' => 'seo',
+ 'organization' => 'cloro',
+ 'patterns' => ['crolbot'],
+ 'robots_name' => 'CrolBot',
+ 'website' => 'https://cloro.dev',
+ 'base_score' => 50,
+ 'respects_robots' => false,
+ 'http_client' => false,
+ ],
[
'id' => 'ahrefsbot',
'name' => 'AhrefsBot',
@@ -1434,6 +1525,19 @@
'respects_robots' => true,
'http_client' => false,
],
+ [
+ 'id' => 'artex',
+ 'name' => 'ARTEX',
+ 'category' => 'security_scanner',
+ 'behavior' => 'security_testing',
+ 'organization' => 'Open Source',
+ 'patterns' => ['artex-enrich/'],
+ 'robots_name' => '',
+ 'website' => 'https://github.com/BaaRai/ARTEX',
+ 'base_score' => 90,
+ 'respects_robots' => false,
+ 'http_client' => true,
+ ],
[
'id' => 'nessus',
'name' => 'Nessus',
@@ -1655,6 +1759,19 @@
'respects_robots' => false,
'http_client' => false,
],
+ [
+ 'id' => 'norma',
+ 'name' => 'Norma WebFetch',
+ 'category' => 'generic_scraper',
+ 'behavior' => '',
+ 'organization' => 'Open Source',
+ 'patterns' => ['norma/'],
+ 'robots_name' => '',
+ 'website' => 'https://github.com/Autumn-27/norma',
+ 'base_score' => 70,
+ 'respects_robots' => false,
+ 'http_client' => true,
+ ],
[
'id' => 'python-requests',
'name' => 'Python-Requests',
@@ -2721,6 +2838,19 @@
'respects_robots' => true,
'http_client' => false,
],
+ [
+ 'id' => 'terncrawler',
+ 'name' => 'TernCrawler',
+ 'category' => 'commercial_scraper',
+ 'behavior' => '',
+ 'organization' => 'Unknown',
+ 'patterns' => ['terncrawler'],
+ 'robots_name' => 'TernCrawler',
+ 'website' => '',
+ 'base_score' => 60,
+ 'respects_robots' => false,
+ 'http_client' => false,
+ ],
[
'id' => 'diffbot',
'name' => 'Diffbot',
diff --git a/sdk/src/registry/parity-vectors.generated.json b/sdk/src/registry/parity-vectors.generated.json
index 8e68595..e7edbbc 100644
--- a/sdk/src/registry/parity-vectors.generated.json
+++ b/sdk/src/registry/parity-vectors.generated.json
@@ -11,6 +11,30 @@
"category": "training_crawler",
"matched": true
},
+ {
+ "userAgent": "artex-enrich/",
+ "id": "artex",
+ "category": "security_scanner",
+ "matched": true
+ },
+ {
+ "userAgent": "Mozilla/5.0 (compatible; artex-enrich//1.0; +http://example.com/bot)",
+ "id": "artex",
+ "category": "security_scanner",
+ "matched": true
+ },
+ {
+ "userAgent": "abliterantbot",
+ "id": "abliterantbot",
+ "category": "training_crawler",
+ "matched": true
+ },
+ {
+ "userAgent": "Mozilla/5.0 (compatible; abliterantbot/1.0; +http://example.com/bot)",
+ "id": "abliterantbot",
+ "category": "training_crawler",
+ "matched": true
+ },
{
"userAgent": "acunetix",
"id": "acunetix",
@@ -155,6 +179,18 @@
"category": "training_crawler",
"matched": true
},
+ {
+ "userAgent": "aranet-searchbot",
+ "id": "aranet-searchbot",
+ "category": "ai_search_crawler",
+ "matched": true
+ },
+ {
+ "userAgent": "Mozilla/5.0 (compatible; aranet-searchbot/1.0; +http://example.com/bot)",
+ "id": "aranet-searchbot",
+ "category": "ai_search_crawler",
+ "matched": true
+ },
{
"userAgent": "archive.org_bot",
"id": "archive-org-bot",
@@ -635,6 +671,18 @@
"category": "commercial_scraper",
"matched": true
},
+ {
+ "userAgent": "crolbot",
+ "id": "crolbot",
+ "category": "seo_crawler",
+ "matched": true
+ },
+ {
+ "userAgent": "Mozilla/5.0 (compatible; crolbot/1.0; +http://example.com/bot)",
+ "id": "crolbot",
+ "category": "seo_crawler",
+ "matched": true
+ },
{
"userAgent": "dataforseobot",
"id": "dataforseobot",
@@ -1823,6 +1871,18 @@
"category": "monitoring",
"matched": true
},
+ {
+ "userAgent": "norma/",
+ "id": "norma",
+ "category": "generic_scraper",
+ "matched": true
+ },
+ {
+ "userAgent": "Mozilla/5.0 (compatible; norma//1.0; +http://example.com/bot)",
+ "id": "norma",
+ "category": "generic_scraper",
+ "matched": true
+ },
{
"userAgent": "nuclei",
"id": "nuclei",
@@ -2519,6 +2579,18 @@
"category": "search_crawler",
"matched": true
},
+ {
+ "userAgent": "speridlabsresearchcrawler",
+ "id": "speridlabsresearchcrawler",
+ "category": "training_crawler",
+ "matched": true
+ },
+ {
+ "userAgent": "Mozilla/5.0 (compatible; speridlabsresearchcrawler/1.0; +http://example.com/bot)",
+ "id": "speridlabsresearchcrawler",
+ "category": "training_crawler",
+ "matched": true
+ },
{
"userAgent": "splash",
"id": "splash",
@@ -2579,6 +2651,18 @@
"category": "fetcher",
"matched": true
},
+ {
+ "userAgent": "talarionsearchbot",
+ "id": "talarionsearchbot",
+ "category": "ai_search_crawler",
+ "matched": true
+ },
+ {
+ "userAgent": "Mozilla/5.0 (compatible; talarionsearchbot/1.0; +http://example.com/bot)",
+ "id": "talarionsearchbot",
+ "category": "ai_search_crawler",
+ "matched": true
+ },
{
"userAgent": "tavily",
"id": "tavily",
@@ -2603,6 +2687,18 @@
"category": "fetcher",
"matched": true
},
+ {
+ "userAgent": "terncrawler",
+ "id": "terncrawler",
+ "category": "commercial_scraper",
+ "matched": true
+ },
+ {
+ "userAgent": "Mozilla/5.0 (compatible; terncrawler/1.0; +http://example.com/bot)",
+ "id": "terncrawler",
+ "category": "commercial_scraper",
+ "matched": true
+ },
{
"userAgent": "theoldreader",
"id": "theoldreader",
@@ -2627,6 +2723,18 @@
"category": "training_crawler",
"matched": true
},
+ {
+ "userAgent": "tokenfoundrybot",
+ "id": "tokenfoundrybot",
+ "category": "training_crawler",
+ "matched": true
+ },
+ {
+ "userAgent": "Mozilla/5.0 (compatible; tokenfoundrybot/1.0; +http://example.com/bot)",
+ "id": "tokenfoundrybot",
+ "category": "training_crawler",
+ "matched": true
+ },
{
"userAgent": "tumblr",
"id": "tumblr",
@@ -2663,6 +2771,18 @@
"category": "generic_scraper",
"matched": true
},
+ {
+ "userAgent": "unfragilebot",
+ "id": "unfragilebot",
+ "category": "ai_search_crawler",
+ "matched": true
+ },
+ {
+ "userAgent": "Mozilla/5.0 (compatible; unfragilebot/1.0; +http://example.com/bot)",
+ "id": "unfragilebot",
+ "category": "ai_search_crawler",
+ "matched": true
+ },
{
"userAgent": "uptimerobot",
"id": "uptimerobot",
diff --git a/webdecoy.php b/webdecoy.php
index 805237c..b22c7ef 100644
--- a/webdecoy.php
+++ b/webdecoy.php
@@ -3,7 +3,7 @@
* Plugin Name: WebDecoy - AI Traffic Analytics & Bot Protection
* Plugin URI: https://webdecoy.com/wordpress
* Description: Understand AI crawler visits and bot identity evidence in WordPress, with local analytics and protection against spam, login abuse, and WooCommerce card testing.
- * Version: 2.13.0
+ * Version: 2.13.1
* Requires at least: 6.1
* Requires PHP: 7.4
* Author: WebDecoy
@@ -41,7 +41,7 @@ function str_starts_with(string $haystack, string $needle): bool
}
// Plugin constants
-define('WEBDECOY_VERSION', '2.13.0');
+define('WEBDECOY_VERSION', '2.13.1');
define('WEBDECOY_PLUGIN_FILE', __FILE__);
define('WEBDECOY_PLUGIN_DIR', plugin_dir_path(__FILE__));
define('WEBDECOY_PLUGIN_URL', plugin_dir_url(__FILE__));