Contain first, clean second
Hacked Website Emergency: Contain It, Keep the Evidence, Then Clean
The site still loads. That is the unsettling part. Type the address yourself and it looks normal, while a customer who clicks it from Google lands on a pill shop in another hemisphere. Someone else has a key to your building, and the first hour is about changing the locks in the right order.
November 18, 2026 · 10 min read
- 13:05 Google visitors redirected; direct visits look normal
- 13:11 host snapshot taken; files, database, logs copied off
- 13:19 503 maintenance page served from the host, not the site
- 13:27 hosting, SFTP, database and admin passwords changed
- 13:34 unknown admin user wp_support2 recorded, then removed
- 14:20 way in: outdated slider plugin; patched, files cleaned
- 15:02 site back online; review requested in Search Console
The short answer
If your website is hacked, contain it before you clean it. Take the site offline with a temporary maintenance response served from outside the infected server, tell your host, and copy the files, database and logs as evidence. Change every password from a clean device. Only after the way in is closed should you clean the site and request a review in Google Search Console.
On this page
- Signs of a break-in rather than an ordinary breakdown
- Sixty minutes after you find the intruder
- Getting the red warning lifted: Google's review, as written
- Why the way in matters more than the mess
- Attorneys, insurers and police: when a hack turns legal
- Shortcuts that let the intruder walk back in
- A fixed price for WordPress cleanup; an estimate for everything else
Signs of a break-in rather than an ordinary breakdown
A broken site fails in plain sight. A hacked site often hides. Google's spam policies, updated August 28, 2026, note that hacked redirects can depend on the referrer, the browser or the device, so a page may redirect when clicked from Google Search and not when you type the address. The owner sees a healthy site. The customers see something else. That gap is deliberate, and it is why a hack can run for weeks before anyone inside the business notices.
Visitors from search land somewhere else
Customers say your listing opens a gambling or pharmacy site. You cannot reproduce it from a bookmark. Try a search on a phone that has never visited the site.
Pages you never wrote, under your domain
A site search on Google shows product pages in another language or thousands of strange URLs. Google calls this content or URL injection. Some injected code never touches your server at all: in November 2026 an attacker reached visitors of 178 organizations through a vendor's testing script, which our Optimizely hack breakdown explains. When the tampered file is a script your pages borrow from someone else, our script compromise response covers that case.
A red warning before your home page
Browsers show a full-screen warning, or search results carry a note. Google's Search Console lists the reason in its Security Issues report.
A suspension notice from the host
Hosts switch off accounts that send spam or serve malware. The host suspension walkthrough covers the notice itself.
Logins nobody on your team created
A new administrator in the site, a new user on the hosting account, or a Search Console owner you do not recognize. Record it before removing it.
Google's Security Issues report help page, read in November 2026, names the categories it may flag, among them Hacked: Malware, Hacked: Code injection, Hacked: Content injection and Hacked: URL injection, plus deceptive pages and harmful downloads. Each issue shows sample URLs and the date Google first detected it. That date is evidence. Write it down before anything changes.
Sixty minutes after you find the intruder
Google publishes no single numbered recovery checklist; the closest is a set of web.dev guides, quoted below. The order here is ours, built around one idea: every action should either stop harm to visitors or preserve what you will need later. Cleaning comes last on purpose. Done first, it destroys the trail that shows how the intruder got in.
- 1
Copy everything before you delete anything
Ask the host for a snapshot, or download the site files, a database export and the server's access and error logs. Store them off the server. Note the time you first noticed the problem and what you saw.
- 2
Take the site offline from outside
Google's web.dev guide to quarantining a site says a 503 is the useful signal and that "the response should occur from outside your compromised server or site," for example a host-level maintenance page or DNS pointed at a static page elsewhere. If you change DNS, change only the website's record and leave the mail records alone. A maintenance plugin inside the hacked site is not outside it.
- 3
Tell the hosting company
The same guide says: "Contact your hoster to make them aware of the situation." They may see the attack across other accounts, hold logs you cannot reach, and need to know before they suspend you.
- 4
Change every password from a clean device
Web.dev lists FTP, database, system administrator and CMS logins. Add the registrar, the hosting account, and any email inbox that can reset them. Turn on two-factor sign-in wherever it is offered. Use a computer you trust, not the one that may be infected.
- 5
Check who can reach Search Console
Read the list of owners and users on the property and record anyone you do not recognize. Google's ownership help page warns that a removed owner can re-verify unless you also delete their verification token.
- 6
Ask whether customer data was exposed
If the site stores accounts, orders or form submissions with personal details, stop here and call your attorney and insurer before cleaning. Our data breach first hours page explains why.
- 7
Then close the hole and clean
Find the way in, patch it, remove the intruder's files and database entries, and only then bring the site back. Or hand the whole job to someone who does it weekly.
Getting the red warning lifted: Google's review, as written
Once the site is clean, Google has to agree. Its web.dev page on requesting a review, read in November 2026, says you should first have "Verified ownership of your site in Search Console," "Cleaned your site of the hacker's vandalism," "Corrected the vulnerability," and "Brought your clean site back online." Then, per the Security Issues help page, you fix every affected page and "select Request Review in the Security Issues report," explaining the issue, the fix and the result.
| What Google says | What it means for you | |
|---|---|---|
| Any security review | "A review can take from a few days to a few weeks to complete." | Plan around a range; nobody can promise a date |
| Spam hacks | Reviews "can require up to several weeks to process" | Injected pages usually mean the longer wait |
| Malware | Reviews "require a few days to process" | Faster, if the site is truly clean |
| Approved | Warnings are removed within 72 hours, per web.dev | The warning lingers briefly after approval |
| Resubmitting early | "don't resubmit your request before you get a final decision" | A second request can slow the next one |
| Flip-flopping sites | Repeat Offender status "persists for 30 days" | A half-clean site that gets reinfected can wait a month to ask again |

