Blog / How the internet works /
Phishing pages hosted on real websites
The old advice for spotting phishing was: look at the web address. If it says paypa1-secure-login.xyz, run. That advice is still useful, but it’s no longer enough, because a growing share of phishing pages sit on perfectly respectable domains.
The link might go to a small business’s WordPress site, a school’s page, a well-known document-sharing service or a free website builder. The padlock is there. The domain has existed for years. And the page asks for your password.
This post covers two angles: how to avoid being fooled, and, for site owners, how to make sure your own site isn’t quietly being used.
Why attackers use real websites
- Trust. Email filters and people both trust an older domain more than a brand-new one.
- Cheap. Hacking a poorly maintained site costs less than buying and warming up a domain.
- Harder to block. Blocking a whole legitimate domain would also block its real content, so security tools hesitate.
- Takedown is slow. The owner often doesn’t know. The page can live for weeks.
Where phishing pages hide
- Hacked WordPress and other CMS sites. The attacker uploads a folder with fake login pages deep inside the site, for example under
wp-content/uploads/or a random folder name. The main site looks normal, so no one notices. - Free hosting and site builders. Anyone can create a page on a free service, with a trusted domain name.
- Cloud file and form tools. Shared documents, forms and presentations used as “you have a file waiting” lures. The link points to a real service, and the form inside collects your details.
- Code and page hosting platforms. Static hosting services, developer platforms and storage buckets are sometimes misused to host fake pages.
- Open redirects. A legitimate site has a link feature that forwards visitors to any address. Attackers use it so the first part of the link looks genuine, then bounce the visitor to the fake page.
- Hijacked subdomains. A forgotten subdomain pointing at a service the owner no longer uses can be taken over. See domain expiry and DNS hijacking for how to keep your DNS tidy.
How to avoid being fooled
A trusted domain doesn’t make a page trustworthy. Build habits that don’t depend on the address alone.
- Don’t log in from an email link. Open the site yourself, by typing the address or using your bookmark, and look for the notification there.
- Ask what the page wants. A shared document that asks you to “sign in again with your email password” is wrong. Real services rarely need that.
- Be suspicious of urgency. “Your account closes in 24 hours” is the oldest trick.
- Check the whole address, not only the first part. A real domain followed by a long odd path, or a login form on a page that seems unrelated to the company, is a flag.
- Use a password manager. It fills credentials only on the exact domain you saved them for. If it doesn’t offer your login, stop and ask why.
- Use passkeys or two-factor authentication. Passkeys are bound to the real site, so they resist phishing by design. See passkeys explained and two-factor authentication compared. Text-message codes are the weakest of the options.
- Report it. Most email providers and browsers have a “report phishing” option.
For a wider look at scam messages on phones, phone scams: the messages and calls to ignore is a good companion.
If you own a website: is yours hosting one?
This is the part many owners miss. If your site is hacked, you may not see a defaced home page. The attackers prefer to stay hidden and let the phishing page do its work.
Warning signs:
- Google Search Console shows a “Security issues” warning, or Chrome shows a red “Deceptive site ahead” page for your domain. I covered the reports in the security issues and manual actions reports in Search Console.
- Your host emails you about malicious files.
- Strange files or folders that you didn’t create, particularly in uploads, theme or plugin folders. Names like
login,secure,verifyor a bank’s name are suspicious. - Unexpected URLs in your logs getting traffic, especially pages ending in
.phpor.htmlthat you don’t recognise. - Spikes in traffic to a single odd address.
- Your site is blocklisted or your email suddenly lands in spam.
My earlier post on monitoring website changes you didn’t make describes ways to catch unexpected file changes early.
What to do if you find one
- Don’t just delete the page. If the attacker got in, they probably left a way back. Deleting the visible file isn’t the fix.
- Take a backup of the current state for investigation, then restore a clean copy from before the compromise if you can.
- Change all passwords: hosting, database, WordPress admin, FTP, email. Add two-factor authentication.
- Update everything: core, themes and plugins. Remove anything abandoned.
- Scan files with a reputable security plugin or your host’s scanner, and check for unknown admin users.
- Close the hole. Find how they got in, typically an outdated plugin or a weak password.
- Ask for a review through Search Console and your browser’s blocklist service once it’s clean.
- Tell your host and, if people may have been affected, say so openly.
Prevention that works
Nothing exotic. The same basics as in WordPress security basics every site owner should know and website security basics: five things that stop most attacks:
- Keep core, themes and plugins updated, and delete what you don’t use.
- Use strong, unique passwords and two-factor authentication.
- Limit admin users and file permissions.
- Use a firewall and, where possible, block PHP execution in the uploads folder.
- Keep off-site backups, and test them.
- Monitor file changes and security alerts.
Myths
- “The padlock means it’s safe.” It means the connection is encrypted. Phishers get certificates too. See HTTPS and the padlock.
- “My site is too small to be targeted.” Small, neglected sites are exactly what attackers want.
- “I’d notice if I was hacked.” Phishing pages are built to stay unnoticed.
Key takeaways
- Phishing increasingly lives on legitimate domains, so the address alone isn’t proof.
- Don’t log in from email links; use bookmarks, password managers and passkeys.
- Site owners should watch for hidden files, security warnings and odd URLs.
- If you find a phishing page, clean the whole site, not just the one file.
Related reading
When did you last look at the file list in your site’s uploads folder?