Website Says Your iPhone Is Hacked: Real?
If a website says your iPhone or phone is hacked, it is almost certainly a scam pop-up trying to scare you into tapping, calling or installing something. It is not a real alert from Apple or Google.
This post is for two groups: people who just saw a scary message in their browser, and site owners who want to know if their own site is showing it to visitors. You will get a plain explanation of why these alerts exist, a straight answer on whether a website visit alone can hack you, short step lists for iPhone and Android, and a way to check your own site.
Why a website says your iPhone is hacked
These messages are a type of scam called scareware. The page uses ordinary web code (JavaScript) to draw a loud warning. Common versions say "Your iPhone has been hacked", "3 viruses found" or "Your battery is damaged".
The goal is never to protect you. It is to get you to do one of these things:
- Call a fake "support" phone number.
- Install an app or profile you do not need.
- Pay for a pointless "cleaner" or "antivirus".
- Allow notifications on Android and desktop Chrome, so the site can keep sending scary alerts. On iPhone, regular Safari tabs cannot receive web push notifications, so the equivalent trick is a subscribed calendar.
- Enter your Apple ID, card or other details.
The FTC explains how tech support scams work. CISA also covers the pressure tactics in its guide on avoiding social engineering and phishing attacks.
Real warning or scam? A quick comparison
| What you see | Likely meaning |
|---|---|
| A pop-up inside a web page with a countdown, sirens or a phone number | Scam |
| Text that says "Apple", "Google" or "Microsoft" has detected a virus | Scam. These companies do not warn you through random web pages |
| A page you cannot close, or one that keeps reopening | Scam (a browser trick, not an infection) |
| A request to install a "cleaner" or "security" app | Scam |
| Safari or Chrome showing a full-page red warning before a site loads, such as "Deceptive website warning" or "Dangerous site" | Real browser protection. Go back and do not continue |
| An alert in Settings from Apple about your Apple ID or a software update | Real. Open Settings yourself, do not tap links in messages |
A useful rule: a real warning comes from your device or browser, not from inside a web page. The page cannot scan your phone. It has no permission to look at your files or apps.
Can I get hacked by going to a website?
Usually no. A normal web page runs inside a sandbox (a locked box) in your browser. It cannot read your photos, messages or other apps.
A visit alone can cause harm in rare cases. That needs a security flaw in your browser or operating system that has not been patched yet. Vendors fix such flaws in updates, which is why Apple's security releases matter. These attacks are uncommon and usually aimed at specific targets.
The common risks are different. They come from what you do after the page loads:
- Tapping "Allow" on a notification request (on Android and desktop Chrome). On iPhone, regular Safari tabs cannot receive web push notifications, so the equivalent trick is a subscribed calendar.
- Installing an app, profile or extension the page pushes.
- Calling the number and letting someone "fix" the phone.
- Typing your password or card into a fake page.
So the scary message itself is usually harmless. Your reaction is what the scammer needs.
What to do on iPhone
- Do not tap, call or install anything. Do not call any number on the page.
- Close Safari. Swipe up from the bottom (or double-press Home), then swipe the Safari card away.
- Reopen Safari. If the page returns, tap the tabs button and close all tabs.
- Clear website data. Go to Settings > Apps > Safari > Clear History and Website Data. On iOS 17 and older, it is Settings > Safari.
- Check for fake calendar invites. Some scams add a subscribed calendar that sends alerts. Open Calendar, tap Calendars, then check for subscriptions you do not recognize and delete them. You can also check Settings > Apps > Calendar > Calendar Accounts > Subscribed Calendars. On iOS 17 and older, it is Settings > Calendar > Accounts.
- Remove unknown profiles. Go to Settings > General > VPN & Device Management. Delete any profile you did not install on purpose.
- Update iOS. Go to Settings > General > Software Update.
- If you typed a password, change it right away on the real site, and turn on two-factor authentication.
Also check that Safari's Block Pop-ups and Fraudulent Website Warning options are on, in Safari settings.
What to do on Android
- Do not tap the pop-up. Do not call the number or install anything.
- Close the tab. In Chrome, tap the tab button and close it. If the page blocks you, close Chrome from the recent apps screen.
- Stop notification spam. In Chrome, go to Settings > Notifications > Site settings (or Settings > Site settings > Notifications) and remove sites you do not know.
- Clear browsing data. Go to Chrome > Settings > Privacy and security > Delete browsing data.
- Check recent installs. Go to Settings > Apps and look for apps you did not choose. Uninstall them.
- Run Google Play Protect. Open the Play Store, tap your profile picture, then Play Protect > Scan.
- Update Android and Chrome. Open Settings and look for System update or Software update (the exact path depends on your phone brand). Update Chrome in the Play Store.
If you gave someone remote access or paid, contact your bank at once. Then change the passwords for your email and bank first.
Why you saw it on a normal website
Often the site you visited did nothing wrong on purpose. Common causes:
- A bad ad. Ad networks sometimes serve malicious ads that redirect the page.
- A hacked website. An attacker planted code that redirects some visitors.
- A compromised plugin or theme on a WordPress or Shopify-style site.
- A third-party script (chat, analytics, widgets) that was tampered with.
If you own the site, this matters. Your visitors may see a scam page while you never do.
Site owners: is your site showing these pop-ups?
These redirects are often sneaky. They may only fire for mobile visitors, for people who arrive from Google, or for first-time visitors. You can look fine while customers do not.
1. Test like a visitor. Use a phone on mobile data, not your office Wi-Fi. Open your site from a Google search result, not by typing the address.
2. Check redirects from the command line. This sends a mobile browser identity and a Google referrer (the page you came from). It uses a normal GET request (a regular page load), not a HEAD request (headers only), because injected redirects often fire only on GET. It prints the response headers for every hop, then the final address. Swap in your domain:
curl -sL -o /dev/null -D - -w '%{url_effective}\n' -A 'Mozilla/5.0 (iPhone; CPU iPhone OS 17_0 like Mac OS X) AppleWebKit/605.1.15 (KHTML, like Gecko) Version/17.0 Mobile/15E148 Safari/604.1' -e 'https://www.google.com/' https://example.com
Look at every Location: line, and at the final address on the last line. If your site sends people to a domain you do not recognize, treat that as a problem.
This only catches server-side redirects. Redirects done in JavaScript, or served only by certain ads or scripts, will not show up here. Note: curl does not run JavaScript, and many injected redirects are JavaScript or only fire for real browsers, so a clean result does not prove your site is clean. Avoid curl -I for this check, because it sends a HEAD request and some servers answer that differently from a normal visit. Also test on a real phone (step 1) and inspect the page source (step 3).
3. Look for odd code. In your page source, search for <script src= pointing at unfamiliar domains. Check ad, chat and tag-manager scripts too.
4. On WordPress, verify your files. If you have shell access and WP-CLI, run:
wp core verify-checksums
wp plugin verify-checksums --all
These compare files to the official copies and flag files that were changed, but only in limited places. wp core verify-checksums covers WordPress core only. wp plugin verify-checksums --all works only for plugins hosted on WordPress.org. Premium or custom plugins and themes are skipped, so a pass does not cover them. Neither command checks themes, uploads or the database. Many redirect injections live in the database (for example in posts or the wp_options table), so a pass does not prove your site is clean. You can also scan with a free tool such as Sucuri SiteCheck or the Wordfence plugin.
5. Check Google's view. In Google Search Console, open the Security issues report. It tells you if Google flagged your site.
6. Limit which scripts can run. A Content Security Policy (CSP) is a header that tells browsers which sources may run scripts on your pages. Start in report-only mode so nothing breaks. Send these two headers together:
Reporting-Endpoints: csp-endpoint="https://your-report-endpoint.example/csp"
Content-Security-Policy-Report-Only: default-src 'self'; script-src 'self' https://trusted.example; report-to csp-endpoint
Report-only mode needs a reporting target. Add a report-to endpoint (as above) or the older ; report-uri https://your-report-endpoint.example/csp directive if you want to collect violation reports from visitors. Without one, violations only show in the browser's developer console, so you would have to open your own site with the console open to see what would be blocked.
CSP limits which scripts load. It will not stop a malicious ad network or a script you have allowed from redirecting the page, so treat it as one layer, not a fix for this problem.
OWASP has a good CSP cheat sheet. To see which headers you already send, try the security headers tool.
If you find injected code, do not just delete it. Change all admin, hosting and database passwords, update everything, and find how the attacker got in, or they will return. Our website hacked guide walks through that.
Where a human audit helps
A free scan can spot some signs. It cannot tell you how someone got in, or whether other weak spots exist. You can start with the free website security check, which looks at your domain from the outside. Our guide on whether your website is hackable explains what a deeper test looks at.
Key takeaways
- A page saying your iPhone or phone is hacked is almost always a scareware scam, not a real alert.
- Do not call numbers, install apps or enter passwords. Close the tab, clear website data and check for unknown profiles or calendar subscriptions.
- A web page alone rarely hacks a device. Keep iOS, Android and your browser updated.
- If you own a site, test it on a phone from a Google search, check redirects and scripts, and verify WordPress files.
- If you find a redirect, fix the entry point, not just the symptom, and rotate your passwords.
Next step
If you want a person to test your site and explain what could let an attacker in, a Bug Circuit audit is $49 one-time for one website. It is a manual small-site test with a written report and fix steps. It is not a compliance certificate or a multi-week enterprise test, and it does not monitor your site afterward. Fixes are quoted separately, and you pay only if you agree. See the details on the pricing page.
A real human security engineer audits your whole site by hand and sends a full report: every issue, its severity, and the exact fix. From $49, with a 14-day money-back guarantee.
See pricing