Hacked WordPress Website in India: A Business Owner’s Incident Plan for Cleanup, Google Review and CERT-In Reporting

A hacked website rarely announces itself with a dramatic defaced homepage. More often a customer sends a screenshot of a strange search result, your host suspends the account, a browser shows a red warning, or someone notices an administrator account nobody remembers creating. The technical cleanup matters, but so do the decisions around it: who is in charge, what evidence to keep, whether to restore or rebuild, what to tell customers, when to ask Google for a review, and whether you have a reporting duty in India.

This guide is written for the owner or manager of a business website, usually on WordPress, who has to run that response even if someone else does the technical work. It does not replace a security professional for a serious compromise. It helps you make better decisions, give your developer or host a clear brief, and avoid the mistakes that turn a short incident into a long one.

First, confirm what kind of problem you have

Not every broken website is a hack. A white screen after a plugin update, an expired SSL certificate or a hosting outage can look alarming but needs a different fix; the website troubleshooting guide covers those cases. WordPress’s own FAQ on hacked sites suggests describing the specific symptoms, which it calls indicators of compromise, before asking for help.

Signs that point to a genuine compromise include:

  • Google Search Console shows an entry in the Security issues report, or search results show “This site may be hacked”.
  • Chrome or another browser shows a dangerous or deceptive site warning.
  • Your host has disabled the site or reported malware or outbound spam.
  • Visitors are redirected to gambling, pharmacy or fake prize pages, sometimes only on mobile or only when they arrive from search.
  • A site:yourdomain search in Google lists pages you never created, often in another language.
  • New administrator users, changed passwords or unfamiliar plugins appear in WordPress.
  • Customers report spam email that seems to come from your domain or server.
What you seeLikely categoryWhere to look first
Spam pages or links you did not createHacked content (content or URL injection)Search Console Security issues report, site: search
Browser warning that the site may harm visitorsMalware or harmful downloadsSecurity issues report, host malware scan
Pages that imitate a login or ask for card detailsSocial engineering (deceptive pages)Security issues report, the flagged URLs
Redirects only for some visitorsCode injection or cloakingHost logs, URL Inspection, command-line fetches
Unknown admin accounts but no visible spamUnauthorised accessWordPress Users screen, hosting access logs

Google’s Security issues report help page explains that the report shows Google’s findings when it determines a site was hacked or behaves in a way that could harm visitors, grouped as hacked content, malware and unwanted software, and social engineering. It also warns that you may not be able to reproduce a warning yourself, because warnings depend on browsing context, and that the report should be treated as the source of truth for whether Google still sees an issue. Sample URLs in the report are only a sample, so a short list does not mean the problem is small.

Be careful when checking flagged pages. Google advises against opening suspected infected pages directly in a browser, because malware can target browsers and attackers often cloak spam so owners do not see it. Safer options are the URL Inspection tool, which shows how Google sees a page, or a developer fetching pages from the command line.

Appoint one incident lead and open an incident log

The first useful action is not technical. Decide who is running the response and start writing things down. WordPress’s FAQ puts documentation first: what you saw, when you noticed it (including the time zone), and what changed recently, such as a new plugin, theme edit or widget. It calls this the baseline for an incident report.

The incident lead does not need to be technical. Their job is to keep decisions, access and communication in one place. In a small business that may be the owner; in a larger one, an operations or IT manager. The developer, host or security specialist does the cleanup and reports to that person.

Keep a simple log with these columns:

Time and date (IST)What was observed or doneBy whomEvidence kept
Customer reported redirect from Google resultScreenshot, customer message
Security issues report checkedScreenshot of issue type and sample URLs
Host informed; ticket number recordedTicket email
Full copy of files and database takenStorage location

This log becomes the raw material for your host ticket, the brief to your developer, any regulatory report, your Google review request and your own post-incident review. It also protects you if questions about what happened arise later.

Contain first, but preserve evidence

There is a tension at the start of every incident. You want the problem gone immediately, but deleting files or restoring an old backup too early can destroy the evidence that shows how the attacker got in. Without that, the same weakness is often used again.

