News

PHP vulnerability attacks: 190,000 alerts in 24 hours

contacts/grega-kabi-2023 Grega T.,
7 min read
PHP vulnerability attacks: 190,000 alerts in 24 hours

In late October we described how we patched more than 500 websites, web shops and applications against two critical PHP vulnerabilities in two days. The patches are installed and the sites run on new infrastructure.

Would you like to stay up to date on the latest developments in web solutions and business digitization? Add Kabi as a preferred source on Google.

The attacks did not stop there. Since 21 October our servers have recorded far more attack attempts than before. Clients ask us whether their sites are still safe, so we are sharing what our daily reports show: how many attempts we see, what the attackers are looking for, and how we protect your data.

What do the numbers show?

Every morning we receive a system security report. It follows the traffic to our servers, records every suspicious request and stops the request automatically when the pattern is known to us.

On 20 October, before the vulnerability was made public, the report listed 5,002 security alerts in 24 hours. A week later there were more than 110,000. On 3 November there were almost 193,000.

Security alerts in 24 hours on our servers

Date Security alerts in 24 hours Distinct attacking IP addresses Addresses blocked in the firewall
20 October 2026 5,002 no data 29,940
28 October 2026 110,974 no data 30,658
1 November 2026 105,872 6,899 30,399
3 November 2026 192,789 9,272 33,722
5 November 2026 135,646 7,052 33,456
8 November 2026 42,367 8,167 35,560

Over the same period the number of addresses blocked in our firewall grew from 29,940 to 35,560.

Aggressive robots are a separate part of the picture. On 20 October they caused 3,178 alerts. In November the figure is around 13,000 a day. The daily count moves a great deal, which is normal during a wave of attacks.

What are attackers looking for?

Attackers rarely choose a target. They scan thousands of sites with the same list of weaknesses, and they do not check which technology each site actually uses.

What attackers try and how we stop it

Type of attempt What the attacker wants How we protect the site
Looking for settings files (.env) A file that holds database passwords, payment system keys and access to external services These files are not reachable from the web. We refuse the request and block the address.
Looking for the source code folder (.git) The whole code of the site, so they can look for flaws or forgotten passwords The folder is not published. Attempts are stopped automatically.
Exploiting known vulnerabilities in popular frameworks To get past the login, or to run their own code on the server A protective layer in front of the application recognises the pattern of the attack and stops it before it reaches the code.
Aggressive robots To download the content of the site quickly and in bulk, which slows the site down for real visitors We limit how many requests one address may send and block the addresses that keep going.
Looking for admin interfaces and vulnerable paths To find the back office login page and guess the passwords We stop requests to suspicious paths and block addresses that try to guess passwords.

Most attempts are aimed at files that hold passwords and settings. On 3 November, 2,257 different IP addresses tried to reach such files almost 109,000 times.

The second largest group is the attempts to exploit known vulnerabilities in other libraries published last year. These come from only a few hundred addresses a day, but they are persistent. Some addresses try the same thing more than a hundred times.

Aggressive robots belong in the same report, even though they are not an attack in the usual sense. We have written separately about the shared signal in robots.txt that tells AI crawlers whether they may use your content.

Why are there more attacks after a vulnerability is disclosed?

Once a vulnerability is public, attackers know exactly what to look for. Within days, sometimes within hours, tools appear that test it automatically on every server they can reach.

Anyone who has not installed the fix is exposed. Anyone who has installed it still gets scanned, because the attacker has no way of knowing which servers are already patched.

According to the Si21 technology portal, about 9.5 million vulnerable servers were reachable worldwide. One week after the fixes were released, only one third of them had been updated. Nearly 80 percent of the servers that were still vulnerable run old PHP versions for which no official fix exists. That is roughly five million servers that will never receive the fix.

This is why the threat will stay with us for a long time. Those servers remain available to attackers.

Owners of smaller sites often assume they are not interesting enough to attack. That is not how it works. Nobody is looking for your company. They are looking for a known vulnerability in the code, and it makes no difference whose site it sits on.

The consequences of an attack include:

  • stolen client data,
  • interrupted business and an interrupted website,
  • the server being used to send spam.

How we protect our clients' websites, web shops and applications?

Protection is not one setting. It is several layers that work together on the hosting infrastructure we run ourselves.

  • A firewall with tens of thousands of blocked addresses. An address that has attacked before no longer reaches any of our sites.
  • Shared lists of known attackers. Our system exchanges data with a network of other servers. An address that attacks one of them is reported to the others and stopped before it tries again.
  • Our own rules, written for our own solutions. We build and host only our own solutions, so we know what normal traffic on them looks like. We write and update our own rules for aggressive robots and for malicious paths.
  • Protection against known vulnerabilities. We stop attack attempts before they reach the application, including attempts aimed at technologies a site does not even use. A newly published vulnerability therefore does not leave the door open until the fix is installed.
  • Regular updates. The layers above buy time, they do not replace updates. We install fixes as part of routine maintenance, not only when they are urgent.

What you can do by? yourself

If we maintain your website, you do not need to do anything. The work described above is part of our service. A few things, though, are only in your hands.

  • Use strong passwords and switch on two-factor verification for access to the back office.
  • Do not share one user account between several employees. Give each person their own account, so you can see who changed what.
  • Remove access as soon as an employee leaves.
  • Tell us when something looks unusual, for example content you do not recognise or a sudden drop in visits.

If we do not maintain your website

Put five questions to your hosting provider.

  1. Have the PHP vulnerability fixes been installed, and when?
  2. Which PHP version does the site run on?
  3. Are the settings files and the source code unreachable from the web?
  4. Is there protection against attacks in front of the application?
  5. Does the provider watch for attacks and tell you when something happens?

If the answers are vague, that is an answer in itself.

PHP 7.4 has now received its last official fix. If your site runs on it, plan the upgrade soon. The first official fix was not planned for any version below 8.2, and the PHP community later supported 8.1, 8.0 and 7.4 as well. That was an exception, not a rule.

A move within the same branch of the code is part of maintenance. A move to a higher branch carries an additional cost.

Security is an important part of a good website

We develop websites and web shops on our own platform, we host them on our own infrastructure and we maintain them ourselves. Because all three parts are in our hands, we can respond to an attack as soon as we see it, without waiting for anyone else.

Security is not an extra. It is part of what makes a website work properly.

If you would like us to look after the security and the operation of your website, get in touch with us. We will go through what you need and agree how we could work together.

News Websites and web shops

Maybe you are interested

Read more