Skip to main content

Insights

Signs Your Website Has Been Hacked

Many website compromises are designed to stay hidden. Learn the visible and less obvious signs of a hacked website and what to do if you spot them.

Published
Updated
Reading time
7 min read
Site cleanedRoot cause fixed

When people imagine a hacked website, they often picture a defaced homepage with a message from the attacker. That does happen, but it is now the exception. Most compromises of business websites are designed to stay hidden for as long as possible, because a hidden compromise is more valuable to the attacker. It can quietly send spam, redirect a share of visitors to scam sites, host phishing pages, skim payment details or boost someone else's search rankings.

That means the owner of a compromised site is often the last to know. The first sign might be a customer complaining about a strange redirect, a warning in Google Search Console, an email from the hosting company or a sudden drop in search traffic. By then the compromise may have been in place for weeks.

This article covers the most common signs that a website has been hacked, from the obvious to the subtle, and explains what to do – and what not to do – if you suspect a problem.

Visible signs visitors may notice

These symptoms affect what people see when they visit your site.

Unexpected redirects

Visitors are sent to another website – often a gambling, pharmaceutical, adult or fake prize site. Redirect malware is frequently conditional: it may only trigger for mobile users, for visitors arriving from search engines, or on a first visit. That is why you may not see it yourself when you type the address directly while logged in. If customers report redirects you cannot reproduce, take the report seriously.

Browser or search engine warnings

Chrome, Firefox and Safari use Google Safe Browsing and similar services to warn users away from sites flagged as dangerous. A full-page red warning, or a "This site may be hacked" note in search results, is a strong sign that something malicious has been detected on your site.

Spam content and strange pages

Search for your domain with the site: operator in Google (for example, site:yourdomain.com) and look for pages you did not create – often in foreign languages, or about pharmaceuticals, replica goods or loans. These are typically injected so that attackers can exploit your domain's reputation in search results.

Defacement or unexpected pop-ups

Changed content, unfamiliar pop-ups, fake browser update prompts or new script-driven overlays can indicate injected code. Fake "update your browser" prompts are a known technique for distributing malware to visitors.

Signs in your search and analytics data

Some symptoms only appear in the tools you use to monitor your site.

  • Security issues or manual actions in Google Search Console. Google notifies site owners when it detects malware, hacked content or spam.
  • A sudden spike in indexed pages. Thousands of new URLs appearing in the index often indicates spam pages.
  • Sudden drops in organic traffic. This can follow search engines detecting hacked content and demoting or flagging the site.
  • Unusual traffic sources or landing pages. Referral spikes from unfamiliar sites or landing pages that do not exist in your CMS deserve investigation.
  • Search snippets in another language. If your titles and descriptions in search results have been replaced with spam text, cloaking malware may be showing search engines different content than humans.

Signs on the server and in the CMS

These require admin or hosting access, and they are often the most reliable indicators.

New or modified user accounts

Unfamiliar administrator accounts – sometimes with plausible names such as "admin2", "support" or "wpadmin" – are a classic sign of persistent access. Check user lists regularly and investigate any account that nobody can account for.

Unfamiliar or recently modified files

Look for PHP files in upload directories (where only images and documents should exist), files with random or misleading names, recently modified core files and obfuscated code using functions such as eval, base64_decode or gzinflate in unusual places. File integrity monitoring, which compares files against known-good versions, makes these changes far easier to spot.

Suspicious scheduled tasks and database entries

Attackers often add cron jobs or database entries that re-infect the site after it is cleaned. In WordPress, injected JavaScript is frequently found in the options table, in post content or in widget settings rather than in files.

Unusual resource usage

A site that suddenly uses far more CPU, memory, bandwidth or disk space than normal may be running malicious scripts, sending spam or hosting files for others. Hosting companies sometimes suspend accounts for this reason.

Signs in email and hosting communications

  • Your domain's emails start landing in spam or bouncing, because your server has been used to send spam and has been added to blocklists.
  • Your host sends abuse notices or suspends the account for malware, phishing or excessive resource use.
  • Customers report phishing emails that appear to come from your domain, or phishing pages hosted on it.
  • Password reset emails arrive for accounts you did not try to access, indicating someone is attempting to gain access.