A sensible order for a business owner to agree with the technical team:

  1. Take a copy of the site as it is now. WordPress’s FAQ recommends one more snapshot of the environment before cleaning, even if it is infected, so you have a reference if something goes badly wrong. Ask for files, database and, if the host provides them, server access logs. Store the copy where it cannot run on the live server.
  2. Ask your host what they see. WordPress notes that on shared hosting a hack may affect more than one site, and the host may already be taking action or can confirm whether the problem is an attack or a service fault.
  3. Limit harm to visitors. If pages are redirecting people to malicious sites or serving malware, ask the developer or host about putting the site into maintenance mode or restricting access while cleaning. This is a business decision: you trade some downtime for not exposing customers.
  4. Lock down access. WordPress’s FAQ recommends forcing password resets for users, especially administrators, and replacing the secret keys in wp-config.php so existing logged-in sessions are ended. Remember every access point: WordPress admin, hosting control panel, FTP or SFTP, and the database.
  5. Check the devices used to manage the site. WordPress points out that infections sometimes start on the site owner’s own computer, where malware captures login details. Run a full scan on the computers of anyone with admin access.

If the person who built the site still controls the hosting account or domain, you may not be able to do some of this quickly. That is a good reason to confirm ownership of every account before an incident; the website handover checklist explains how to take control of domain, hosting, WordPress and Google access.

Check the CERT-In reporting requirement

Indian businesses often miss this step. This section summarises what the official documents say. It is general information, not legal advice. Whether and how the requirement applies to your organisation and incident is a question for a qualified lawyer, and you should get that advice quickly, because the time limit is short.

CERT-In, the Indian Computer Emergency Response Team, issued Directions under sub-section (6) of section 70B of the Information Technology Act, 2000, dated 28 April 2022. Paragraph (ii) says that any service provider, intermediary, data centre, body corporate and Government organisation “shall mandatorily report cyber incidents as mentioned in Annexure I to CERT-In within 6 hours of noticing such incidents or being brought to notice about such incidents.”

Annexure I lists the types of incident to be reported. Several match what happens when a business website is hacked:

  • “Defacement of website or intrusion into a website and unauthorised changes such as inserting malicious code, links to external websites etc.”
  • “Unauthorised access of IT systems/data”
  • “Malicious code attacks such as spreading of virus/worm/Trojan/Bots/Spyware/Ransomware/Cryptominers”
  • “Attack on servers such as Database, Mail and DNS and network devices such as Routers”

CERT-In’s FAQs on the Directions (May 2022) add several points relevant to website owners:

  • Who is covered. The FAQs say individual citizens are not covered by the Directions. They explain “body corporate” by quoting section 43A of the IT Act: “any company and includes a firm, sole proprietorship or other association of individuals engaged in commercial or professional activities”.
  • When the clock starts. Asked about incidents that go undetected for a long time, the FAQs say the incident “needs to be reported to CERT-In within 6 hours of noticing the incident or being brought to notice about such incident.” The clock runs from when you notice the incident or are told about it, for example by a customer, your host or a Google notification, not from when the attacker first got in.
  • Incomplete information. If all the information asked for in CERT-In’s incident reporting form is not available within 6 hours, the FAQs say entities “may provide information to the extent available at the time of reporting” and report more later within a reasonable time. Not knowing the cause yet is therefore not a reason to wait for the full picture.
  • Incidents in third-party systems. The FAQs say the Directions apply to all entities as far as reporting is concerned, including incidents affecting their data stored in a third party’s systems, such as a hosting provider.

The same FAQ answer on incomplete information also lists criteria for incidents that “should be reported within the stipulated 6 hour time”. These include severe incidents on public information infrastructure, data breaches or data leaks, large-scale or most frequent incidents such as intrusion into websites, and incidents affecting human safety. Do not read that list as a published exemption for smaller incidents or as permission to report later: the Directions themselves set the 6-hour requirement for Annexure I incidents, and the FAQs do not state a different deadline for incidents outside those criteria. How the two documents fit together for your incident is exactly the kind of question to put to your lawyer.

The Directions list the reporting channels as email to incident@cert-in.org.in, phone 1800-11-4949 and fax 1800-11-6969. They say reporting methods and formats are published on CERT-In’s website. Before you need them, put these details and your legal contact in your incident plan. During an incident, record in your log when the incident was noticed, what advice you received, what was reported, when, and any reference number.

If customer personal data such as enquiry form entries, accounts or orders may have been exposed, there may be separate legal duties under data protection law. Ask your lawyer to cover that as a separate question rather than assuming the CERT-In report covers it.

