001 Exposure

What the bots are looking for, and why they keep missing

A month of edge logs from one site: hundreds of daily probes for software it has never run. What automated scanners ask for, and what that tells you.

Yesterday a request arrived for /alfa-rex.php7.

That is not somebody trying to break in. ALFA is a PHP webshell — a back door that attackers install on servers they have already taken. A request for it is a check for whether this site is already compromised, so that somebody else’s back door can be borrowed rather than built.

It got a 404. It will arrive again tomorrow.

What one day of it looks like

We pulled a month of edge logs from a site we look after. In twenty-four hours it returned 315 responses that were 404, across eighty distinct combinations of path and origin country. Across thirty-two days it logged 3,921 requests the firewall classified as threats, with 1,446 of them arriving on a single day.

Here is what they were asking for:

  • WordPress core files — /wp/index.php, /wordpress/index.php, /wp-login.php
  • A plugin endpoint with a history of being abused — /wp-json/batch/v1/, in six different spellings
  • WordPress fingerprint files — wlwmanifest.xml, under three different directory prefixes
  • Configuration dumps — /phpinfo.php, /php-info.php, /info.php, /tmp/phpinfo.php, /dev/phpinfo.php
  • One named plugin’s test endpoint
  • Environment variables — /webroot/index.php/_environment
  • Four spellings of that webshell

The site is a Python application. It has never run PHP. Not one of those requests could have worked on any day of its existence.

The detail that tells you it is a machine

Two of the probes were /wp-json/batch/v1/ and /wp-json/Batch/v1/.

Same origin. Same day. One capital letter apart.

Nobody types that twice. That is a list being worked through, with a variant included on the chance that a filter somewhere is case-sensitive and lets the second one past.

Nobody chose this company

This is the part worth internalizing, because it changes what you should conclude from a quiet security dashboard.

Scanners work through address space continuously. They are not researching your business, your revenue, or whether you hold anything worth taking. They ask every host they reach for the same list of things that are valuable if present: an unpatched plugin, a config file that prints database credentials, a login page worth guessing at, a back door somebody else already installed.

The cost of asking is close to zero, so they ask everyone. Being small has never been protection, because nothing in that process is aware of how small you are.

The old platform stays on the list

This site moved off WordPress about a year ago. The probes have not noticed.

They will not. There is no feedback loop that removes an address from a scan list because the software behind it changed. The requests are generated from the list, the list is copied and resold, and a 404 is not interesting enough to prune anything.

So the WordPress-shaped attack surface you removed keeps being probed, daily, indefinitely. The good news is the only news that matters here: it now misses every time.

What was actually protecting it

Not obscurity. Not the firewall, mostly — the firewall blocked twelve things that day, and the other three hundred simply had nowhere to land.

What protected it was that there was nothing at the end of the request. No PHP interpreter. No plugin directory. No admin login on a guessable path. The probes are identical to the ones that were arriving before the migration; the difference is entirely in what they find.

That is worth stating plainly, because it is the argument for doing this work before something happens rather than after. You do not reduce the probing. You make it pointless.

What you can check this week

Three things, none of which need a consultant:

  1. Pull a day of 404s from whatever sits in front of your site. If you use a CDN, this is one screen. You are looking for paths that were never yours. The volume usually surprises people.
  2. Ask what happens when one of them hits something. A 404 is fine. A 200 is a finding. A 500 means the request reached your application and confused it, which is a different and more interesting problem.
  3. Check whether your admin login is on the path everybody guesses. If it is, look at how many attempts it has seen. That number is rarely zero and rarely small.

If you have never looked at any of this, an hour will tell you where you stand. What we found on one system is written up here, and an audit is what this looks like done properly. Tell us what you are running and the reply will say honestly whether it is worth your money.

Recognise any of this in your own system? Describe what breaks and a person replies within one business day. Free, and a person is what’s at the other end.

Write to us  ·  The work  ·  What things cost  ·  All writing