ResourcesIf you’re hacked — and how to stay safe
Practical, in-depth guides for small businesses and the people who run their websites. No jargon, no fear-selling — just what actually works.
Incident responseI’ve been hacked — what to do in the first hour
The first hour matters more than the next week. The goal is to stop the bleeding, preserve evidence, and lock attackers out before you start cleaning up. Work through these in order.
- Contain it. Put the site into maintenance mode or take it offline. If the server handles payments or connects to other systems, disconnect those integrations so an attacker can’t pivot or move money while you work. Containing first prevents the incident from spreading to customers and partners.
- Preserve evidence before you clean. Download the server and access logs, and take a copy of the current (compromised) files. If you delete everything and rebuild immediately, you lose the trail that tells you how they got in — and the same hole gets used again.
- Change every password and key — from a clean device. Hosting control panel, CMS admin, database, FTP/SFTP, email, and any API keys. Use a device you know is not compromised. Assume anything stored on the server, including secrets in config files, was copied.
- Find the entry point. The usual suspects: an outdated plugin or CMS core, an exposed file (a downloadable .env or backup), a weak admin password, or a reused password from another breach. Your host’s logs show what was accessed and when.
- Remove the backdoor. Attackers leave a way back in — hidden admin accounts, modified core files, scheduled tasks (cron jobs), or uploaded scripts in your uploads folder. Restoring from a known-clean backup taken before the compromise is usually safer and faster than cleaning in place.
- Patch before you go back online. Update the CMS, every plugin and theme, and the server software. If you restore without patching, bots re-exploit the same vulnerability within days — often hours.
- Turn on defences. Two-factor authentication for every admin, a web application firewall in front of the site, and login-attempt limits. Then monitor closely for a few weeks.
- Meet your notification duties. If customer data may have been taken, you may be legally required to notify affected people and a regulator (GDPR, PDPA and similar), often within a set deadline. Document what happened, what data was involved, and when — you’ll need it.
For a serious breach — payment data, large customer databases, or signs the attacker is still active — bring in a professional incident-response firm rather than going it alone.
How it happensAnatomy of a typical small-business website hack
Most SME sites are not targeted by a person at all. They’re found by automated bots that scan the entire internet looking for the same handful of weaknesses, around the clock. Understanding the pattern makes it far easier to break.
- Fingerprint. A bot loads your homepage and reads which software you run — WordPress, Joomla, the exact PHP and server versions, the plugins in your page source.
- Match. It compares those versions against a list of public vulnerabilities. An outdated plugin with a known flaw is an open invitation.
- Probe. In parallel it requests common exposed files — /.env, /.git/, backup.zip, wp-config.php.bak — hoping one is downloadable.
- Exploit or log in. It either exploits the vulnerable component or brute-forces the login page with stolen password lists. The emails you get about “failed login attempts” are this step.
- Persist and abuse. Once in, it adds a hidden admin, uploads a backdoor, and quietly uses your site to send spam, host scam pages, mine crypto, or skim card details — often for weeks before anyone notices.
Every step above is defeated by boring basics: keep software updated, don’t leave files in the web root, use strong unique passwords with two-factor authentication, and put a firewall in front. A scan tells you which of these a bot would find today. See each weakness with examples →
PreventionYour 10-minute hardening checklist
Turn on automatic updates
Outdated software is the number-one cause of SME website hacks. Enable auto-updates for your CMS core, plugins and themes. Where auto-update isn’t safe, set a weekly reminder to do it by hand.
Back up off-site and test it
Keep regular backups somewhere separate from the live server, and actually restore one to confirm it works. A backup you’ve never tested is a guess.
Enforce 2FA and strong passwords
A password manager plus two-factor authentication on every admin account stops the password-guessing bots in your logs completely. Never reuse passwords across sites.
Remove what you don’t use
Delete unused plugins, themes, admin accounts and old subdomains. Deactivated plugins can still be exploited; a forgotten subdomain can be hijacked. Every one is a door to keep locked.
Apply least privilege
Give each person the lowest access they need to do their job. Not everyone needs to be an administrator, and your daily login shouldn’t be the one with full control.
Put a firewall in front
A web application firewall (for example Cloudflare’s free tier) blocks a large share of automated attacks before they ever reach your site, and hides your origin server.
Lock down the login page
Limit login attempts, rename the default admin username, and consider restricting the admin area to your office IP or a VPN.
Keep files out of the web root
Never leave .env files, backups, database dumps or .git folders in a public folder. Serve only what visitors need to see.
Scams, phishing & deepfakesThe invoice-fraud and impersonation playbook — and how to beat it
The costliest attacks on small businesses often involve no hacking at all. They rely on tricking a person into sending money or credentials. The techniques are predictable once you know them.
Changed bank details
A supplier emails that their bank account has changed, just as a real invoice is due. Always verify a change of payment details by phoning a known number for the supplier — never a number or link in the email. This one habit prevents most SME losses.
Look-alike domains
Fraudsters register domains that look right at a glance — micros0ft-support.com, your-supplier-pay.com. Read the full sender domain and hover every link to see where it truly goes before you click.
Manufactured urgency
Scams create pressure — a locked account, an overdue payment, a boss who needs it “right now, don’t tell anyone”. Urgency plus secrecy is the tell. Slow down and verify through a second channel.
Deepfake voice and video
Attackers can now clone a director’s voice or appear on a video call to approve a payment. For anything that moves money, confirm through a separate known channel — a callback to a saved number, not the one that just called you.
Credential phishing
A fake login page captures your password. Check the address bar before typing credentials, and use a password manager — it won’t autofill on a look-alike domain, which is itself a warning.
Reused passwords
When one service is breached, attackers try those passwords everywhere. Unique passwords per site contain the damage. Check whether your email has appeared in a breach at Have I Been Pwned.
Not sure where you stand?
Run a free scan and get a prioritised list of exactly what to fix on your own site.
WebSafora provides general guidance, not legal advice. Rules on breach notification vary by country and industry.