Decide how to recover: clean, restore or rebuild

Once the site is contained and evidence preserved, the main technical decision is how to get back to a clean state. There are three broad routes, and the right one depends on facts your technical team can establish.

RouteWhen it tends to fitMain riskQuestions to ask
Restore a clean backup, then patchA backup exists from before the compromise began, and the weakness can be identified and fixedThe backup may already contain the infection or the vulnerable plugin; changes made since the backup are lostWhen did the compromise start? Has the backup been checked? What will be patched before going live?
Clean the existing siteNo reliable clean backup, but the site is current and the infection is understoodA missed backdoor allows reinfectionWhich files and database tables were checked? How was the entry point found?
Rebuild on a fresh install, reusing checked contentThe site is old, heavily modified, full of abandoned or pirated plugins, or repeatedly reinfectedTime and cost; content and settings must be moved carefullyWhich content can be safely exported? What will be dropped?

WordPress’s FAQ gives a few principles that apply whichever route you choose:

  • Core directories /wp-admin and /wp-includes can be replaced with fresh copies of the same WordPress version. Use the same version to avoid breaking the site.
  • Do not rely on the dashboard’s reinstall options for cleanup. They may only overwrite existing files, and hacks often add new files. Upload clean copies instead.
  • Treat wp-content, which holds themes, plugins and uploads, with more care, replacing theme and plugin files from trusted sources.
  • Check .htaccess, which is commonly modified in infections and can exist in several directories, and common template files such as index.php, header.php, footer.php and functions.php.

Two traps deserve emphasis. First, a backup is only clean if it predates the compromise, and spam injections are often present for some time before anyone notices. Ask for evidence of when the first malicious change happened before trusting a restore point. Second, cleaning without finding the entry point usually fails. The WordPress FAQ describes forensics as understanding how attackers got in so they cannot use the same route again. Common causes include outdated plugins or themes, pirated “nulled” plugins, reused or weak passwords and compromised local computers, but the cause on your site has to be established from evidence, not assumed.

Finish the cleanup properly before asking Google to review

After cleanup, WordPress recommends updating WordPress to the latest version, because older versions are more prone to attack, and changing all passwords again. Passwords changed during the incident may have been captured if the attacker still had access. Consider changing the database user password too, and remember to update wp-config.php when you do.

Before requesting any review, confirm:

  • All issue types are fixed. Google’s help says to fix every issue listed and to fix it across the whole site. Fixing only the sample pages does not earn a partial return to search results.
  • Spam pages are gone. URLs created by the attacker should no longer serve content. Ask your developer how they will respond, typically as not found, rather than redirecting them to your homepage.
  • The site is accessible. Google’s request a review guidance lists prerequisites: ownership verified in Search Console, the site cleaned, the vulnerability corrected and the clean site back online. It also notes that pages must be crawlable by Googlebot, so they should not be blocked by robots rules or noindex when Google checks them.
  • Accounts are clean. Unknown WordPress users removed, application passwords and API keys reviewed, hosting and FTP users checked, and Search Console owners reviewed for anyone you do not recognise.
  • Your own fetches look clean. Ask the developer to fetch the homepage and previously affected URLs from the command line and through URL Inspection, since cloaked spam may show only to search engines.

If Search Console is not set up, verify the site now. Google’s help also covers the case where you have just bought a site with existing security issues: fix the issues, then say in the request that you recently acquired the site.

Write the review request

When everything is fixed, open the Security issues report and select Request Review. Google’s help says a good request explains the exact issue, describes the steps taken to fix it, and documents the outcome. Google’s request a review guidance suggests a brief explanation for each category of issue, such as removing spam content and fixing the vulnerability by updating an out-of-date plugin.

Use your incident log to fill in this outline:

Issue: [The exact issue types shown in the Security issues report, for example content injection and URL injection.]

Cause: [The entry point found, for example an outdated plugin, a compromised admin password, or “not conclusively identified; the following controls were added”.]

What was fixed: [Files replaced or cleaned, database entries removed, spam URLs removed, unknown users deleted, passwords and keys rotated, software updated.]

Result: [Checks performed after cleanup and what they showed.]

Keep it factual. Do not claim the cause was found if it was not, and do not send the request before the cleanup is finished.