Google's Safe Browsing site, as of November 2026, says the service "helps protect over five billion devices every day" and links a Site Status tool in Google's Transparency Report, where anyone can look up how Google currently rates your address. Check it before and after the review.
Why the way in matters more than the mess
The spam pages are the symptom. The open door is the disease. On WordPress, the door is very often a component nobody updated. Patchstack's State of WordPress Security in 2026 counted 11,334 new vulnerabilities in the WordPress ecosystem in 2025, with 91% of those new vulnerabilities found in plugins. Patchstack also reports that 46% did not get a fix from the developer in time for public disclosure, and that "the weighted median time to first exploit is 5 hours."
Read those numbers carefully. They count weaknesses found, not sites hacked. But they explain why the cleanup that skips the root cause fails: restore yesterday's backup and you restore yesterday's hole, and the same automated scanner that found it the first time will find it again. On PHP servers, our signs of compromise checklist shows where intruders hide their return tickets.
A restore without a patch is an invitation with the same address on it.
Attorneys, insurers and police: when a hack turns legal
If the site held customer data, the hack may be a data breach, and the rules change. The Federal Trade Commission's Data Breach Response guide, August 2023, tells businesses: "Call your local police department immediately," and to "Check state and federal laws or regulations for any specific requirements for your business." It also says: "Don't destroy any forensic evidence in the course of your investigation and remediation." That is why step one above is a copy, not a cleanup.
Deadlines exist. The Texas Business and Commerce Code, as of November 2026, requires notice to affected individuals "not later than the 60th day" after a breach is determined, and to the Attorney General "not later than the 30th day" when at least 250 Texas residents are involved. Laws differ by state, and other states set their own deadlines and thresholds. Your attorney decides what applies. If you carry cyber insurance, call the insurer before cleaning; your policy may say who investigates.
Shortcuts that let the intruder walk back in
- Deleting the spam pages you can see. Injected code usually sits in more places than the pages it creates: theme files, uploads folders, the database, scheduled tasks.
- Changing only the CMS password. If the intruder has hosting, FTP or database credentials, the CMS password was never the door.
- Leaving the strange admin account until later. Record its name and creation date, then remove it the same hour.
- Cleaning while the infected site keeps serving visitors. Every hour it stays up, customers can catch whatever it serves. Quarantine first.
- Requesting Google's review the moment the home page looks clean. Google warns an unfixed request can get a site "marked as a repeat offender."
- Moving to a new host to escape the problem. The infected files move with you.
Each of these feels like decisive action, which is exactly what makes them tempting at 11 at night. If the hack also took the domain or the email with it, the domain and DNS emergency page covers registrar access, and the developer disappeared page covers sites where nobody on your side holds the logins.
A fixed price for WordPress cleanup; an estimate for everything else
We respond the same business day; hours are on the contact page. For WordPress, our Fix it now malware cleanup is $349, paid online on the WordPress malware removal page or the host suspension page. It covers infected files and database entries removed, passwords and keys changed, the way in closed, and a blocklist review requested where Google or your host flagged the site. We start within one business day of payment, with a full refund if we can't fix it.
Other platforms, custom applications and servers are from $575, depending on complexity, with a written estimate before work starts; the emergency pricing page explains what moves it. More WordPress help lives on the WordPress repair page. We do not promise when Google will finish its review; Google does not either. Our malware removal service covers the longer engagement, and emergency website repair lists the logins to have ready.
Not sure it is a hack at all? Start with the website down checklist or the emergency repair overview. Afterward, a hosting and maintenance plan from $55 a month keeps updates and monitoring on someone's calendar. DataCram is a San Antonio web studio, building for the web since 1999. See our work or call (210) 346-0848.
Questions owners ask in an emergency
Take it offline. Google's web.dev quarantine guide says to stop serving content to users and to return a 503 from outside the compromised server, such as a host-level maintenance page. Leaving an infected site up exposes every visitor to whatever it is serving and can deepen the damage to your reputation with browsers and search engines.
Google's Security Issues help says, as of November 2026, that a review can take from a few days to a few weeks. Its web.dev guide says spam hacks can need up to several weeks and malware a few days, and that warnings come off within 72 hours of a clean result. Nobody can promise a date, including us.
It may remove the visible damage, but it also restores whatever let the intruder in, and you may not know when the infection started. Copy the hacked site for evidence first, find and patch the vulnerability, then decide whether a restore or a cleanup is the better path.
It depends on what data the site held and where your customers live, and we cannot answer it for you. Texas, for example, sets notice deadlines in its Business and Commerce Code; other states differ. If personal information may have been exposed, talk to your attorney and insurer before you notify anyone or clean anything.
Google's spam policies note that hacked redirects can depend on the referrer, browser or device. A page may redirect visitors who arrive from Google Search but not someone who types the address. Test from a phone that has never visited the site, starting from a Google search result.
Removal of infected files and database entries, new passwords and keys, the way in closed, and a blocklist review requested where Google or your host flagged the site. You pay online, we start within one business day of payment, and you get a full refund if we can't fix it.
Keep reading
- Not legal advice. Read anyway.Data Breach: What to Do in the First Hours, Before Anyone Wipes the EvidenceThe first hours after a data breach: contain it without destroying evidence, call your attorney, insurer and police, and know the Texas notice deadlines.
- The first fifteen minutesWebsite Down? The First 15 Minutes, Before Anyone Touches AnythingYour website is down. Check it from outside, rule out renewals and DNS, read the error code, and skip the moves that turn a short outage into a long one.
- The website offerEmergency Website Repair: Who to Call When the Site Is Down, and What Happens After You DoWebsite down and no one to call? A same-business-day reply, fixed WordPress repair prices, from $575 for other platforms, and the checks before we sign off.
- The software offerEmergency Software Repair: Triage, Containment and a Written Root Cause for Broken Custom SoftwareCustom software or a web app broken today? Triage, stop the damage, restore, find the root cause, and a written estimate first. From $575, depending on scope.
- The mobile offerEmergency App Repair: An iOS and Android Developer for Crashes, Store Trouble and Expired CertificatesApp crashing, rejected or pulled from the store? Crash triage, store fixes, certificates and the access we need, from $575 with a written estimate first.
- Rejected by App ReviewApp Store Rejection: What to Do in the First Hour After Apple Turns Down Your AppApple rejected your app or update. Read the cited guideline, check Apple's common issues, fix or reply, and appeal only when it fits. No approval promised.
- Everything in Emergency RepairSee the section
From the Insights desk
- Why Your WordPress Form Gets Spammed — and the Fix That Doesn't Annoy Real CustomersForm spam isn't the problem — it's what the spam does: buried leads, a poisoned CRM, and an inbox you've learned to ignore. Why CAPTCHAs make it worse, and the silent fix that stops bots without costing you real customers.
- Next.js or PHP? The Better Question Is Who Patches Your SiteApache, NGINX and PHP all shipped urgent fixes between November 11 and 19, 2026. PHP is not the villain, and Next.js has patch days too. The real difference is who installs the fix, how fast, and how much of your site runs code at all.
Tell us what the intruder left behind
Describe what customers see, any warnings or host notices, and the platform. We reply the same business day with the first steps and a price.
Which of these sounds like you? (pick any)
Rather talk now? Call (210) 346-0848.