In short: I repair hacked WordPress sites at 30 EUR an hour, and most cases take 5 to 12 working hours. That comes to 150 to 360 EUR, roughly 750 to 1,800 RON. The hours go up when several sites share one hosting account, when there is no clean backup, or when the infection has been in for a long time. Until then, do not delete anything and do not restore a backup.
The hacked website repair cost with me is hourly: 30 EUR an hour, and most cases are done in 5 to 12 working hours. That comes to 150 to 360 EUR, roughly 750 to 1,800 RON. I do not quote a fixed price up front, because until I see the files and the logs, nobody knows how big the problem is. What I can describe is what fits into that time and what makes it longer.
If you only have a suspicion so far, first go through the seven signs of a hack.
What does the hacked website repair cost cover?
- A backup before I touch anything. I save the infected state off the server. This is what later shows what happened, and it is also needed if a data breach has to be reported.
- Finding the entry point. Logs, unknown admins, recent PHP files. If the logs are already gone, it cannot always be found.
- Cleaning. I compare WordPress core and the plugins with the official checksums, and remove the foreign files, users and plugins.
- Replacing the keys. A new password for every admin, new secret keys in WordPress, and a new key for every connected service (invoicing, newsletter, email sending).
- Hardening. Two-factor authentication, the built-in file editor disabled, PHP execution disabled in the uploads folder.
- A check through the eyes of Google. I look at what the search robot sees, and request a review in Search Console if needed.
At the end you get it in writing: what I found, what I fixed, and what is left for you to do.
What turns 5 hours into 12?
- Several WordPress installations on one hosting account. The malware writes from one into the other, so all of them have to be cleaned at the same time.
- No clean backup. If every backup was made after the infection, what is yours and what is the attacker's has to be sorted by hand.
- It has been in for a long time. In one of my cases the first traces were three years old, and a migration had carried the infection over to the new hosting too.
- A webshop. More connected services, more keys, and I have to check whether the attacker had access to the orders.
The examples come from three earlier cases of mine. I described them in detail, without names.
When cleaning is not enough
Some infections write themselves back within minutes even after two cleanups, because they sit at the level of the hosting account. Then the site has to be rebuilt clean on a new hosting. That is more work than the range above, so I give a separate quote for it once I have seen what we are dealing with.
What should you do until someone looks at it?
- Do not delete anything. The suspicious file is the evidence of how they got in.
- Do not restore a backup blindly. If the backup is infected too, you only lose time with it.
- Change your password from another computer. If the password was stolen from your own computer, the new one will be taken from there as well.
- Tell your hosting provider. Many hosts keep the logs for only a few days, so ask for them right away.
How long does it take?
The 5 to 12 working hours are spread over several days, because there is waiting in between: for the hosting logs, for the new passwords, for the new keys of the connected services. If Google has put a warning on the site, the review on their side can take further days.
If your site is down right now, write to me with its address and I will tell you what I see on it from the outside. After the repair, monthly maintenance starts at 250 RON a month, and it includes updates, daily backups and monitoring.
