Last week we wrote about the third week of the sensor on digimasi.com: requests jumped and WordPress almost caught up with .env. In week four, from Monday 2 November to Sunday 8 November, the pattern turned around. There were fewer bots and a third fewer requests. But almost as many requests went after .env files as before, so now half of all requests were aimed at them.
The numbers
- 1,988 requests from 121 IP addresses, recorded from 2 November at 00:00 WIB (Jakarta time) to the end of 8 November.
- Those addresses are registered in 21 countries. That is where the servers are, not necessarily where the people are.
- On average each address sent about 16 requests, about the same as last week.
- Not a single login guess this week. It is the first week without one since the sensor started.
Nothing succeeded. The files they asked for do not exist on our website, so every request just got a "not found" page.
Compared with week three
- Requests fell by about a third: from 2,976 to 1,988. IP addresses fell from 179 to 121, and countries from 29 to 21.
- .env hardly changed: from 986 to 967 requests. Because everything else fell, its share rose from a third to almost half (49%).
- WordPress dropped sharply: from 936 to 369 requests, and from 100 to 62 addresses. Last week WordPress almost matched .env; this week it was less than half of it.
- PHP, .git and other configuration files fell too, each by about 40–46%: PHP from 313 to 171, .git from 253 to 152, other configuration from 221 to 120.
- Backup files actually rose a little: from 72 to 86 requests, and from 7 to 9 addresses.
What they were looking for
- Secret .env configuration files (967 requests, 54 addresses). Nine of the ten most requested paths were variations of .env: /.env (70), /.env.production (42), /.env.backup (35), /.env.bak (35), /.env.development (34), /.env.local (34), /.env.old (33), /.env.dev (30) and /.env.save (28). /.env.development and /.env.dev came back into the top ten this week.
- WordPress (369 requests, 62 addresses). Our website does not use WordPress.
- PHP files (171 requests, 24 addresses). Our website does not use PHP either.
- The .git code-history folder (152 requests, 45 addresses). /.git/config was still the only non-.env path in the top ten (55 times, from 36 addresses).
- Other configuration files (120 requests, 22 addresses).
- Backup files (86 requests, 9 addresses).
- Cloud and server keys (58 requests, 19 addresses), admin panels (52 requests) and framework-specific paths (13 requests).
What stands out: fewer bots, a narrower target
For the first three weeks the number of bots kept rising. In week four it fell for the first time. The bots that dropped off most were the ones trying WordPress and PHP. The bots looking for .env kept coming in almost the same numbers. In other words, an exposed .env file stays the main target, in busy weeks and quiet ones.
The networks shifted as well. Google LLC was now the largest (802 requests from 31 addresses), followed by TECHOFF SRV LIMITED (513 from 6 addresses), which sent 1,000 requests from 22 addresses the week before. Then came TC DATACENTER (134 from 8 addresses) and DigitalOcean (125 from 34 addresses). A network name here is the owner of the address block, usually a server or cloud provider. Anyone who rents a server there can use it, so it does not mean the company itself sent the requests.
The Netherlands stayed on top (668 requests from 21 addresses), followed by the United States (305), Belgium (215), Poland (153), Australia (141, from just 3 addresses) and Singapore (137). Australia entered the top ten for the first time, and India came back after the first week.
Check your own website
You can check all of this yourself in five minutes, on a website you own:
- Open yourdomain.com/.env in a browser. You should see "not found". If you see the file's contents instead, move that file out of the public folder right away, then change every password and key in it.
- Try the variations too: /.env.production, /.env.development, /.env.dev, /.env.backup, /.env.bak. This week the bots guessed nine different names.
- Open yourdomain.com/.git/config. That should also be "not found". If you see text, your .git folder is open to anyone, and so is your website's code history.
- Make sure no backup files (.zip, .sql, .bak) are left in the website folder.
- For a quicker route, read our guide to an exposed .env file and .git folder, or use our free tools at /en/tools/.
A note on this data
We only observe. All data comes from bots that came to digimasi.com on their own; we never scan anyone else's website, and we do not show IP addresses here. Addresses that clearly attack us are reported to AbuseIPDB. The full method is on the methodology page, and each week's numbers are in the weekly record.
Data: Digimasi security research, weekly sensor record (https://doi.org/10.5281/zenodo.23655270).
We will keep recording and comparing the results week by week.