How are you blocking AI scrapers that use regular member accounts?

LogicWhisper

Member
Licensed customer
We recently had someone use an AI browser to scrape our forum and copy the content to another website, including posts word for word.

I tested this myself using Tab AI. It logged in with a regular member account and opened 10 different threads in 8 seconds. Every page loaded normally, with no CAPTCHA, rate limit or slowdown.

Most of the solutions I've seen involve Cloudflare or blocking known bots, but what happens when the AI is using a real browser and a legitimate account?

We're running XenForo 2.3 Cloud.

Has anyone found something that actually blocks this kind of scraping?

I'm not looking to just detect or log it. I want to prevent an account from systematically downloading the entire forum.

Curious what other forum owners are doing about this.
 
If it's automated, Login Spaminator should stop the login.

 
Thanks. I think I should explain a little better what I'm looking for.

The problem isn't really automated logins. AI agents like Tab can use a normal browser, log in with a regular member account, and browse the forum just like a person.

What I'm looking for is something that monitors how quickly an account is accessing threads.

For example, if an account opens 10 different threads in 8 seconds, or hundreds of threads within a few minutes, it should automatically block or temporarily restrict access.

Ideally, this should work even for logged-in members and stop the requests before the thread content is delivered.

Is anyone using something like this on XenForo?
 
AI agents like Tab can use a normal browser, log in with a regular member account, and browse the forum just like a person.
If it's using automation to perform the login, Spaminator will block it. AND log it, so you can ban or delete the account.
 
Last edited:
Has anyone found something that actually blocks this kind of scraping?

I'm not looking to just detect or log it. I want to prevent an account from systematically downloading the entire forum.

What I'm looking for is something that monitors how quickly an account is accessing threads.

For example, if an account opens 10 different threads in 8 seconds, or hundreds of threads within a few minutes, it should automatically block or temporarily restrict access.

Ideally, this should work even for logged-in members and stop the requests before the thread content is delivered.

Is anyone using something like this on XenForo?
What you are looking for is a rate limiter. IP Thread Monitor has one built in, initially this was the main purpose of the add on. It should work for logged in members, too, with the right configuration and will be able to block the account in case of hitting the barrier.
 
What you are looking for is a rate limiter. IP Thread Monitor has one built in, initially this was the main purpose of the add on. It should work for logged in members, too, with the right configuration and will be able to block the account in case of hitting the barrier.
Thanks, this looks much closer to what I'm looking for.

I noticed the add-on says registered members are exempt from rate limiting when Protect Members is enabled.

Are you saying I can disable that exemption and have it actually block someone who's already logged in and opening threads too quickly?

Also, does it limit by IP only, or can it limit by XenForo user account? And have you tried it on XenForo Cloud?

I'd like to confirm before buying it.
 
I noticed the add-on says registered members are exempt from rate limiting when Protect Members is enabled.

Are you saying I can disable that exemption and have it actually block someone who's already logged in and opening threads too quickly?
Yes, that's why it says "when Protected Members is enabled". When this setting is disabled the ruleset inc. rate limiter will also be applied to logged in members. I did however never do that due to no need and as some settings within IP Threat Manager are crossdependent from other settings due to the historical development of the add on it may be the case that when you use rate limiter on members some other features of the add on should rather be not used to not annoy genuine members or block them accidentially. In general it is a very good add on from a very responsive developer. I would not hesitate to give it a try.
 
I let Claude Code analyse my server logs and CloudFlare logs. It takes notice of speed, behavior from page to page and many other technical specifications. It does identify specific scrapers and configures CF WAF rules to block the specifics of the scraper. Most likely server logs are not needed and cloudflare logs will suffice. Adding digitalpoints CloudFlare integration is helpful.
 
You might be after @Xon's Sign up and abuse add on.
But please make sure that if you're getting registered users with no captcha that's on you.
Use something like the Question/Answer or the cloudflare turnstile captcha.
Also make sure that guests cannot post.
 
Thanks everyone for the suggestions!

Regarding the login and signup protection, I understand how that could help stop automated accounts. But the bigger concern is someone using a normal browser with an existing account, or even browsing as a guest, and copying hundreds of threads.

Someone can simply give an AI assistant their login details and tell it to go through the forum and copy everything. No need for automated signups or spam accounts.
Yes, that's why it says "when Protected Members is enabled". When this setting is disabled the ruleset inc. rate limiter will also be applied to logged in members. I did however never do that due to no need and as some settings within IP Threat Manager are crossdependent from other settings due to the historical development of the add on it may be the case that when you use rate limiter on members some other features of the add on should rather be not used to not annoy genuine members or block them accidentially. In general it is a very good add on from a very responsive developer. I would not hesitate to give it a try.

Thanks, that makes sense. This might actually be what I'm looking for.

