Help desk impersonation: Why attackers are calling instead of hacking
MFA has made account takeover harder, so attackers are targeting the people who can reset it. Help desk impersonation has made the help desk a critical identity control point. Here is what IT and security leaders should do about it.
Key takeaways
- Attackers are increasingly bypassing technical controls by posing as employees and asking IT help desks to reset passwords or multifactor authentication (MFA).
- Recent industry research shows that voice- and message-based social engineering is already a material source of security incidents and breach costs.
- The risk is operational as well as technical: One successful reset can give an attacker access to privileged accounts, sensitive data, and the systems needed to disrupt the business.
- Lean IT teams and MSPs need verification processes that do not depend on information an attacker can research, guess, or pressure an agent into accepting.
For years, one of the clearest pieces of security advice was to enable multifactor authentication (MFA). That advice remains sound: MFA still stops many account takeover attempts. But attackers have adapted, and help desk impersonation is now one of the simplest ways around it. Instead of stealing a password and defeating MFA directly, they call the help desk, pose as an employee who has lost a phone, and ask for both controls to be reset.
If the caller is believed, the attacker can receive a new password and register an MFA device they control. There may be no malware, exploited vulnerability, or obvious technical event to trigger an alert. A routine support process becomes the route into the environment.
Why attackers target the help desk
The reason is straightforward: The help desk can provide something an attacker would otherwise have to steal or bypass. As Gartner analyst Craig Porter said when the firm published its 2026 survey of security leaders: “Most attacks will continue to rely on users, stolen credentials, weak recovery processes, and familiar technical methods.”
Help desk impersonation exploits exactly those weak recovery processes. The stronger the organization’s login controls become, the more value attackers gain from persuading someone with legitimate authority to reset them. A convincing “I lost my phone” call can turn identity recovery into an authentication bypass.
U.S. authorities have documented the same playbook. In their joint advisory on Scattered Spider, CISA and the FBI describe attackers calling “to convince IT help desk personnel to reset passwords and/or transfer MFA tokens,” and then using the newly obtained access to take over accounts.
How common is help desk impersonation?
No single data point captures the full scale of help desk impersonation, but recent research and government warnings show that voice-based social engineering is no longer an edge case.
- Security leaders are already seeing voice- and message-based attacks. In a 2026 Gartner survey of 297 security leaders, 58% reported at least one vishing or smishing incident in the previous 12 months, and 41% reported a social engineering incident involving a deepfake on an employee audio call.
- Impersonation carries a measurable financial impact. IBM’s 2026 Cost of a Data Breach Report found that social engineering methods including IT or help desk impersonation and MFA fatigue appeared in 13% of attacks, with an average breach cost of $5.23 million. Voice and SMS phishing appeared in 17% of attacks and had an average breach cost of $5.29 million.
- AI can make impersonation more credible. The same IBM report recorded a 56% increase in AI-driven attacks, led by AI deepfake impersonation. AI is not required for this attack to work, but it can help attackers reproduce voices, tailor scripts, and create a stronger sense of legitimacy.
- Law enforcement continues to warn about the technique. In June 2025, the FBI warned that the group was expanding into the airline sector, “often impersonating employees or contractors to deceive IT help desks into granting access.”
- Voice is part of a broader phishing problem. The ENISA Threat Landscape 2025 identifies phishing, including vishing, as the leading initial access vector in about 60% of observed cases. This figure covers phishing more broadly, so it should not be read as a measure of help desk impersonation alone.
Together, these signals point to an important shift. Email remains a major attack channel, but organizations can no longer treat the phone as a trusted path. For the help desk, every high-risk recovery request is now an identity decision.
Why the help desk is vulnerable by design
Help desk teams are measured on speed, service, and their ability to get people working again. Access issues are a large part of that workload. Based on Barracuda’s own estimate, roughly half of MSP help desk tickets involve requests such as password resets, privilege elevation, and account lockouts. That combination of high volume and pressure to resolve issues quickly gives attackers an opening.
Consider a typical call. The caller knows the employee’s name, manager, role, and current project, information that may be available through public profiles, previous breaches, or a compromised mailbox. They create urgency and give the agent a plausible reason why normal verification will not work. If the fallback checks rely on an employee ID, date of birth, security question, or other discoverable information, the attacker may already have the answers.
This is not simply a training problem. It is a control gap. Awareness can help an agent notice suspicious behavior, but it cannot prove who is on the other end of the call. Gartner’s guidance following its 2026 survey makes the same point: Organizations should make verification the default for requests that could materially change access or risk.
How one reset becomes a business disruption
A successful call rarely ends with one compromised mailbox. Attackers often target accounts with the greatest reach: administrators, finance staff, executives, and other users with elevated access. That is why the UK’s National Cyber Security Centre (NCSC) specifically highlights resets involving accounts “with escalated privileges.” CISA’s advisory describes the next steps in the same campaigns: data theft, extortion, and ransomware deployment.
The business consequences can include operational downtime, incident response costs, regulatory exposure, customer disruption, and weeks of recovery work for teams that were already stretched. The second post in this series will examine organizations where help desk impersonation led to exactly these outcomes.
Why under-resourced organizations and MSPs face added pressure
High-profile breaches attract attention, but the technique is not limited to large enterprises. Resource-constrained organizations may have fewer people separating identity administration, support, monitoring, and incident response. The same person who answers the call may also manage the account, while no separate security team reviews an unusual reset until the damage is visible.
Outsourcing does not remove the risk; it redistributes it. CISA notes that attackers target “large companies and their contracted information technology (IT) help desks” and abuse “trusted relationships of contracted IT help desks.” For MSPs, one weak verification process can put multiple customer environments at risk. For customers, any provider authorized to reset credentials or MFA should be treated as part of the identity attack surface.
How to prevent help desk impersonation: What IT and security leaders should do next
Make identity verification part of the control stack
MFA, strong passwords, patching, and endpoint security remain essential. But every one of those controls depends on a secure recovery process. If an attacker can persuade the help desk to replace the password and MFA device, the organization has effectively issued new credentials to the wrong person.
Start with the highest-risk requests: password resets, MFA changes, privilege elevation, and recovery for administrators or executives. Require a verification method that is independent of the channel used to make the request, define when an agent must escalate, and ensure that exceptions are logged and reviewed. MSPs should apply the same standard consistently across customers rather than relying on customer-specific knowledge held by individual technicians.
Then test the process with a simple question: If someone called the help desk today and said they had lost their phone, what evidence would prove they were the account owner? If the answer is a few questions based on personal information, the recovery process is still vulnerable.
Learn how to strengthen caller verification and reduce the risk of fraudulent password and MFA resets. Register for the December webinar on stopping help desk impersonation.
Di cosa avranno bisogno i clienti MSP, dal back office alla sala del consiglio di amministrazione
Barracuda Research ha rilevato che l’eccellenza tecnica resta essenziale, ma la crescita futura sarà trainata dalle competenze in IA, dalla resilienza informatica e dalla capacità di comunicare il rischio in termini aziendali.
Iscriviti al blog di Barracuda.
Iscriviti per ricevere i Threat Spotlight, commenti del settore e altro ancora.
Rapporto sul divario di competenze nella sicurezza informatica: il rischio dell’IA è in cima alla lista
Un sondaggio di Barracuda Research condotto tra 2.000 responsabili della sicurezza rileva che il 94% segnala carenze di competenze nella sicurezza informatica, mentre l’IA riduce i ruoli entry-level nella sicurezza che contribuiscono a formare i futuri investigatori.