The email that reaches your HR manager doesn’t look dangerous. It’s from “InfoSec,” the subject line is “Password Reset Notification,” and it says her Outlook password stopped working after a “security modification.” There’s a self-service reset link, a list of password rules that looks like every real policy she’s seen, and a warning that the account locks in 24 hours. Nothing about it is technical. It works by sounding like your own IT department on a busy afternoon.
We have seen that exact lure forwarded to our help desk by staff at several nursing homes, often with three words on top: “Is this legit?” The staff who ask are doing the right thing. The question for an administrator is what happens on the day someone doesn’t ask.
What is a digital social engineering attack?
A digital social engineering attack is an attempt to trick a person, through email, text, phone, chat or a fake website, into giving up access, money or data, or into running something they shouldn’t. The attacker doesn’t break your firewall or your EHR. They borrow someone’s trust instead: a password typed into a fake login page, an MFA code read aloud to a “help desk,” a vendor’s “new bank account” entered into accounts payable.
The “digital” part is just the channel. The attack itself is on people under time pressure, which is why a skilled nursing facility, running 24 hours a day with rotating shifts, agency staff and dozens of outside vendors, is such a good target.
The common forms, as TechTarget and most security references group them:
- Phishing: a fraudulent email made to look legitimate, usually leading to a fake login page.
- Spear phishing and whaling: phishing written for one person or role, often the administrator, CFO or business office manager.
- Vishing: social engineering by phone.
- Smishing: the same trick by text message, often to staff personal phones.
- Pretexting: a made-up story that justifies the request (“I’m the new therapy contractor, I need the Wi-Fi password”).
- Baiting: leaving an infected USB drive or similar device where someone will plug it in.
What it looks like inside a nursing home
Generic definitions miss where these attacks actually land in a building. Here is how the same techniques map onto SNF operations.
| Where it lands | What the attacker sends or says | What they’re after |
|---|---|---|
| Any staff inbox | A fake Microsoft 365 “password reset” or “mailbox expiring” notice | The mailbox, and everything in it, including resident information |
| Your IT help desk | A call from “an employee” who has a new phone and needs MFA moved | A working login that bypasses MFA |
| Business office | An email from a “vendor” or payer contact with new bank details | Diverted payments |
| Administrator or DON | A short, urgent request that looks like it came from the owner or regional office | A wire, gift cards, or a document with PHI |
| Nurses’ station phone | A caller posing as a family member, pharmacy or hospital asking about a resident | Protected health information |
| Staff personal phones | A text with an MFA prompt or a “verify your account” link | Codes and credentials |
The help desk row is not hypothetical. In April 2024, the HHS Health Sector Cybersecurity Coordination Center (HC3) issued a sector alert describing attackers who called health sector IT help desks from a local area code, posing as employees in revenue cycle or administrator roles. They had the employee’s corporate ID and the last four digits of their Social Security number, claimed their phone was broken, and talked the help desk into enrolling a new device for MFA. With that access they went after payer websites, submitted ACH changes and redirected legitimate payments to accounts they controlled.
Notice what that attack needed: a plausible story, a few pieces of personal data that are easy to find after a breach, and a help desk that resets MFA on the strength of a phone call. No malware at all.
Why skilled nursing gets hit differently than an office
Three things about SNF operations make social engineering easier, and none of them are training problems.
Nobody knows everyone’s voice. Agency nurses, per diem staff, weekend supervisors and contractors rotate through every week. A caller who says “this is IT” or “this is the regional office” is rarely challenged, because the person answering often doesn’t know who IT is.
Vendors legitimately send links and ask for things. Your EHR vendor, pharmacy, lab, therapy contractor, staffing agency and payroll provider all email links, request logins and call about accounts. Attackers copy that normal traffic. “PointClickCare needs you to re-verify” doesn’t sound odd in a building where PointClickCare is open on every workstation.
The building never closes, but the decision-makers do. A request that arrives at 6 a.m. on a Sunday lands on whoever is on shift, with no administrator or business office manager to check with. Attackers know this and time their requests for nights, weekends and holidays.
Training is required, but controls are what stop it
HIPAA expects you to train your workforce. The Security Rule’s administrative safeguards include a security awareness and training standard at 45 CFR 164.308(a)(5), and your HIPAA risk analysis should treat social engineering as a real threat to ePHI, not a footnote. If you haven’t done a current one, our HIPAA risk assessment for nursing homes covers what it should include.
But training alone assumes a tired person on a double shift will spot a well-made fake every time. They won’t. The better question for every risky request is: what makes this attack fail even when someone falls for the first step? That’s where your money should go.
- A callback rule for passwords, MFA and bank details. Any request to reset a password, move MFA to a new device or change payment details gets verified by calling a number already on file, never the number in the email or the one the caller gives. The HC3 alert recommends exactly this, and notes that attackers will say they’re too busy to take a callback. Treat that as a red flag, not an inconvenience.
- MFA that a phone call can’t talk around. HC3, citing Mandiant, recommends Microsoft Authenticator with number matching, removing SMS as an MFA option, and requiring a trusted network or compliant device to register MFA or reset a password. If your staff still get codes by text, that is the gap to close first. Our post on MFA fatigue scams explains the push-notification version of this attack.
- Two people for any payment change. A new bank account for a vendor, payer or employee’s direct deposit should need a second person and a callback to a known contact before it takes effect. This is a business office procedure, not an IT product, and it shuts down the most expensive outcome.
- One way to report, and no blame for using it. Staff should know exactly what to do with a suspicious message: one button or one address that reaches someone who looks at it. Marking a phish as junk isn’t reporting it: junk tells no one. If one person got the message, others did too, and someone needs to pull it from every inbox.
- Ask your IT provider how they verify you. Your help desk is a target too, as the HC3 alert shows. Ask your managed service provider what they check before resetting a password or MFA for one of your staff. If the answer is “we recognize their voice” or “they told us their employee ID,” that won’t stop the attack HC3 described.
If someone already clicked
Speed matters more than blame. If a staff member entered a password on a fake page, approved an MFA prompt they didn’t start, or read a code to a caller:
- Reset the password and revoke active sessions right away, not at the end of the shift.
- Check the mailbox for new forwarding rules and sign-ins from unfamiliar locations. Attackers often add a rule to hide replies.
- Tell the business office to hold any recent payment or bank-detail changes until they’re verified.
- Bring in your privacy officer. If the account held resident information, you may have a reportable HIPAA breach, and that call depends on what the attacker could reach. Our ransomware post walks through why the first few hours decide how bad an incident gets.
Write these steps into your incident response plan with names and phone numbers, so the night supervisor doesn’t have to work them out at 2 a.m.
The short version for administrators
A digital social engineering attack goes after your staff’s trust, not your technology. In a nursing home it usually means a fake Microsoft 365 login, a call to your help desk to move MFA, or a request to change where money goes. Training helps and is expected under HIPAA. What stops the expensive outcomes is a callback rule, MFA that can’t be talked around, two-person payment changes and a single reporting path.
If you want a second set of eyes on how your facility would hold up, including how your help desk verifies callers, talk to RDE about skilled nursing IT or contact us.