What to Do in the First Hour After Someone Clicks a Phishing Link
Someone clicked a phishing link. Here's a minute-by-minute first-hour playbook to contain the account, check for spread, protect payments and make the right calls.
It's 2:40 on a Tuesday afternoon. Someone in accounts payable walks over to your desk, a little pale, and says, "I think I clicked something I shouldn't have." The email looked like a shared invoice from a supplier you actually use. She clicked the link, a Microsoft sign-in page came up, and she typed her password before it occurred to her that something was off.
If someone on your team clicked a phishing link, what to do in the next 60 minutes matters far more than what you do next week. I've been doing network and IT work for 15 years, and my partner Mukesh has spent 25 years in cybersecurity. The incidents that turn ugly are rarely the ones where someone clicked. They're the ones where nobody acted quickly because they weren't sure what to do first.
This is the first-hour playbook we wish every small manufacturer and small business had taped to the wall. It assumes you don't have a security team on staff.
In this guide
- Why the first hour after a phishing click matters
- Minutes 0 to 5: keep the user talking, not hiding
- Minutes 5 to 15: contain the device and the account
- Minutes 15 to 30: figure out what the link actually did
- Minutes 30 to 60: look for spread and protect the money
- Who to call: insurance, bank, law enforcement and compliance
- A printable first-hour checklist
Why the first hour after a phishing click matters
Most phishing links are after one of three things: your password, a foothold on the computer, or a payment. Stolen Microsoft 365 or Google Workspace credentials are often tested within minutes, sometimes by automated tools.
The goal of the first hour is simple. Stop the attacker from using what they got, find out how far it went, and preserve enough evidence to make good decisions later. You do not need to solve the whole incident in an hour. You need to close the doors before anyone walks through them.
A click is not automatically a breach. Plenty lead nowhere because the user closed the page or a filter blocked it. Your job is to find out which kind of click this was, fast.
Minutes 0 to 5: keep the user talking, not hiding
The single most valuable thing in a phishing incident is an employee who reports it right away. If people get yelled at for clicking, the next person will close the window and say nothing. Thank them, out loud, and mean it.
Then get the facts while they're fresh. Ask these questions and write the answers down with the time:
- What time did you click, and what did the email say?
- Did a page ask you to sign in? Did you enter your password?
- Did you get an MFA prompt or text code, and did you approve it or type it in?
- Did anything download or open, like a file, a "document viewer" or a browser extension?
- Did the email ask you to change bank details, pay an invoice or buy gift cards?
Ask them not to delete the email. You'll need it to find other recipients and block the sender.
Minutes 5 to 15: contain the device and the account
Containment comes before investigation. You can always look closer once the doors are shut.
Isolate the computer, but don't wipe it
If anything was downloaded or opened, take the computer off the network. If you have an EDR tool (CrowdStrike, SentinelOne, Microsoft Defender for Endpoint, Cisco Secure Endpoint and similar), use its network isolation feature, which cuts the machine off while keeping it reachable for your security tools. If you don't, unplug the network cable and turn off Wi-Fi.
Leave it powered on if you can. Shutting it down or reimaging it right away can destroy evidence your insurer or a forensics firm may need.
Lock down the account
If the user typed a password into the fake page, assume the attacker has it. Do these in order:
- Reset the password from your admin console, not from the user's possibly compromised computer.
- Revoke all active sessions. In Microsoft 365 this is in the Entra admin center under the user's account; Google Workspace has a similar option to sign the user out of all sessions. This matters because many modern phishing kits steal the session token, not just the password, which lets an attacker skip MFA entirely until that session is killed.
- Check the MFA methods on the account and remove any phone number or authenticator app the user doesn't recognize. Attackers often register their own device to keep access.
- Reset the password anywhere else the user reused it. Ask them directly. Reuse is common, and it's better to know now.
If you do only one thing from this article, do steps 1 and 2 together.
Minutes 15 to 30: figure out what the link actually did
Now you can slow down slightly and look at what happened. You're answering one question: did the attacker get in, and if so, what did they touch?
Check the sign-in logs
Pull the user's sign-in history for the last 24 hours. In Microsoft 365, that's the Entra sign-in logs; in Google Workspace, the login audit log. Look for:
- Successful sign-ins from countries or internet providers you don't use
- Sign-ins from unfamiliar devices or browsers right after the click time
- A burst of failed MFA prompts followed by a success, which can mean the user approved one by mistake
If you see a successful sign-in you can't explain, treat this as a confirmed account compromise and keep going with the rest of this guide at full speed.
Look at what the attacker would do next
Attackers who get into a mailbox commonly do a few quiet things to stay hidden. Check the account for:
- Inbox rules that move, delete or mark as read any emails containing words like "invoice", "payment", "wire" or the name of your bank
- Forwarding set up to an outside address
- New app consents (OAuth apps) the user didn't knowingly approve, which can keep access even after a password change
- Sent items the user didn't write, especially to vendors or customers
Delete any malicious rules and forwarding, and revoke suspicious app consents. Take screenshots first so you have a record.
Check the computer
Read any EDR alerts from around the click time. Look for new startup programs, browser extensions or remote access tools. If anything doesn't make sense, bring in help rather than guess.
Minutes 30 to 60: look for spread and protect the money
Phishing emails are rarely sent to just one person. And in our experience, the real damage at small businesses usually comes from money moving, not from the click itself.
Find everyone else who got the email
Search your mail system for the same sender, subject line or link. Microsoft 365 admins can use Threat Explorer (if licensed) or content search; Google Workspace admins can use the security investigation tool or email log search. Then:
- Remove the message from every mailbox it reached.
- Block the sender address, the sending domain if it's clearly malicious, and the URL at your email filter and firewall or DNS filter.
- Ask anyone else who received it whether they clicked. Make it easy to say yes.
A calm all-staff note helps: "If you clicked the fake invoice email or entered your password, tell IT right away. You won't be in trouble."
Freeze the money trail
If the email involved payments, act on this before anything else in this section. Call your bank's fraud department immediately if any payment went out or bank details were changed, and ask them to attempt a recall. Wire transfers are hardest to recover, and in many cases the chance of recovery drops the longer you wait.
Then lock down the payment process for the next few days:
- Pause any pending vendor bank detail changes until they're confirmed by phone, using a number you already had on file, not one in the email
- Tell your AP team and owners that the account may have been used to send fake payment requests
- Warn any vendors or customers who may have received emails from the compromised account
Check who else the account could reach
Note whether the user could reach shared drives, the ERP, or files with drawings or CUI. If they were an admin, review recent admin activity, since admin rights let an attacker create accounts and change security settings.
For manufacturers, also think about the plant floor. If the laptop could reach production systems, confirm your isolation actually separated it. Good segmentation makes this much easier, which is one reason I wrote about securing shop-floor OT networks without stopping production.
Who to call: insurance, bank, law enforcement and compliance
Here's who you may need to contact, in roughly the order it tends to matter. I'm not a lawyer, and requirements vary by contract, industry and state, so confirm your obligations with your attorney or compliance assessor.
Your cyber insurance carrier
If you carry cyber insurance, call the carrier's claims or breach hotline early, ideally within the first day. Many policies require prompt notice and expect you to use their approved forensics and legal vendors. Paying your own vendor before notifying them can complicate coverage, so read your policy or call your broker before you hire anyone.
Law enforcement
The FBI asks businesses to report cyber fraud, including business email compromise, through the Internet Crime Complaint Center at ic3.gov. If a wire transfer is involved, report it to your bank and to IC3 as quickly as possible, because speed improves the odds of freezing funds. Your local FBI field office is another option for larger losses.
Compliance and contract obligations
This is where your industry matters:
- Defense suppliers: If your contracts include DFARS 252.204-7012 and the incident may affect covered defense information, the clause requires reporting to the DoD within 72 hours of discovery. If you're working toward CMMC, your incident response capability is part of what's assessed. I cover the basics in CMMC Level 1 vs. Level 2: which one does your manufacturing shop need?
- Healthcare and their business associates: HIPAA has its own breach assessment and notification rules if patient information may be involved.
- Any business holding personal information: Virginia, like every state, has a data breach notification law that can require notifying affected residents and, in some cases, the Attorney General if certain personal data was accessed. Other states' laws may apply if you have customers or employees there.
Don't try to decide whether it's a reportable breach in the first hour. Just write down what you know and when you learned it.
A printable first-hour checklist
Here's the whole playbook on one page. Print it, fill in the blanks for your company, and put it where the person on call can find it.
Minutes 0 to 5
- Thank the user and get the facts: time, what they clicked, password entered, MFA approved, files opened, payment requested
- Keep the email; don't delete it
Minutes 5 to 15
- Isolate the computer from the network (EDR isolation or unplug), leave it powered on
- Reset the password from the admin console
- Revoke all active sessions
- Remove unknown MFA methods
- Reset reused passwords elsewhere
Minutes 15 to 30
- Review sign-in logs for unfamiliar locations and devices
- Check inbox rules, forwarding, app consents and sent items
- Review EDR alerts on the computer
Minutes 30 to 60
- Search for and remove the email from all mailboxes
- Block sender, domain and URL
- Call the bank if money moved; pause bank detail changes
- Note what data and systems the account could reach
- Start an incident log with times and actions
Fill in for your company
- IT or MSP emergency contact: ____________
- Cyber insurance claims line and policy number: ____________
- Bank fraud line: ____________
- Attorney: ____________
- Who can approve taking a system offline: ____________
After the first hour, the work shifts to cleanup: reimaging the computer once evidence is preserved, confirming the attacker is out, and fixing what let the email through. If you want a broader starting list, our 10 steps to protect your company is a good place to begin.
Frequently asked questions
I clicked a phishing link but didn't enter anything. Am I safe?
Often, yes, but don't assume it. Visiting a page can sometimes trigger a download, especially on unpatched systems. Report it to IT, let them run a scan and check the browser for new extensions, and change your password if you have any doubt.
Should I turn off my computer after clicking a phishing link?
Disconnect it from the network instead of shutting it down. Unplug the cable or turn off Wi-Fi, then call IT. Leaving it powered on preserves evidence that can show what happened, which matters if your insurer or a forensics team gets involved.
Is changing my password enough after a phishing attack?
Usually not. Many phishing kits steal your active login session, which can keep the attacker signed in even after a password change. Your admin should also revoke all sessions, check for unknown MFA devices, and look for new inbox rules or forwarding.
Do I have to report a phishing incident?
It depends on what was accessed and what rules apply to your business. Defense contractors, healthcare organizations and any business holding certain personal information can have legal or contractual reporting requirements, some with short deadlines. Write down what happened and when, and check with your attorney or compliance advisor quickly.
How do I know if my email account was compromised after clicking a link?
Look for sign-ins from unfamiliar locations or devices, inbox rules you didn't create, forwarding to outside addresses, and sent emails you didn't write. Your IT admin can review the sign-in and audit logs to confirm. If anything looks off, treat the account as compromised.
Not sure you'd catch it in time?
A phishing click is going to happen at almost every company eventually. What separates a scare from a real incident is whether you have the tools, the logs and the plan to respond in that first hour. If you're not sure your sign-in logs are being kept, whether your EDR can isolate a machine, or who you'd even call, that's worth finding out on a quiet day rather than a bad one.
We offer a free cybersecurity assessment for small manufacturers and businesses across the US, including here in Roanoke and the rest of Virginia. We'll look at your email security, endpoint protection and incident readiness and give you a plain-English list of what to fix first. No pressure, and you keep the findings either way.
Related reading
- Cybersecurity for Roanoke Small Businesses: 10 Steps to Protect Your Company
- How to Secure Shop-Floor (OT) Networks Without Stopping Production
- Managed IT Services in Roanoke, VA: What Local Businesses Should Expect
Harsha is a co-founder of SoftwarePac Technologies in Roanoke, VA, and a network engineer with 15 years of experience.




