Web shell probing
—
They try addresses like /alfa.php or /1.php, hoping a backdoor from someone else's break-in is still on the server. If they find one, they take control of the server.
What to do on your side: Keep unneeded executable files out of the public folder; forbid running scripts in upload folders.
Leak hunting
—
They look for forgotten copies of configs (wp-config.php.bak), .env files and .git folders, which hold database passwords and API keys.
What to do on your side: Do not keep backups and .env in the public folder; keep secrets in a vault; scan repositories for secrets.
WordPress attacks
—
Vulnerable plugins, file managers, admin panels. We have no WordPress; scanners hit all sites in a row without checking.
What to do on your side: Update the CMS and plugins, remove unused ones, close the admin panel from the internet.
Exploits
—
Requests with signatures of known vulnerabilities. Managed WAF rules blocked them.
What to do on your side: Install CVE updates, keep a WAF in front of the application, scan the site with DAST regularly.
AI crawlers
—
AI companies collect texts to train models and generate answers. This is not a break-in, but it is traffic nobody asked for.
What to do on your side: Decide whom to let in: AI search bots are usually fine, dataset collectors are optional.
Not a vulnerability but traffic: handled by WAF and bot management
Suspicious bots
—
Automated clients that look like bots. Cloudflare sent them to a "are you human?" check.
What to do on your side: Turn on bot protection and request rate limiting.
Not a vulnerability but traffic: handled by WAF and bot management