A dimly lit workstation with multiple screens

Clicked on a Phishing Link? Here Is What to Check.

By Thomas Lovas Lokoy · Published September 6, 2026 — researched and drafted with AI assistance from published sources; edited and published by NorwegianSpark SA.

The first thing to establish is which of two very different things happened, because most advice on this topic treats them as one.

You clicked a link and looked at a page. In the overwhelming majority of cases, on an updated device with a modern browser, nothing happened. A web page cannot silently install software on a patched system as a matter of routine. The click was the bait; the trap was further in.

You clicked, and then typed something, or opened something. A password, a card number, a verification code, a downloaded file you ran, a permission you approved. That is the event that matters, and everything below is about containing it.

If you only did the first, read the quick check and get on with your day. If you did the second, work down the list in order.

The ten-minute triage

What CISA says, and the part worth memorising

CISA's public guidance on recognising phishing lists the indicators that are worth committing to memory, quoted verbatim from its own page on 6 September 2026: "urgent or emotionally appealing language, especially messages that claim dire consequences for not responding immediately"; "requests to send personal and financial information"; "untrusted shortened URLs"; and lookalike addresses, "like amazan.com".

Its instruction for a message you have not acted on is short: "Delete the message. Don't reply or click on any attachment or link, including any 'unsubscribe' link. Just delete."

The first indicator is the one that identifies almost every campaign. Urgency is not a side effect of phishing; it is the mechanism. The message needs you to act before you check, because checking defeats it. If you notice nothing else, notice when a message is trying to make you hurry.

Judge the damage honestly

What you didRealistic exposureFirst move
Clicked, saw the page, closed itVery low on a patched deviceNothing beyond staying alert to follow-up messages
Entered an email address onlyLow; expect more targeted mailWatch for a follow-up that references it
Entered a passwordHigh for that account, and for every reuse of itChange it, then change every reuse
Entered a one-time codeAccount should be assumed takenChange password, sign out all sessions, audit recovery settings
Entered card detailsHighCall the issuer on the number on the card, ask for a replacement
Downloaded and ran a fileHigh, and device-wideFull scan, then change passwords from a different device
Approved an app or permission promptOngoing access until revokedRevoke it in the account's connected-apps page

The bottom two rows are the ones people underestimate. A file you ran can harvest saved passwords straight out of the browser, which is why the advice there is to change passwords from a different device — changing them on the compromised one hands the new ones over as you type them. And an approved OAuth permission survives a password change entirely; it has to be revoked separately in the account's own settings.

Report it, and why that is not pointless

In the United States, consumer fraud goes to the FTC at ReportFraud.ftc.gov, and cybercrime goes to the FBI's Internet Crime Complaint Center, which describes itself as "the central hub for reporting cyber-enabled crime". Elsewhere, your national cybercrime or fraud reporting body is the equivalent. If the message impersonated your employer, tell whoever handles IT there — a campaign that reached you reached others.

It feels futile at an individual level. It is not futile in aggregate: reporting is how a phishing domain gets taken down and how a pattern gets recognised. It costs two minutes.

The follow-up call, which is the part that actually empties accounts

Expect a second contact, and expect it to be the more convincing one.

Having your details from the form, an attacker often follows up by phone, posing as your bank's fraud team and warning about the suspicious activity they themselves caused. They may trigger a genuine verification code to your phone so that a real message arrives seconds before they ask you to read it back.

The rule, with no exceptions: an inbound request for a verification code is always fraudulent. No legitimate institution phones you and asks you to read one out. If a code arrives that you did not trigger, that is itself the alarm.

If you are ever unsure, hang up and call the number printed on your card or on your official statement — never a number given to you in the message or by the caller. The related threats are covered in smishing and scam texts, AI voice clone scams, and the wider picture in your password is on the dark web.

The counter-argument to panic

It is worth saying plainly, because the anxiety after a click is disproportionate to the risk in most cases: on a patched device with a modern browser, visiting a malicious page and leaving is usually a non-event. Drive-by installation without any interaction is rare and generally depends on an unpatched flaw. The industry's own advice about disconnecting from the internet immediately is sound for the "I ran a file" branch and largely theatre for the "I looked at a page" branch.

Which means the most valuable thing you can do after a click is not to scan frantically. It is to establish honestly what you typed. That single question determines whether this was a nothing or a something, and the whole of the response follows from it.

The prevention side, for next time, is in how to spot and avoid phishing, and moving to passkeys removes the phishable secret altogether on the accounts that support them. Endpoint protection covers the download branch — Bitdefender is built for that class, and Norton 360 bundles it with identity tools.

Clicking is rarely the disaster. Typing is. Work out which you did, contain that, and report it. The managers and monitoring that limit the damage next time are compared in our shortlist of security tools. This is general guidance, not security advice for a specific threat model.

Affiliate disclosure

This article contains affiliate links. If you purchase through them, CyberTechVault earns a commission at no extra cost to you. Our assessments are based on vendors' published documentation, independent lab results and security disclosures — not on hands-on testing by us. Affiliate relationships never decide what we recommend.

Full disclosure: /affiliate-disclosure.

Sources

Factual claims above were checked against these primary sources. Verify directly on the source for anything time-sensitive before relying on it.

Continue reading

Continue in this collection