Pricing Insights
Book a demo
CVE radar · Our perimeter

Attacks on traio.kz.

A live log of what hits our site. There are no login forms or personal data here, yet there are hundreds of attacks a day. Any site is scanned this way, yours too. Data from Cloudflare WAF, updated every hour; we show only aggregated figures.

Period
30 days
Synced
—
Flow
LIVE
Attacks in 30 days
—
Per day · last 7 days
—
From clouds
—Azure, Google Cloud, AWS and others: attacks come from rented servers
No User-Agent
—they do not even introduce themselves: these are scripts, not people
Trend

By day

day, Almaty time
Web shell probingLeak huntingWordPress attacksExploitsAI crawlersSuspicious bots

What they tried

Six types of attacks

30 days

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
What they look for

Most frequent addresses

mass attack requests only · 30 days

Almost none of these files are ours: attackers check whether someone left a backdoor, a config copy or a vulnerable plugin on the server. Many names are known web shells and traces of mass WordPress compromises.

The list is the same for thousands of sites. If you have even one such file, it will be found within hours.

Who comes

Scripts, scanners and AI

by User-Agent · 30 days
What they came with
AI crawlers that were blocked
From where

Clouds and countries

network and country of the source server · 30 days
Network
Country

The country is where the server is located, not where the attacker sits: a cloud server can be rented in any country within minutes.

When

By hour of the day

Almaty time · 30 days
00:0006:0012:0018:0023:00

Feed

Latest break-in attempts

without AI crawlers and bots
TimeWhatAddressFrom where
Your site · AppSec technologies

What covers each attack

three lines of defense: code → test environment → production

In this period the WAF blocked thousand requests, and did not fix a single vulnerability. It recognizes known patterns: a request that is not in the rules will pass. If there is a hole in the code, one such request is enough for an attacker. The cause is removed earlier: in code, dependencies and configuration.

In code · before releaseremoves the causeIn test environmentfinds the hole before attackers doIn productionblocks the request, the hole remains
AttackSASTSCASecretsIaC and containersDASTWAF
Web shells File upload without validation and RCE in code: the way a shell gets onto a serverPlugins and libraries with RCE—Ban on running scripts in the upload folder, read-only file systemChecks whether your own file can be uploaded and runBlocks requests to known shell names
Config leaks Passwords and keys hardcoded in code—Keys and passwords in the repository and commit history, before they reach the serverThe web server does not serve .env, .git and backupsRequests /.env, /.git, *.bak on its own, like an attackerBlocks requests to service files
WordPress and plugins Vulnerabilities in your own plugins and themesCMS, plugins and libraries with known CVEs—Admin panel closed from the internetChecks the CMS for known vulnerabilitiesVirtual patch while no update is available
Exploits of known vulnerabilities Injections and RCE in your codeLibraries with CVEs: what is exploited en masse—Vulnerable images and extra open servicesChecks the running application against OWASP Top 10Cuts off requests with exploit signatures

AI crawlers and suspicious bots are not a vulnerability but traffic: WAF, bot management and robots.txt handle them.

The code line of defense, in one platformTRAIO: SAST, SCA and secret detection. One shared list of vulnerabilities, works inside your perimeter.
How it works →