My only concern is accidentally blocking regular members. I'd have to figure out a reasonable limit that would catch someone scraping hundreds of threads without bothering people just browsing normally.



I let Claude Code analyse my server logs and CloudFlare logs. It takes notice of speed, behavior from page to page and many other technical specifications. It does identify specific scrapers and configures CF WAF rules to block the specifics of the scraper. Most likely server logs are not needed and cloudflare logs will suffice. Adding digitalpoints CloudFlare integration is helpful.

That's an interesting approach. Unfortunately, I'm on XenForo Cloud using their community.forum domain, so I don't have direct access to the Cloudflare settings or server logs.


Access Log could definitely be useful for investigating activity, but I'm mainly trying to prevent the scraping rather than find out about it afterward.
For members

Page View Limit actually sounds pretty close to what I'm looking for. I noticed it exempts members with secondary user groups, though. Is there a way around that? We use quite a few secondary groups.

So far, IP Threat Monitor and Page View Limit seem like the most relevant options.

Has anyone actually used either of them to limit excessive thread views without causing problems for regular members?
 
Just to explain why I'm so concerned about this.

Someone actually used an AI tool to copy pretty much our entire forum onto another website. Not just a few threads, but posts copied word for word, with the new site looking almost identical to ours.

The scary part is that members sometimes post things by mistake or later decide to delete something. But even if we remove it from our forum, it's already sitting on another website that we have no control over. Some members are already hesitant to post because of this.

And it's surprisingly easy to do. Someone can give an AI assistant like Tab or Instinct access to a regular account and tell it to copy the forum. I tested Tab myself, and it opened 10 threads in just 8 seconds without any restrictions.

I know we can't completely stop people from copying what they can see, but there should be a way to prevent someone from automatically going through thousands of threads and copying the entire forum in a short time.

That's what I'm trying to prevent, without making things difficult for regular members.
 
Someone actually used an AI tool to copy pretty much our entire forum onto another website. Not just a few threads, but posts copied word for word, with the new site looking almost identical to ours.
In such a case I would do three things:

1. Contact the hoster of this other website to get the site removed due to copyright infriction and content theft.
2. Find out which of your members copied the content and throw them out
3. Implement techical measures to discover early when this happened again
(4. add a paragraph in the TOS that explicitely states an excessive sum that s/o who does that will have to pay to you)
 
OMG many replies here with users don't get what it is you are up against.

Check outthis https://xenforo.com/community/resources/xf-bot-guard.10508/
It works, and hopefully the developer will release a much better more advnaced version soon as he promised a few months ago
:)

This together with advanced cloudflare logs and filtering can stop this at least for now. We have been fighting with it for a 6 months or more.. contacting hosts can be a solution if it is not hosted somewhere where they could care less about disputes DMCA etc.
 
OMG many replies here with users don't get what it is you are up against.
True, but it seems that you don't get it either.
How would Bot Guard work against the scenario, that a member of your forum does mass-download content using a genuine Browser? Bot Guard does not have a rate limiter and "all" it does is to check wether a browser is a "normal" browser (which it seems to be in the case described). If it has doubts it fires out a captcha that can then be solved either manually or automatically and after that you do have a trust window of xx minutes/hours where the downloader can act freely. Furthermore, in a typical configuration, one would let BotGuard act on guests only and not on logged in members.

So how would Bot Guard stop the scenario described by the OP?
 
Use a DNS firewall, such as Cloudflare. Logged in, logged out, doesn't matter, you can catch the majority of bots with an accurate header rule.

AI replication, does not replicate your site. It attempts to replicate the public facing pages. It cannot walk your server side folders or database. It can though create static HTML pages from what you have publicly facing.

A client was having trouble with their dev, so I showed them how easily they can recreate their website with AI.

Original: https://www.spaceworks.com.au/
AI 1hr: https://spaceworks.anthonyparsons.workers.dev/

This was a couple months back, so I think they made some changes since then, but it got it about 98% right and just needed a few tweaks. They were shocked, to say the least, yet relieved, because the dev was withholding their website from them and this changed the negotiation very quickly.

Again, that is only a static replication, which is enough in this case as there is no user interaction with the site.

How do you defend against that? A simple block on Claude would have stopped it, along with any other AI bot running around the web. Just a switch at cloudflare.
 
Use a DNS firewall, such as Cloudflare.
Jesus, I know that you love Cloudflare, but you have started it recommending it for absolutely everything, no matter if it is a fit or not. The name "DNS firewall" seems to be nothing but buzzword bingo that was invented by some companies that want to sell their solutions. Basically it seems to mean that the hostnames of requesting hosts are checked against a blacklist before a connection is established.
As we do not know how what the OP describes is done technically

We recently had someone use an AI browser to scrape our forum and copy the content to another website, including posts word for word.