Then wait. Google’s help says reviews can take several days or weeks and that you will be emailed when the request is received and when the review is complete. Do not resubmit before you receive a decision: submitting while the problem remains can lengthen the next review or lead to a site being treated as a repeat offender. Google’s request a review guidance gives indicative times by issue type, from about a day for phishing to up to several weeks for sites hacked with spam, and says that once Google finds a site clean, warnings in browsers and search results are removed within 72 hours. If the review fails, the report may show more sample URLs for the next round.

Also note the difference between reports. Google’s help explains that the Manual Actions report covers mostly attempts to manipulate the search index, while the Security issues report covers hacking and behaviour that could harm visitors. A hacked site can have entries in either or both, and each is fixed and reviewed through its own report.

Communicate with customers, staff and partners

A hacked site is a trust issue as well as a technical one. Decide early who needs to hear what:

  • Staff who answer phones, email or WhatsApp. Give them a short, accurate line: the website has a technical security problem, it is being fixed, and customers should not enter information on the site until it is resolved. Tell them which channel to use for orders or enquiries meanwhile.
  • Customers who reported the problem. Thank them and tell them what to avoid. If visitors may have been sent to malicious pages, advise anyone who entered information to change their passwords.
  • Payment and service partners. If checkout pages, payment integrations or forms were affected, tell your payment provider and any service whose keys may have been exposed, and rotate those keys.
  • Email recipients. WordPress notes that compromised sites are often used to send spam, which can get server IP addresses blocklisted, affecting email that shares the server. If email is affected, involve your email provider.

Avoid speculating about cause or scale before you know. A brief, accurate message now and a fuller update after cleanup are better than an early message that has to be withdrawn.

Hypothetical example: the spam pages nobody could see

This is a hypothetical example for illustration, not a real case.

A Kolkata furniture showroom’s site was built three years ago and has not been updated since. A customer sends a screenshot of the showroom’s search result labelled “This site may be hacked”. The owner opens the homepage and it looks normal.

The owner names the office manager as incident lead and starts a log. Search Console shows URL injection with sample URLs full of foreign-language product spam. The host confirms unusual file changes and provides access logs. The developer takes a full copy before changing anything.

The owner calls the business’s lawyer about the CERT-In Directions the same day, follows that advice, and records the time the incident was noticed, the advice received and what was reported in the log. The developer finds an outdated form plugin with a published vulnerability in the logs around the time of the first modified file. The only backup on the hosting account is a week old and already contains the spam, so they clean the existing site, replace core files, reinstall plugins from official sources, remove the vulnerable plugin, delete two unknown admin users and rotate all passwords and keys.

After checking that spam URLs no longer serve content and that the site is crawlable, they request a review describing the URL injection, the plugin, the steps taken and the checks done. They do not resubmit while waiting and add regular updates and off-site backups to the maintenance arrangements.

Hypothetical example: when rebuilding is the better route

This is a hypothetical example for illustration, not a real case.

A consultancy’s WordPress site has been cleaned twice in a year and reinfected each time. It uses a pirated premium theme, a dozen plugins without updates and an unsupported PHP version. Nobody can say with confidence what is clean.

The incident lead asks the three route questions. A restore is unattractive because no backup is known to be clean. Cleaning has already failed twice. The site is small, about thirty pages, and most content can be exported and checked. The business decides to rebuild on a fresh install with a licensed theme and a short plugin list, moving content manually after review. The old site stays in maintenance mode until the new one is ready; URL structure is kept where possible and any changes are handled with redirects, following the principles in the website migration checklist.

Reduce the chance of a repeat

Once recovered, treat the incident as a prompt to fix the conditions that allowed it. The security and backups guide covers prevention layers and backup planning in more depth. WordPress’s FAQ ends its hacked-site guidance with securing the site, and its recovery steps point to the main areas:

  • Keep software updated. WordPress, themes, plugins and the server’s PHP version all need updating. Remove plugins and themes you do not use.
  • Use only legitimate software. Avoid pirated themes and plugins. Prefer actively maintained plugins from trusted sources.
  • Strong, unique passwords and two-factor login. WordPress recommends long, unique passwords from a password manager and considering two-factor authentication.
  • Least privilege. Give each person the lowest WordPress role that lets them do their job, and remove accounts for people who have left.
  • Regular, tested, off-site backups. WordPress describes backups as critical to continuity and suggests asking your host about their backup policy. Keep enough history to go back before an undetected compromise, store copies away from the server, and test restores.
  • Monitoring. Keep Search Console verified with alerts going to someone who reads them, and consider uptime and file-change monitoring.
  • Choose hosting with the response in mind. Ask hosts what malware scanning, isolation and support they provide and what is extra. The guides on cheap WordPress hosting in India and comparing WordPress hosting discuss what support usually covers.
  • Write down responsibilities. If an agency or freelancer maintains the site, agree in writing who handles updates, backups, monitoring and incident response, and how quickly.

