The discovery is usually secondhand. A customer mentions the strange page they landed on. Your host suspends the account. Chrome puts a red warning in front of anyone trying to visit you. Occasionally you find it yourself, which means you were paying attention.
Two instincts follow, and both are expensive. The first is to start deleting anything that looks unfamiliar. The second is to restore last month's backup and hope it goes away. In both cases the damage from the response is routinely worse than the damage from the intrusion itself.
This piece is about what happens after you know. If you are not yet sure whether something is wrong, the symptoms are covered in our website hygiene checklist. Start there, then come back.
01
The first hour. What to do,
and what to leave alone.
Take a full copy before you change anything. Files and database, exactly as they are now, infected and all. This is the single most useful thing you can do in the first ten minutes. That copy is how anyone works out where the attacker got in and what they left behind. Delete first and you destroy the only record of what happened, which means you will be guessing at the entry point, which means it stays open.
Do not start deleting suspicious files. It feels productive. What it actually does is remove the visible symptoms while leaving the mechanism, so the site looks fine for a few days and then comes back exactly as it was.
Stop serving the problem to your customers. If the site is pushing spam pages or redirecting visitors somewhere unpleasant, take it into maintenance mode. A holding page for two days costs you far less than customers meeting a malware warning with your company name above it.
Tell your host early. In Singapore they have often noticed before you did, and may have suspended the account already. More usefully, they hold server and access logs that are frequently the fastest route to the entry point. Those logs also rotate, which is a good reason not to leave the call until next week.
Change passwords, but know it is not the fix. Do it from a device you trust. Understand that if an attacker has left a way back into the site itself, new passwords are an inconvenience to them rather than an eviction.
What Search Console shows youHacked content detected. Some pages on this site may have been modified by a third party.
Affected pages
/wp-content/uploads/2024/vt/
/wp-includes/tmp/rx-sg/
Detected 26 Aug 2026. First seen in crawl data 4 Aug 2026.
Note the gap between the two dates. That gap is the point.
Why restoring a backup
usually fails.
This is the advice everyone gets, and on its own it is the reason so many businesses get hacked twice.
The date you found it is not the date it started. Intrusions sit quietly. Spam pages are often served only to search engine crawlers and not to logged-in visitors, precisely so that the owner does not notice. By the time it surfaces, the backup you consider clean may have been taken weeks after the site was already compromised. Restoring it restores the problem.
A backup restores the vulnerability too. Whatever the attacker used to get in was present in the version you are rolling back to. Even a genuinely clean restore puts you back at the exact configuration that was successfully attacked. Automated scanners revisit sites they have already breached.
Modern intrusions hide inside legitimate files. Security researchers tracking the WordPress ecosystem report that attackers increasingly inject code into real core, plugin and theme files rather than dropping obvious new ones. Some persistence techniques run in server memory and rewrite files such as index.php the moment they are restored. A scanner looking for unfamiliar filenames finds nothing wrong.
Backups are essential. They are just not a cleanup on their own. A backup is one input into a recovery, alongside knowing how they got in and closing it.
Discovery is not the beginning of the infection. By the time you see it, it has usually been living there for weeks.03
How they actually
got in.
Almost always a plugin. Of the vulnerabilities disclosed across the WordPress ecosystem in 2025, researchers attribute roughly nine in ten to plugins rather than to WordPress core. New plugin vulnerabilities are disclosed at a rate of a few hundred a week, and a substantial share have no patch available on the day they become public. Core is comparatively well defended. The twenty-three plugins layered on top are the attack surface.
The plugin you forgot is the dangerous one. Deactivated is not removed. Deactivated plugin code still sits on the server and can often still be reached. The same is true of the old theme you switched away from and the staging copy at /old that somebody set up in 2023 and nobody has updated since.
Accounts that outlived their purpose. The intern from two years ago who still has an administrator role. The developer account nobody revoked. A password reused on a service that was breached elsewhere. None of this is exotic.
You were almost certainly not targeted. This matters more than it sounds, because business owners take it personally. The overwhelming majority of these compromises are automated. Software scans enormous numbers of sites for one known weakness and takes whatever it finds. Nobody chose your bakery. Your bakery simply answered.
04What a proper cleanup
actually involves.
Establish the entry point before removing anything. Server logs, file modification times, and the forensic copy taken at the start. Until you can say how they got in, you cannot know whether you have finished.
Replace rather than clean. Core, plugin and theme files get replaced wholesale from known-good sources instead of being edited to remove the bad parts. It is faster and it removes the guesswork about whether a file is now genuinely clean. Custom code and the database need line-by-line attention, because they have no known-good version to compare against.
Hunt the things designed to survive cleanup. Backdoors in unexpected directories, scheduled tasks that reinstall the payload, injected rows in the database, unfamiliar administrator accounts, modified .htaccess rules, and redirects that trigger only for visitors arriving from search results. This stage is what separates a cleanup that holds from one that quietly does not.
Close the vector, then rotate everything. Patch or remove what let them in. Then change every credential involved: CMS accounts, database, hosting panel, FTP and SFTP keys, and any API keys the site holds for payment or email services.
Then deal with your reputation, which is a separate job. Request a review in Search Console once the site is genuinely clean, because Google will not lift a warning on its own schedule. Check whether your domain sits on browser or host blacklists. If your server was used to send spam, your ordinary business email deliverability may be damaged and will need its own attention. Businesses regularly finish the technical recovery and then wonder for weeks why their invoices keep landing in customers' spam folders.
05How long it takes, and
what it really costs.
A straightforward case is a day or two. Recent backup, obvious entry point, contained damage, no persistence worth the name. Many compromises fall into this category.
A stubborn one takes longer, and usually for one of three reasons: no usable backup, an intrusion that has been resident long enough to spread through the database, or heavy customisation with no clean reference version to restore from.
The cleanup is rarely the expensive part. The cost is the days spent behind a browser warning, the search visibility that dips while Google keeps a hacked-content flag on your listing, and the customers who tried to reach you during it and quietly went elsewhere. That is the real argument for spending the extra half day to do it properly the first time.
06Making a second one
unlikely.
The fundamentals of updates, strong credentials and two-factor authentication are in our hygiene checklist and we will not repeat them here. These are the measures that specifically address reinfection.
Before you put the site back online
Reduce what you are running. Every plugin is somebody else's code with its own update schedule and its own risk. The most effective hardening available to most sites is removal: cutting thirty-odd plugins down to the dozen that earn their place.
Put something in front of the site. Filtering traffic at the edge, before it reaches your server, stops the automated scanning that finds most victims. It is inexpensive and it is the difference between being probed and being breached.
07Where we come in.
Cleanup and recovery is repair work, which is the core of what we do. We take the forensic copy, find the entry point, remove what is there, close what let it in, and handle the Search Console review and blacklist removal afterwards so you are not managing that alongside running your business.
You get a written account of how they got in, what was changed, and what we did about it. Not a scanner report with a green tick, which tells you nothing about whether the door is still open.
If your site is compromised right now, the useful first step is the one at the top of this page. Take a full copy before anyone touches anything, then call someone.
Site compromised, or not
sure if it still is?
We handle hacked site recovery for Singapore businesses. Tell us what you are seeing and we will tell you what it takes to clean it properly.
Get in touch