(i.e. via his home internet connection with dynamic IP and a dynamic hostname vs. i.e. a dedictated static host in a data center) your "solution" has absolutely no foundation currently. How would you block a dynamic IP and hostname with a DNS firewall w/o massive colateral damage to genuine users?

AI replication, does not replicate your site. It attempts to replicate the public facing pages.
I cannot see where the OP would have claimed his forum would be cloned. He was talking about content theft. This problem is decades old and was in earlier years i.e. done by misusing RSS feeds that were not limited to a shortend excerpt as well as by other means.
Logged in, logged out, doesn't matter, you can catch the majority of bots with an accurate header rule.
Once more your love to Cloudflare lets you ignore the problem that the OP has lined out as it seems. He was not talking about masses of bots but about a single member of his forum that would copy forum content at speed to another website, using a genuine browser.

Obviously, a proper solution depends from looking at the issue more closely to identify the relevant, unique patterns. Until now the main distinguishing pattern seems to bee speed and amount of requests. A "DNS firewall" has absolutely no card in this game. What you would need is a rate limiting mechanism. At best, you would somehow connect the rate limiter to your user database to identify which account is used for scraping. IP Threat Monitor will deliver this out of the box with an adeqate configuration targetet at this problem. CF can't.
How do you defend against that? A simple block on Claude would have stopped it, along with any other AI bot running around the web. Just a switch at cloudflare.
You are really missing the target by miles as you seem to be in deep love with your solution and adverdize it for anything, no matter if it has even the slightest connection to the problem that s/o wants to solve.
 
In such a case I would do three things:

1. Contact the hoster of this other website to get the site removed due to copyright infriction and content theft.
2. Find out which of your members copied the content and throw them out
3. Implement techical measures to discover early when this happened again
(4. add a paragraph in the TOS that explicitely states an excessive sum that s/o who does that will have to pay to you)
I agree, and we're already working on some of this.

The problem is that most of these solutions are after the fact. We might get one copied site removed, but how do we know there aren't others?

As for banning the account, users create a separate account for the AI to use. By the time we catch it, the content is already copied.
That's why I'm trying to prevent the mass scraping in the first place, rather than deal with the damage afterward.

(Again, I can't protect screenshots, or someone Ctrl+C a whole page and ctrl V, but the option of copying a whole site, with a single message to a WhatsApp bot, is something new)

OMG many replies here with users don't get what it is you are up against.

Check outthis https://xenforo.com/community/resources/xf-bot-guard.10508/
It works, and hopefully the developer will release a much better more advnaced version soon as he promised a few months ago
:)

This together with advanced cloudflare logs and filtering can stop this at least for now. We have been fighting with it for a 6 months or more.. contacting hosts can be a solution if it is not hosted somewhere where they could care less about disputes DMCA etc.
Thanks! I'm actually already using XF Bot Guard.

I tested it with Tab AI using a regular logged-in account. It opened 10 threads in 8 seconds. Bot Guard recorded all the requests, but they scored only 30, below the challenge threshold of 50.

It was in observe-only mode, but based on those scores, it wouldn't have challenged the requests anyway.
As @smallwheels pointed out, the issue is that these AI agents use real browsers, pass the checks, and can keep browsing with an existing session.

And unfortunately, I'm on XenForo Cloud using their community.forum domain, so I don't have control over the Cloudflare settings.


Use a DNS firewall, such as Cloudflare. Logged in, logged out, doesn't matter, you can catch the majority of bots with an accurate header rule.

AI replication, does not replicate your site. It attempts to replicate the public facing pages. It cannot walk your server side folders or database. It can though create static HTML pages from what you have publicly facing.

A client was having trouble with their dev, so I showed them how easily they can recreate their website with AI.

Original: https://www.spaceworks.com.au/
AI 1hr: https://spaceworks.anthonyparsons.workers.dev/

This was a couple months back, so I think they made some changes since then, but it got it about 98% right and just needed a few tweaks. They were shocked, to say the least, yet relieved, because the dev was withholding their website from them and this changed the negotiation very quickly.

Again, that is only a static replication, which is enough in this case as there is no user interaction with the site.

How do you defend against that? A simple block on Claude would have stopped it, along with any other AI bot running around the web. Just a switch at cloudflare.
I understand it doesn't actually copy the database or server files, but that's not really what concerns me.

In our case, the actual threads and posts were copied word for word onto another site. It doesn't need database access for that, just access to the pages like any regular visitor.

Blocking known AI crawlers makes sense, but would that really stop someone using Tab or another AI agent through a normal Chrome browser, logged in with a regular account?

That's the part I'm struggling to find a solution for. And since I'm on XenForo Cloud with their domain, I can't configure Cloudflare rules myself.
 
Back
Top Bottom