Worksheet: incident brief for your developer or host

Fill this in and send it when you ask for help. It saves time and reduces guesswork.

ItemYour answer
Website URL and platform (for example WordPress version if known)
Hosting provider and plan type
Who controls hosting, domain, WordPress admin and Search Console
First symptom, who noticed it, date and time (IST)
Security issues report entries and sample URLs
Recent changes (plugins, themes, users, hosting)
Backups available, their dates and where stored
Copy of current infected state taken? Where stored?
Customer data handled by the site (forms, accounts, orders, payments)
Time incident was noticed; legal advice received; CERT-In report time and reference (if made)
Business constraints (acceptable downtime, key pages, deadlines)

Frequently asked questions

Can I remove the “This site may be hacked” label without cleaning the site?

No. Google’s help page on the “This site may be hacked” message says the notification won’t be removed until the website owner takes action, and that Google removes it after checking the site is fixed following a review request in Search Console. Google’s Security issues help also says to fix the issues throughout the site before requesting a review. Requesting a review too early can slow the next review.

How long does recovery take?

The cleanup depends on the infection and the route chosen. The Google review depends on the issue type: Google’s guidance describes about a day for phishing, a few days for malware, and up to several weeks for spam hacks. Treat any promise of a guaranteed timeline with caution.

Is restoring a backup enough?

Only if the backup predates the compromise and the weakness that let the attacker in is fixed before going live. Otherwise you may restore the same vulnerability or the infection itself.

Do small businesses have to report to CERT-In?

CERT-In’s Directions require service providers, intermediaries, data centres, body corporate and Government organisations to report the incidents listed in Annexure I within 6 hours of noticing them or being told about them. Website intrusion and unauthorised changes to a website are on that list. CERT-In’s FAQs explain “body corporate” to include firms and sole proprietorships engaged in commercial or professional activities, and say individual citizens are not covered. This is general information; get legal advice on your own situation promptly.

Should I use the Removals tool to hide the spam pages?

Removing the spam from your site, fixing the entry point and requesting a review come first. Google’s Removals tool help says the tool temporarily blocks pages on sites you own from Google Search results. A successful request lasts only about six months, and blocking does not stop Google from crawling the page, so further steps are needed to remove a URL permanently. Ask your developer whether it helps in your case; it is not a fix for the hack.

Can I clean the site myself?

Google’s help notes that fixing malware requires the ability to read code and possibly server configuration, and suggests getting help if that is beyond your comfort zone. Owners can usually handle the log, containment decisions, account checks, communication and the review request, and should bring in a professional for file and database cleanup and finding the entry point.

Summary

A hacked website needs an incident lead, a written log and a clear order of work. Confirm the issue type in Search Console without opening infected pages in a browser. Keep a copy of the infected state, involve your host and lock down every access point. Check the CERT-In reporting requirement straight away, with prompt legal advice, because the Directions set a 6-hour window from when the incident is noticed. Choose between restoring, cleaning and rebuilding based on evidence about when the compromise started and how it happened. Fix everything across the whole site, request a single review with a factual description, wait for the decision, and then fix the conditions that made the attack possible.

Website security service profile: our Business Listing directory has a profile of Sucuri, a website security service. It is a profile, not a recommendation for your specific incident, and some directory links are partner links. Ask your host or developer which route fits your case.

References

  1. Google Search Console Help, “Security issues report”: https://support.google.com/webmasters/answer/9044101
  2. WordPress Documentation, “FAQ My site was hacked”: https://wordpress.org/documentation/article/faq-my-site-was-hacked/
  3. CERT-In, Directions under section 70B(6) of the IT Act, 2000 (28 April 2022): https://www.cert-in.org.in/PDF/CERT-In_Directions_70B_28.04.2022.pdf

Leave a Reply

Share Your Love