Quick answer
Help desk social engineering is when an attacker calls or messages your IT support team pretending to be an employee, usually one who is locked out or has a new phone, and persuades them to reset a password or MFA method. It bypasses every technical control at once, and it has been the starting point for several major breaches of large companies.
On this page
How It Works
The attacker researches a target employee on LinkedIn and social media, gathers details such as their manager, employee number or recent travel, and calls the help desk under time pressure: they are at an airport, about to present to the board, or their phone was stolen. Some use AI voice cloning to sound like the person. Once the help desk registers a new MFA device or issues a temporary password, the attacker signs in as a legitimate user, often a privileged one, and moves quickly to cloud consoles, identity systems and data.
Why It Matters
Help desks are measured on how quickly they solve problems, which works in the attacker's favor. Groups such as Scattered Spider have used this technique against hospitality, retail and technology companies to reach domain admin and cloud administrator access within hours. Verification questions based on information that is publicly available or easily stolen do not stop a prepared caller.
How to Test for It
- Run an authorized vishing exercise against the help desk using realistic pretexts, such as a lost phone or an urgent executive.
- Review the identity verification procedure for password and MFA resets: what does a caller need to prove, and can that be found online?
- Check whether resets for privileged and executive accounts require extra steps.
- Test whether the user and their manager are notified when their MFA method changes.
- Check whether new MFA registrations from new locations trigger alerts and review.
How to Reduce the Risk
Verify identity with something an attacker cannot research, such as a call back to the number on file, a manager's approval, a video check against an ID, or self-service reset with an existing strong factor. Apply stricter rules to privileged accounts, notify users and managers of every MFA change, alert on new MFA registrations followed by unusual activity, and give help desk staff explicit permission to slow down.
Regulatory and Framework Context
In the US, CISA and the FBI issued a joint advisory on Scattered Spider describing help desk social engineering, and NIST SP 800-63 sets out identity proofing levels that apply to credential recovery.
Latest intel on this topic
- US disrupts North Korean campaign behind $400 million crypto theftBleepingComputer · November 14, 2026
- FBI Says North Korean Hackers Stole Over $400 Million in Crypto Using Deepfake Video CallsThe Hacker News · November 13, 2026
- Extortion Group Luna Moth Flits Into Law Firms a Second TimeDark Reading · November 12, 2026
Updated hourly from the daily briefing. More in scam alerts and fraud warnings.
Common questions
Why is the help desk such a common target?
It is the one place where a person can legitimately bypass MFA for a user who is locked out. If the verification can be fooled, every other control is skipped.
Are knowledge-based questions enough?
No. Date of birth, employee ID and manager's name are often findable online or in previous breaches. Use call-backs, manager approval or verified ID instead.
Change log
- November 13, 2026First published.