How to Respond to a Smishing Attack on Healthcare Staff
What should healthcare staff do when they receive a suspicious text?
Smishing is SMS phishing: a text message designed to trick you into clicking a link, opening an attachment, replying, or sharing sensitive information. If a message unexpectedly asks you to sign in, verify a code, or access a work system, treat it as suspicious—even if it appears to come from a colleague, a familiar organization, or a number you recognize. Caller and sender information can be spoofed.
Do not click links, open attachments, reply, call a number in the text, or enter credentials. If you need to check whether a message is genuine, contact the supposed sender using a phone number or channel you already know is legitimate. The FTC’s guidance on suspicious text messages recommends avoiding links in unexpected texts and contacting organizations through known, trusted channels.
Report the message through your employer’s security incident reporting process, even if you have not interacted with it. Follow your organization’s instructions before blocking or deleting the message, since it may be useful for incident documentation. Do not forward it to coworkers or a personal account.
How should staff report a suspected smishing message?
Use the organization’s designated security channel, such as its security operations center, IT help desk, incident-reporting system, or on-call security contact. Follow your employer’s policy for urgent reports; if the message may affect a clinical account or active patient care, notify your supervisor or the appropriate clinical leader as well.
Tell the response team whether you only received the text, replied, clicked a link, opened an attachment, downloaded an app, or entered information. Report promptly even if you are unsure whether the message was malicious. HIPAA’s Security Rule requires covered entities and business associates to respond to suspected or known security incidents, mitigate harmful effects where practicable, and document incidents and outcomes. See HHS guidance on security incident procedures.
After preserving the message and following workplace policy, you may also report an unwanted text to your mobile carrier by forwarding it to 7726 (SPAM), or use your phone’s report-junk feature. The FTC explains these reporting options. Carrier or FTC reporting does not replace your organization’s internal incident report.
What incident details should staff preserve?
Preserve what you can without clicking links or changing the message. Follow your organization’s instructions and use an approved, secure channel to send evidence; the message may contain sensitive information.
- The original text on the device, including the sender’s number or displayed name.
- The date and time received, including your time zone if known.
- The full message text, any displayed link or attachment name, and screenshots that show the message and sender.
- Whether you replied, clicked, opened or downloaded anything, entered information, or received follow-up prompts.
- The device involved, whether it is organization-managed or personal, and whether it was being used to access work accounts or systems.
- Any signs of unusual behavior, such as unexpected login prompts, account alerts, or unfamiliar activity.
Do not visit the link just to copy its destination, delete the message, or forward it outside approved reporting channels unless your response team directs you to do so. HHS notes that incident procedures may include preserving evidence, mitigating the situation, and documenting the incident and its outcome, consistent with the organization’s administrative safeguards; see its HIPAA Security Series guidance on administrative safeguards.
Ready to simplify HIPAA compliance?
Join thousands of organizations that trust Accountable to manage their compliance needs.
Get Started Free TodayWhat should staff report if they clicked a link or shared information?
Report the interaction immediately; do not wait to confirm whether anything bad happened. Be specific about what you did and when: whether you opened a page, downloaded or installed anything, allowed a permission, entered a password, shared a verification code, or provided patient or other sensitive information.
If you entered a work password or verification code, contact your organization’s IT or security team using a trusted method—not the message’s link or phone number. From a trusted device and through an official login page, follow the team’s instructions to change the password, revoke active sessions, and secure the account. Tell the team if you reused that password elsewhere. A shared verification code can enable account access even when you did not disclose your password.
If you entered patient information or sent it to someone, tell the privacy officer or designated privacy contact what information may have been exposed, which patients or records may be involved if known, and where it was submitted. Do not try to investigate or contact affected patients yourself unless your organization directs you to. A staff report is not the same as a formal breach determination: the organization’s privacy and security teams assess the facts and determine whether notification duties apply. See the HHS Breach Notification Rule overview.
How can the response team protect affected devices and accounts?
The response team should assess the device, accounts, and systems involved, then decide what containment is appropriate. Mobile device isolation may help limit risk, but staff should follow their organization’s directions rather than independently disconnecting, powering off, wiping, or resetting a device. Those actions can affect evidence, security controls, or access needed for clinical work.
Depending on what happened, authorized responders may isolate the device from organizational resources, use mobile device management tools, block a malicious link or sender, reset credentials, revoke sessions, and review account and system logs for unusual access. If malware or unauthorized access is suspected, do not install cleanup tools or attempt your own remediation; report what you observed and let qualified responders guide next steps.
HIPAA requires regulated entities to identify and respond to suspected or known security incidents, mitigate harmful effects where practicable, and document outcomes. The organization’s policies determine how it applies those duties to a specific event. See 45 CFR § 164.308 and the HHS fact sheet on ransomware and HIPAA.
How should teams address patient care and potential data exposure?
Coordinate cybersecurity response with clinical leadership. If a device or account is needed for care, identify a safe alternative and follow approved downtime procedures so clinical work can continue without using a suspected compromised system. The HIPAA Security Rule includes an emergency mode operation plan for continuing critical business processes while protecting electronic protected health information. Healthcare organizations can also consult the ASPR TRACIE Cyber Incident Response Checklist for response considerations such as communications and downtime procedures.
Document the timeline, staff actions, systems and accounts involved, containment steps, and known or possible patient information exposure. Preserve relevant logs and evidence through approved processes. The privacy and security teams should assess what information may have been accessed or disclosed, who may be affected, and whether regulatory or other notification requirements apply.
HIPAA breach notification depends on the organization’s assessment of the incident and whether unsecured protected health information was breached; not every suspicious text or click automatically means a reportable breach. If notification is required, the covered entity must notify affected individuals without unreasonable delay and no later than 60 calendar days after discovery, subject to the rule’s requirements. See the HHS Breach Notification Rule for details.
In short, do not engage with the text, report it promptly through the approved channel, preserve evidence, and disclose any interaction or information shared. Let the response team coordinate containment, patient-care continuity, incident documentation, and any privacy review.
FAQs
Should I report a smishing text if I did not interact with it?
Yes. Report it through your organization’s security incident reporting process even if you did not click, reply, or share information. A report can help the security team identify messages targeting other staff and assess whether additional action is needed.
What details should I give the incident response team?
Share the sender information, message and link details, date and time received, device involved, and whether you replied, clicked, opened or downloaded anything, or entered information. Preserve the original message and screenshots if your organization’s policy allows, and use an approved reporting channel.
What should I do if I entered my password or verification code?
Contact your organization’s IT or security team immediately using a trusted channel. Do not return to the text’s link. Follow the team’s instructions to secure the account, which may include changing the password from a trusted device and revoking active sessions. Tell them exactly what you entered and whether the password was reused on other accounts.
Should I delete the suspicious text message?
Do not delete it until you have reported it and followed your organization’s instructions. The original message may help the response team investigate. Avoid forwarding it outside approved channels, and delete it only when your employer’s policy or the response team says it is appropriate.
Table of Contents
- What should healthcare staff do when they receive a suspicious text?
- How should staff report a suspected smishing message?
- What incident details should staff preserve?
- What should staff report if they clicked a link or shared information?
- How can the response team protect affected devices and accounts?
- How should teams address patient care and potential data exposure?
- FAQs
Ready to simplify HIPAA compliance?
Join thousands of organizations that trust Accountable to manage their compliance needs.
Get Started Free Today