Crazy amount of guests

Thanks. I'm curious then - how do they solve a Cloudflare interactive challenge if they don't metaphorically "click" the button to say they are human? Presumably code to make it look clicked?

Anyway they are stopped again for now. The ones pretending to be multiple browsers and mobiles and faking referers can't solve cloudflare challenges, so they're being stopped by a challenge rule now. The rest that can solve cloudflare challenges are trapped in the honeypot. No doubt they will try something else.

I believe the bots running real browsers with playwright or puppeteer can click things, using javascript, which I assume is how they solve an interactive, tick box, cloudflare challenge.
There are clients that exist to mimic legitimate clients. Check out various topics with tagged repos on Github that exist for this very purpose:


Many, if not nearly all of the listed repos, are using Chromium in some form or fashion to do their dealings. Think of 'clicking' in this terminology as a phantom-click. The bots aren't actually clicking, they're deciphering the payload to solve, solves it, sends it back to CF for validation.

In the world of HTTP, it's either a GET or a POST - there isn't much else. Yes, yes, I know, OPTIONS and HEAD also exists, but that's aside this subject matter. :)
 
There are clients that exist to mimic legitimate clients. Check out various topics with tagged repos on Github that exist for this very purpose:


Many, if not nearly all of the listed repos, are using Chromium in some form or fashion to do their dealings. Think of 'clicking' in this terminology as a phantom-click. The bots aren't actually clicking, they're deciphering the payload to solve, solves it, sends it back to CF for validation.

In the world of HTTP, it's either a GET or a POST - there isn't much else. Yes, yes, I know, OPTIONS and HEAD also exists, but that's aside this subject matter. :)
Thank you for explaining that :-) Can't believe cloudflare solver solutions are actually out there publicly (those links)!
 
In case this is useful to anyone else. Just blocked ASN 211590 - Bucklog SARL (France) scanner. One of it's IP's was the highest number of requests in the past day. It was probing for .git and .github files. Presumably didn't get anything on a Xenforo site? But it has a bad reputation after googling. The IP was 185.177.72.49. ASN as above.
 
"The standout deserves its own paragraph

BUCKLOG isn't just a number on our chart — GreyNoise did the deep forensic work on it and we're standing on their shoulders here. Their researchers documented AS211590 as a purpose-built, Kubernetes-orchestrated scanning fleet operating out of a single Paris range, generating on the order of 13 million sessions across 90 days, and in one tracked week throwing more than 33,000 HTTP requests at webhook endpoints — hunting file-upload paths, document-processing endpoints, and n8n workflow-automation instances via CVE-2026-21858. That is not a hosting company that happens to have a few bad tenants. The abuse is the product. The entire ASN is the weapon."


Edit - It's been mentioned in this thread before on page 10 - apparently going direct to server IP in this case?

 
Back
Top Bottom