What reaches my own server?
Last 30 days: from 01.10.2026 until today, 8:00, updated hourly. Applies to all figures and charts on this page. I do not keep the data longer than 90 days.
Around 22.000 attack attempts in 30 days. On a single small server.
This is the server this website runs on. I counted requests my firewall blocked and requests for files that don't exist here. Almost all of it comes from programs that comb the entire internet around the clock. Nobody picked secureIT. Every business with a website, router or mail server gets hit exactly the same way, however small.
750
attempts per day on average1.050
different senders106
countriesunder 0,1 %
from known research scannersPeriod: last 30 days, from 01.10.2026 to 30.10.2026, 8:00, as selected above.
PHP2Shell: what of it reaches my server
PHP2Shell (CVE-2026-109618 and CVE-2026-109619) is a critical flaw in PHP, the programming language behind roughly three quarters of all websites, WordPress and many online shops included. Known since 21 October 2026, exploited even earlier. The attacker sends a crafted file upload. PHP takes it apart before the actual website runs, and in the process someone else's code can get onto the server. These four figures show what of it reaches me, from the clearest sign to the background noise.
8
Uploads to addresses without an upload function
The clearest sign of PHP2Shell. A normal visitor never sends a file to these addresses because the page there accepts none. But PHP processes an upload at any address before the actual page even runs. That processing is exactly where the flaw lies.
2
Manipulated uploads
Uploads with a deliberately distorted structure, for example broken or missing separators between the files. The firewall blocks them. PHP2Shell needs exactly such distorted uploads to throw PHP off balance while it takes them apart.
15
Malicious PHP code and system commands
Requests containing PHP code or commands for the server. If an attack like PHP2Shell succeeds, this is exactly the code meant to run afterwards.
about 21.000
Searching for PHP files
Not PHP2Shell but the background noise: bots request PHP files that don't exist here, mostly backdoors and WordPress logins. Some of them look for exactly the backdoors left behind on a server after a successful break-in such as PHP2Shell.
Whether a single hit really was PHP2Shell cannot be proven from the outside. My server is patched.
Do you run PHP on your own servers? The critical PHP2Shell flaw from October 2026 is fixed from PHP 8.2.35, 8.3.36, 8.4.27 and 8.5.12. Older versions are vulnerable.
Period: last 30 days, from 01.10.2026 to 30.10.2026, 8:00, as selected above. I have only been counting uploads since 29.10.2026; before that, only the firewall's hits appear there.
What was attempted
- Hunting for backdoors about 14.300
Requests for files with typical web shell names. Bots hope to stumble on a backdoor that another attacker left on the server earlier.
- WordPress attacks about 5.800
Login attempts with guessed passwords and searches for vulnerable plugins. My server doesn't even run WordPress, but the bots try anyway.
- Hunting for credentials about 1.300
Attempts to fetch configuration files with passwords and keys that are left exposed on poorly set-up websites.
- Probing the server about 300
Requests for test and status pages to learn software versions and pick matching flaws.
- Flaws in other software about 130
Known flaws in programs, routers and firewalls I don't even use. Scanners try them blindly on every address on the internet.
- Suspicious bot requests about 110
Requests that break the rules of the web or carry the typical traits of simple scanning scripts.
- Admin tools about 60
Searches for openly reachable database and file managers.
- Injecting code about 40
Requests carrying malicious code: SQL commands against the database, shell commands, scripts or manipulated uploads meant to make the server run someone else's code.
- Other about 40
Other blocked or dead-end requests without a clear pattern.
Period: last 30 days, from 01.10.2026 to 30.10.2026, 8:00, as selected above.
Every day, every hour
01.10.30.10.2026
Period: last 30 days, from 01.10.2026 to 30.10.2026, 8:00, as selected above. One bar per day; today's is not complete yet.
0 h12 h23 h
Period: last 30 days, from 01.10.2026 to 30.10.2026, 8:00, as selected above. Per hour of the day in German time, added up over all days.
There is no quiet hour: these programs know neither evenings off nor weekends.
Where the sending computers are located
Period: last 30 days, from 01.10.2026 to 30.10.2026, 8:00, as selected above.
- South Koreaabout 5.900
- Australiaabout 5.100
- Indiaabout 3.400
- Japanabout 2.000
- Hong Kongabout 1.400
- Singaporeabout 750
- Germanyabout 650
- Belgiumabout 650
The country shows where the computer is, not where the person behind it sits. Attackers rent machines in other people's data centres or use hijacked routers and PCs. So be careful with conclusions like “the attacks come from country X”.
Source: my own analysis of the secureit.icu server logs. Large figures rounded. I deliberately do not publish individual addresses, requests or firewall settings. Countries: IP Geolocation by DB-IP (CC BY 4.0).