Signs on e-commerce sites

Online stores face additional, particularly damaging risks.

SignWhat it may indicate
Customers report fraudulent card use after buying from youPayment skimming script on checkout pages
Unfamiliar JavaScript loaded on checkout from an unknown domainInjected skimmer collecting form data
Changes to payment gateway settings you did not makePayments being diverted or intercepted
New admin users or API keys in the store backendPersistent unauthorised access
Orders with unusual patterns, such as many low-value test transactionsCard testing using your checkout

If you see any of these on a store, treat it as urgent. Card data compromises can have contractual consequences with your payment provider under PCI DSS, and your payment provider and legal advisers should be involved. Our guide on how to protect a WooCommerce store covers preventive measures.

What to do if you think your site has been hacked

Acting quickly matters, but acting carefully matters more. Hasty actions can destroy evidence or leave backdoors in place.

  1. Do not just delete the obvious malicious file. Most compromises include more than one backdoor; removing only the visible symptom usually leads to reinfection.
  2. Take a snapshot of the current state – files, database and logs – before making changes, so the incident can be investigated.
  3. Change credentials for CMS admin accounts, hosting, FTP/SFTP, database and any API keys, from a clean device.
  4. Identify the entry point. Common causes include outdated plugins or themes, weak or reused passwords, compromised hosting accounts and nulled (pirated) premium plugins. If you do not close the entry point, the attacker can simply come back.
  5. Clean or restore. Either clean the site thoroughly, or restore from a backup known to predate the compromise – then apply all updates before going live.
  6. Request review. Once clean, request a review in Google Search Console and from any blocklists that flagged the site.
  7. Assess data exposure. If personal data may have been accessed, consider your obligations under GDPR or other applicable laws, and seek legal advice where needed.
  8. Harden and monitor. Update everything, remove unused components, enforce two-factor authentication and put ongoing security monitoring in place.

If the incident is serious or you are unsure, this is the point to involve specialists. Our malware detection and removal service focuses on finding the entry point and all persistence mechanisms, not just the visible symptoms, and emergency website support is available when the site is down or actively harming visitors.

Reducing the chance of it happening again

No site can be made unhackable, but the risk can be reduced substantially:

  • Keep CMS core, plugins, themes and the server runtime up to date. See what happens when you don't update WordPress.
  • Use unique, strong passwords and two-factor authentication for every admin account.
  • Remove unused plugins, themes and user accounts.
  • Use a web application firewall to filter common attacks.
  • Run regular malware scans and file integrity monitoring.
  • Keep tested, off-site backups with enough retention to go back before a hidden compromise began.

Conclusion

Most website compromises are quiet, so the signs are easy to miss unless someone is actively looking for them – in search results, analytics, user lists, files and logs. The earlier a compromise is detected, the smaller the damage and the simpler the recovery.

SupportSafe's security monitoring is designed to watch for these indicators continuously and alert on them early. If you are concerned about your site right now, request a free website health check, or contact us immediately if you are seeing active signs of compromise.

Frequently asked questions

Why can't I see the redirect my customers are reporting?
Redirect malware is often conditional. It may only trigger for mobile users, search engine visitors or first-time visitors, and it frequently hides from logged-in administrators. Test from a different device and network, and arrive via a search result.
Is restoring from a backup enough to fix a hacked website?
Only if the backup predates the compromise and you also close the entry point. Restoring without applying updates and changing credentials usually leads to reinfection.
Will a security plugin stop my site being hacked?
A security plugin helps, but it cannot fix outdated software, weak passwords or a compromised hosting account. It is one layer of protection alongside updates, access control, a firewall and monitoring.
Do I need to tell customers if my website was hacked?
It depends on whether personal data was affected and which laws apply to you, such as GDPR. Seek legal advice promptly; technical investigation can help establish what data may have been exposed.

SupportSafe Engineering Team

Maintenance, infrastructure and security engineers

Articles are written and technically reviewed by the SupportSafe engineers who carry out website, application and server maintenance for our clients. Each article is reviewed for accuracy before publication and updated when practices change.

Let's take responsibility for your technology.

Tell us what you run and what keeps you up at night. We'll assess it and recommend a maintenance plan that fits – with no obligation.