12 Red Flags of Phishing: What to Do If You Clicked
A practical checklist for spotting phishing in email, text, and calls, plus a clear action plan for securing accounts and reporting suspicious messages.

The inbox lights up with a warning about a failed payment. Your phone rings moments later, supposedly from the company’s help desk. Seconds after that, a text announces that a parcel is waiting for collection. Individually, each could be legitimate. Together, they are a reminder that phishing rarely announces itself as a crime.
The danger is not merely clicking. It is entering a password, approving an authentication prompt, opening an attachment, sending money or disclosing personal information. The safest response is not panic, but a quick pause followed by a simple security routine.
All examples in this article are fictional illustrations created to show common warning signs; they are not real cases.
1. Inspect the sender, context and request
A convincing phishing message can borrow a familiar name, reproduce a polished logo and refer to something relevant to your life. Visual polish is not proof of legitimacy. Email addresses can be spoofed, and generative AI can make written messages and images more convincing.
The sender is not who they appear to be
- The display name is familiar but the address is not. A message showing a familiar company name may come from an unrelated address. Look at the complete address, including the domain, rather than relying on the name beside it.
- The request contradicts the normal channel. An organization that normally communicates through its own website may suddenly ask you to send a password, payment or confidential file by email.
- The greeting is wrong or oddly specific. A generic “Dear customer” may be weak evidence, but a message containing the wrong name, title or project detail can be just as suspicious. Personalization does not establish trust.
Illustration: A supposed colleague asks for an employee’s payroll details and payment change “before the end of today,” even though the colleague’s address differs slightly from the one normally used.
The message manufactures urgency
Phishing often creates pressure so the target acts before checking. Warnings that an account will be closed, a payment is being cancelled or an investigation will begin are designed to interrupt careful thought. Urgency alone does not prove an attack, but it is a strong reason to pause.
Illustration: A text says, “Your delivery cannot be released. Confirm your address within two hours,” and includes a button that leads to a sign-in page unrelated to parcel collection.
2. Treat links, attachments and QR codes with suspicion
A link’s visible wording can differ from its destination. Phishing links may use misspelled domains, deceptive subdomains or trusted redirect services to conceal their real target. Internationalized domain names can also imitate legitimate addresses with visually similar characters. On a mobile device, where the full address may be harder to inspect, the problem becomes harder still.
Preview the destination, not just the sentence
Before opening a suspicious link, inspect where it points. On a computer, this may mean pausing over the link to reveal the destination. Do not rely on the display text alone: a link labelled “Open account” could point elsewhere. If the destination does not match the service named in the message, do not proceed.
Illustration: A button labelled “Review document” opens a page whose address contains a company-like word followed by a different, unfamiliar domain.
Unexpected attachments deserve extra caution
- An attachment may arrive without warning, carry an unexpected file type or be named in a way that encourages you to open it immediately.
- Files that appear to contain documents, invoices, delivery details or account updates can carry malware.
- If you opened an attachment rather than merely receiving it, contact your IT or security team promptly.
Illustration: A message titled “Updated time sheet” includes a spreadsheet with a name that does not match your organisation’s usual file naming pattern.
QR codes can hide their destination
A QR code sends a scanning device to a website, but the destination cannot be read directly from the code. Attackers can send codes by email or social media, or place misleading codes over legitimate ones. A code in a public place should therefore be treated like any other unexpected link.
Illustration: A sticker placed over a car park payment notice contains a different code from the one underneath and opens a credential-stealing page.
3. Recognise requests that expose credentials or money
Password requests should make you stop
Legitimate services need to authenticate your identity, but a message should not be the thing that collects your password. Phishing pages imitate sign-in screens and collect credentials directly. If a message links to a login page reached through an unexpected message, close it and navigate to the service independently instead.
Illustration: An email announcing “a mailbox security update” opens a page that asks for an email address, password and recovery details. The page looks polished, but the destination is unfamiliar.
One-time codes and approval prompts are not foolproof
A familiar service may send an authentication prompt or one-time code that you did not request. Do not approve it merely to make it disappear. In adversary-in-the-middle phishing, an impostor website can relay authentication to the legitimate service in real time, capturing credentials and even a one-time code. That means a successful relay can make the sequence look normal.
Illustration: You receive a sign-in approval after clicking a link in an unexpected message. The request times out when ignored, but the attacker’s relay has already captured the sign-in details.
Watch for unusual transfers, payments and data requests
Requests to change bank details, buy gift cards, send funds to a new account or disclose confidential information deserve independent verification. Use a known contact method, not the phone number, email address or link supplied in the suspicious message.
Illustration: A supplier asks you to pay an invoice to a newly created account. The message looks specific, including a familiar purchase reference, but the payment instruction arrived unexpectedly.
4. Apply the same checks to texts and calls
Smishing often borrows an everyday routine
SMS phishing may imitate a parcel delivery, bank alert, appointment or workplace message. It can contain a malicious link, request a call, ask for private information or offer a malware lure. The limited display of addresses on mobile devices makes careful inspection harder, so unexpected texts should be verified through the relevant organisation’s normal channel.
Illustration: A text appears to come from a delivery service, asks for a small redelivery fee and requests card details on an imitation website.
Vishing relies on authority and claimed activity
Voice phishing may involve automated calls, text-to-speech or a person using social-engineering techniques. Callers can claim that fraudulent activity has occurred on an account and ask for sensitive information. Caller numbers may also be spoofed, making the displayed name or number unreliable evidence.
Illustration: A caller says a payment is pending and asks you to “confirm” your account by reading back a one-time code. The caller knows a transaction is pending because it was obtained through a separate phishing attempt.
Break the conversation if you feel directed
- Do not share passwords, one-time codes, recovery information or payment instructions.
- End the call and contact the organisation independently if you need help.
- Do not return a suspicious number simply because it appeared in the message.
- Expect the caller to create fear, secrecy or authority if you hesitate.
Being polite is not the same as being compliant. You can say: “I don’t make security changes during unsolicited calls. I’ll contact the organisation myself.”
5. Use a two-minute verification routine
When a message produces doubt, avoid acting on its instructions. Instead, run a simple routine:
- Stop. Do not click, reply, pay, approve a prompt or provide information.
- Identify the real service. Think about what organisation or person the message claims to represent, without using any contact details contained in it.
- Open your own route. Type the service into a trusted app, use a bookmark or navigate from your usual starting point.
- Check the account. Look for security notices, recent sign-ins, password changes and pending transactions.
- Verify independently. Contact the organisation through a trusted number, official app or established workplace channel.
- Report and preserve. Keep the message and relevant details until it has been reported.
This routine helps even when the message contains a detail that matches your circumstances. A phisher may know a recent order, invoice, delivery or internal project without having any legitimate access to the service.
6. “I clicked — now what?”
The next steps depend on what happened. A link click without further interaction is different from entering a password, approving a prompt, paying money, opening an attachment or installing software. If you are unsure how far the interaction went, assume the more serious possibility and seek help.
Immediate response
- Stop interacting with the message. Close the page, do not reply and do not follow any instructions the site displays.
- If you opened an attachment or installed something, disconnect from the network. Stop using the device and contact IT or the relevant security team. Do not attempt to fix the device while the suspected message or file remains active.
- Preserve useful details. Keep the original message, note when you interacted and save the destination of the link if you can do so safely. Do not revisit the site merely to investigate.
- Change exposed passwords from a trusted device. Use a unique password for the affected service. If the same password was used elsewhere, change it there too. If the affected device cannot be trusted, use another device.
- Review account activity. Check sign-ins, password changes, recovery details, forwarding rules, connected applications and recent transactions.
- Revoke active sessions and reset authentication options. Sign out other sessions where possible, review approved devices and change the authenticator setup if it may have been altered.
- Contact the relevant organisation. If payment or financial details were exposed, contact the bank or provider promptly using its established contact route. If a work account was involved, notify IT without delay.
- Report the message. Use the reporting control in your mail or messaging service and tell the appropriate IT, security or financial team. Delete it after the required evidence has been preserved.
Adjust for what was exposed
- Only clicked: Close the page, monitor for follow-up messages and report it. The click may have been all that occurred, but you cannot always tell from the page alone.
- Entered a password: Change the password, revoke sessions and review recovery settings immediately.
- Approved an authentication request or entered a one-time code: Treat the account as potentially compromised even if no unfamiliar alert appeared.
- Opened an attachment or installed software: Disconnect and involve IT or security support.
- Sent money or personal information: Contact the provider and relevant financial institution promptly, document what happened and follow their instructions.
Frequently asked questions
Does an unfamiliar sender address prove an email is phishing?
No. Legitimate services and compromised accounts can produce unusual sender information, while phishing can imitate a trusted address. Treat the address as one piece of evidence and verify through the organisation’s normal channel before acting.
Is a familiar logo or polished design enough to trust an email?
No. Attackers can imitate branding, and generative AI can help create convincing text and images. Consider the message’s request, destination and context rather than judging authenticity from appearance alone.
What if I entered my password but nothing bad happened?
Change that password from a trusted device, sign out other sessions, review account activity and check that recovery details and authentication methods have not been changed. Report the event to the relevant service or IT team even if no suspicious activity is yet visible.
Should I delete the suspicious message immediately?
Preserve it until it has been reported and any needed evidence is recorded. Keep the message, note the time of interaction and record what you clicked or entered; your security team may need those details to assess the incident.
Phishing succeeds by pushing people toward the next urgent action. Your defence is not perfect recognition every time; it is the ability to pause, verify independently and respond quickly when something goes wrong. The best security habit is simple: if a message tries to make you act before you think, take control of the next step yourself.
Sources: Wikipedia — Phishing; Email spoofing; Social engineering (security). Facts checked against the article text before publication.


