Performance, Security & Care

Malware removal & site recovery

A cleanup that only removes the visible infection is not a cleanup. Attackers leave several backdoors precisely because they expect the obvious one to be found, and a site that is cleaned without closing the entry point is usually reinfected within days.

So the sequence is: contain, find how they got in, remove everything including the persistence mechanisms, then harden. Getting the browser warning lifted is the last step, not the first.

What is included

The work itself

Containment

Taking the site offline or into maintenance mode if it is actively serving malware or sending spam, and preserving a forensic copy before anything is modified.

Root cause analysis

Access and error logs, file modification timestamps and account activity, to establish the entry point, usually an outdated plugin, a stolen credential or a vulnerable upload handler.

Full cleanup

Removing injected code, web shells, malicious cron entries, database injections, rogue admin accounts and modified core files, verified against clean upstream copies rather than by eye.

Closing the entry point

Patching what was exploited, rotating every credential including database and FTP, and invalidating existing sessions.

Blocklist removal

Submitting for review to Google Safe Browsing, Search Console security issues, and any host or antivirus blocklists the domain landed on.

SEO damage assessment

Checking for spam pages, injected outbound links and cloaked content that was served only to search engines, and requesting reindexing after removal.

Post-incident hardening

File permissions, update policy, an actual backup schedule, and monitoring, so the next attempt is detected rather than discovered by a customer.

Written report

What happened, when, what was affected, and what was changed. Necessary if you have any obligation to notify anyone.

How I work on it

Process

Adjusted to the job, but this is the shape it usually takes.

  1. Preserve evidence

    A forensic copy taken before cleanup. Once files are overwritten, the ability to determine what happened is gone.

  2. Establish the entry point first

    Cleaning before you know how they got in almost guarantees reinfection.

  3. Rebuild from known-good where possible

    For a compromised CMS, replacing core and plugins with clean upstream copies is more reliable than trying to disinfect files individually.

  4. Monitor after

    Integrity monitoring for several weeks, because a missed backdoor typically reactivates within the first fortnight.

Questions

Things people ask

Only if you are confident the backup predates the compromise, and often it does not, infections sit quietly for weeks. Restoring also puts back the vulnerability that was exploited. A restore is a good starting point, not the whole answer.

A straightforward single-site infection is usually a day. If the whole server is affected, or the attacker had root access, it takes longer and I will usually recommend rebuilding the server rather than cleaning it. A compromised root account means nothing on that box can be fully trusted.

Usually, if it is dealt with quickly. Google generally restores position after the warning is lifted and spam content is removed. Damage lasts longer when the infection ran for months and search engines indexed a large number of spam pages.

Need help with malware removal & site recovery?

Tell me the situation and what you have already tried. I read the code and the server before quoting anything.

Get in touch