How to Check If Your Web App Is Hacked: Signs of Compromise

Check your own app — free, in about a minute.

The free mini-scan checks your live homepage for TLS/HTTPS basics, response security headers, cookie flags, exposed sensitive files, Firebase/Supabase backend rules, and the WordPress plugin versions your site exposes. You get a score and the finding titles — no account, no card.

Run the free mini-scan →

How to Check If Your Web App Is Hacked: Signs of Compromise for Founders

You're not a security analyst — you're a founder who shipped an app and now something feels off. Maybe a user reported something weird. Maybe traffic looks strange. Maybe you just have a bad feeling. This article is the practical version of incident response: the signs that actually indicate compromise (versus normal weirdness), how to check each one, and what to do in the first hour if the answer is yes.

One honest note up front: no outside-in checklist can prove you haven't been hacked — absence of signs isn't proof of safety. But the signs below are how real compromises surface, and checking them is the fastest way to go from "bad feeling" to "known answer."

The Signs, in Rough Order of How Often They Show Up

1. Content on your site you didn't put there

The most common visible sign: pages, links, or redirects that aren't yours. Classic patterns include:

Check: Open your site in an incognito window and click around as a stranger. Then check what search engines see: site:yourdomain.com in Google, and fetch a few pages with curl using a Googlebot-style user agent — some injections only show to crawlers:

curl -s -A "Mozilla/5.0 (compatible; Googlebot/2.1)" https://yourdomain.com/ | grep -oiE '<a[^>]*href="[^"]*"' | head -30

Compare the links against what you expect. Anything unfamiliar is a red flag.

2. Files changed that you didn't change

If attackers got write access, they left files. Check for:

Check: If you deploy from git, git status on the server should be clean — any modified or untracked file in the web root is suspicious. In your database, list users created in the last 30 days and eyeball every one.

3. Your app is doing things you didn't ask it to

4. Users report the classic symptoms

Take every one of these seriously and check the corresponding sign above. Users notice compromise before dashboards do.

5. The quiet technical indicators

These don't prove compromise on their own, but they're how attackers get in — and finding them tells you where to look:

for p in /.env /.git/HEAD /debug /admin /api/debug; do
  echo "$p -> $(curl -s -o /dev/null -w '%{http_code}' https://yourdomain.com$p)"
done

What To Do in the First Hour (If You Find Something)

Don't panic, don't start deleting things yet — preserve evidence first, then contain.

  1. Take a snapshot. Back up the current state (files, database, logs) before you change anything. You'll need it to understand what happened, and deleting the attacker's files destroys your best evidence.
  2. Contain. Put the app in maintenance mode or take it offline. If email is being abused, pause sending. If you can, block the attacker's access (rotate credentials, disable the unknown accounts) without yet wiping the machine.
  3. Rotate everything. Every API key, every database password, every OAuth token, every session secret — assume all credentials the app touched are known to the attacker. This is the step people skip and regret.
  4. Find the entry point. Check access logs for the timeframe of the first suspicious change: look for requests to /.env, /.git, admin paths, and unusual POST requests. The entry point tells you what to fix so it doesn't happen again.
  5. Rebuild clean. Restore from a backup you trust predates the compromise — or redeploy from a clean git state — then re-apply the credential rotations. Patch the hole (the missing auth check, the exposed file, the unpatched dependency) before going back online.
  6. Tell affected users. If user data may have been accessed, say so plainly and quickly: what happened, what you're doing, what they should do (change passwords, watch for phishing). Hiding it is worse than the breach.

If the compromise involves customer data, payment information, or you're unsure about legal obligations — talk to a lawyer, not a blog post. Breach notification laws vary by jurisdiction and data type.

After the Incident: Don't Just Restore — Harden

Most compromised apps get compromised again through the same hole. Before you go back online, run the pre-ship verification pass: secrets out of the frontend bundle and git history, auth checks on every API endpoint, database access policies verified, /.env and debug routes gone, security headers present, rate limiting on auth. The incident told you which check you skipped — make it the one you never skip again.

A Note on What an Outside Scan Can and Can't Tell You

An outside-in scan — which is what PreShipIt does — shows you what an unauthenticated visitor can see and reach: exposed files, missing headers, open endpoints, weak TLS. That's exactly the attack surface a compromise starts from, and it's worth checking regularly. But it can't see inside: it can't tell you whether files were modified last Tuesday, whether a rogue admin account exists, or whether your database was already read. If you suspect an active compromise, you need incident response — logs, snapshots, and credential rotation — not a scan. Run the checks in this article first; they're the ones that answer "am I hacked."

And if the answer turns out to be "not hacked, just exposed" — that's the best possible outcome, and the cheapest time to fix it. A $29 outside-in scan before launch is a lot cheaper than the first hour described above.

Check what strangers can see at preshipit.com — paste your URL, attest you own the app, and get a plain-English prioritized report of your actual exposure.

The PreShipIt Brief — a short weekly email for people shipping vibe-coded apps: the week's important vulnerabilities and launch-safety checks, in plain English.

New and free. Double opt-in: we email you a confirmation link before anything else arrives. Unsubscribe any time.

Check your own app — free, in about a minute.

The free mini-scan checks your live homepage for TLS/HTTPS basics, response security headers, cookie flags, exposed sensitive files, Firebase/Supabase backend rules, and the WordPress plugin versions your site exposes. You get a score and the finding titles — no account, no card.

Run the free mini-scan →

← Back home · Run a free mini-scan · Scan my app — $29 · See a sample report