How hackers find websites to attack, and how to not be on the list
Attackers do not pick your business. Their tools sweep the internet for known weak software. How they find sites, and what to check so yours is a poor target.
Many owners of small sites believe the same thing: “Nobody would bother hacking us. We are too small.” It sounds sensible, and it is the main reason small sites get hacked. Most attacks are not aimed at a business at all. They are aimed at a list of websites that share a weakness, and your site lands on the list because of what it runs, not because of who you are.
This guide explains, in plain words, how attackers find websites, and what you can do so that yours is a poor target.
Attackers rarely choose you by name
Think of a thief walking down a street trying every door handle. They are not interested in your house in particular. They want any door that opens. Automated attack tools work the same way: they visit very large numbers of websites, one after another, and note which ones answer in a helpful way.
That is why a small shop, a school or a clinic can be hit by the same attack as a big company. The tool does not care who owns the site. It cares whether the site is running something it knows how to break.
How they find sites to attack
You do not need the technical detail, only the idea behind each method.
- They ask the website what it is. Every site answers visitors with some background information. The OWASP Web Security Testing Guide, a well known reference for security testers, explains that this information can reveal the type and version of the software a site runs, and that servers running older versions without the latest security fixes can be open to known attacks for that version. In plain words: if your site says “I am running an old version of this software”, an attacker knows which known weakness to try.
- They recognise well known software. OWASP also notes that very many sites are built on popular, well known applications such as WordPress, and that these have recognisable markers: in the information the site sends, in its cookies, in its page code, and in files and folders that have standard names. One marker is usually not enough, so tools combine several to be sure. Being popular is not a fault. It simply means that when a flaw is found in popular software, there are a lot of sites to try it on.
- They look for sites that match a new flaw. When a hole is made public, attackers can scan for the software it affects and try it everywhere at once. Our post on why WordPress plugins are the weak spot covers why the gap between “fix released” and “fix installed” is where the danger is.
- They try the obvious logins. The WordPress hardening guide says that account names such as admin or webmaster are typically attacked first. A predictable name means half of the login is already guessed.
What this means for you
Three things follow from how these tools work.
- Size does not protect you. Being predictable hurts you. The sites that get picked are the ones that look like a known weakness: out of date, running something forgotten, or using an obvious login name.
- You are tested constantly, so small gaps matter. Nobody needs to decide to attack you for a weak spot to be found.
- Hiding things is not enough on its own. The WordPress guide calls “security through obscurity” generally an unsound main strategy, though it lists a few places where hiding information can help. Keep things out of view, but do not rely on that alone. The real protection is that the software is current and the doors are locked.
Six checks that make your site a poor target
None of these needs you to be technical. Some need your developer or host to do them.
- Know what your site runs. Ask for a list of the software, plugins and themes, with versions. If nobody can produce it, that is the first thing to fix.
- Keep everything updated, and take a backup first. Old versions are what attackers look for.
- Remove what you do not use. An unused plugin or an old test site is a door nobody is watching.
- Avoid obvious login names. Do not use “admin” or the name of your business. Use a password manager so every login has a long, unique password. See how to share passwords with staff safely.
- Turn on two-step login for everyone who can edit the site. Read two-factor authentication explained.
- Look at your site from the outside. What can a stranger learn about it without logging in? That is exactly what the tools above see. The free checker below shows you.
If you want a wider list, see our ten-minute website safety checklist.
What to ask your developer or host
- What software and which versions does the site run, and what is out of date today?
- Does the site announce the exact version of its software to visitors, and does it need to?
- Who has an admin login, and are any of them shared or still in use by people who left?
- Are two-step login and automatic security updates switched on where they can be?
- If a new flaw is announced for software we use, who hears about it, and how fast do we act?
Want to see what a stranger sees?
Start with the free website security checker. It looks at your site from the outside, the way an automated tool would, and points out weaknesses worth fixing. It cannot see inside your dashboard, so it does not replace a proper review.
For the review and the fixes, see our website security service.
- Email hello@wpfoss.com
- WhatsApp +254 118 271 160
- Tell us what you need
Sources and further reading
- Fingerprint Web Server (WSTG-INFO-02), OWASP Web Security Testing Guide v4.2. Source for what a site’s answers reveal about its software and version, and that older unpatched versions can be open to known attacks.
- Fingerprint Web Application Framework (WSTG-INFO-08), OWASP Web Security Testing Guide v4.2. Source for well known applications such as WordPress having recognisable markers, and tools combining several markers for accuracy.
- Hardening WordPress, WordPress Advanced Administration Handbook. Source for admin and webmaster usernames being attacked first, and for “security through obscurity” being generally unsound as a main strategy.
