
In 2024, an employee at engineering firm Arup was tricked into transferring $25 million after attending a fake video conference featuring deepfake versions of their colleagues.
A year later, Marks & Spencer (M&S) suffered a major cyberattack after attackers used social engineering to gain access through a third-party helpdesk.
More recently, attackers have impersonated IT support staff to convince employees to hand over remote access to their devices.
While the tactics differ, these incidents raise an important question for IT and security teams: how can organizations be confident that someone requesting access or authorizing a sensitive action is who they claim to be?
We examine these attacks and explore how stronger identity verification and more secure workflows can help organizations defend against similar threats.
The Arup Deepfake Fraud
A finance employee at engineering firm Arup's Hong Kong office received an email in January 2024 that appeared to come from the company's UK-based CFO, requesting a series of transactions. Initially suspicious, the employee was convinced the request was genuine after joining a video conference featuring what appeared to be the CFO and several colleagues.
However, the meeting was a deepfake. According to Hong Kong police, the attackers had used publicly available video and audio to create a convincing pre-recorded conference.
The employee subsequently made multiple transfers, losing approximately HK$200 million (US$25.6 million).
The M&S Cyberattack
In April 2025, British retailer Marks & Spencer (M&S) suffered a major cyberattack that disrupted operations for weeks. Online orders were suspended, contactless payments and Click & Collect services were affected, and customer data was stolen.
M&S initially estimated the incident would reduce its 2025/26 operating profit by around £300 million before mitigation.
The attack was linked to the Scattered Spider cybercriminal group, known for using social engineering to gain access to corporate networks.
M&S later confirmed that attackers had gained entry by deceiving employees at a third-party contractor, rather than exploiting a technical vulnerability in its systems.
Fake IT Support
Microsoft recently reported a cyberattack campaign in which threat actors impersonated IT support staff through Microsoft Teams, tricking employees into handing over remote access to their devices.
The attackers contacted employees through external Teams messages or calls, posing as internal IT personnel. Using convincing pretexts such as urgent technical issues, they persuaded employees to grant remote control through screen sharing or legitimate support tools like Quick Assist.
Once connected, the attackers used PowerShell to install malicious software, establish persistent access and gather information about the compromised network.
Microsoft also observed attempts to move laterally towards critical infrastructure, including domain controllers and certificate authorities.
The Common Thread: Trust Replacing Verification
Impersonation Exploits Familiar Trust Signals
Social engineering has long been a key technique in attackers’ arsenals. They don't need sophisticated malware or technical exploits to compromise an organization if they can convince someone that they're a trusted colleague.
Deepfake technology makes this particularly concerning, as familiar faces and voices can be recreated.
But even without AI, attackers can use convincing pretexts and trusted communication platforms to make fraudulent requests appear legitimate.
Trusted Processes Can Become Attack Vectors
Password resets and remote IT support are routine activities, but they can also give attackers opportunities to gain access if requests aren't properly verified.
Third-party providers expand the potential attack surface; organizations may have strong controls over their own systems but less visibility into how external support teams verify identities and authorize sensitive actions.
Employees Can't Be Expected to Spot Every Impersonation Attempt
Security awareness training helps employees recognize suspicious requests, but even well-trained staff can be deceived by convincing impersonation attempts.
Attackers will carry out reconnaissance beforehand to gather information that makes their social engineering attempts appear like routine requests.
Organizations need reliable verification processes that support employees when they're asked to make security-sensitive decisions, rather than leaving them to judge whether someone can be trusted.
How Can Organizations Mitigate These Risks?
Strengthen Identity Verification at the Service Desk
Rather than relying on security questions or personal information that attackers may have obtained, service desk teams should use trusted authentication methods to confirm callers' identities.
Specops Secure Service Desk helps organizations build this verification into their service desk processes. Agents can verify callers using more than 15 MFA factors, including options that don't require a phone, with integrations for existing identity platforms such as Duo and Okta.
This helps ensure that sensitive account recovery actions are supported by reliable identity checks, reducing opportunities for attackers to exploit service desk procedures.
To see it in action, explore our interactive walkthrough and discover how agents can securely verify callers before carrying out sensitive account actions.
Build Verification Into Business Workflows
As organizations introduce self-service portals, internal chatbots and automated IT processes, it's important that these systems follow the same verification standards as traditional support channels.
A password reset request made through an internal chatbot, for example, should still require strong identity verification before the request is processed.
It’s here that solutions like the Specops Authentication API can help, by allowing organizations to add secure workforce authentication and identity verification to their existing applications, automated processes and business workflows.
By integrating verification directly into these processes, organizations can apply consistent security checks at critical points without relying entirely on manual intervention.
Independently Verify Sensitive Requests
For financial transactions, privileged access, and other sensitive requests, organizations should require independent confirmation through trusted channels.
This might include contacting the requester using previously verified details or introducing additional authentication into approval workflows.
Verify IT Support Requests Before Granting Access
Where support processes are managed through internal applications or automated workflows, additional identity verification can help ensure that sensitive requests are made by authorized users.
These measures should be supported by broader security controls like phishing-resistant MFA and least-privilege access, while monitoring for suspicious account activity.
Make Strong Verification Part of Everyday Security
As social engineering tactics become more convincing, organizations can't rely on employees recognizing every fraudulent request. Strong identity verification, independent approval processes and clear security procedures can help reduce the risks.
By building these checks into service desks, applications and everyday workflows, organizations make it harder for attackers to turn a convincing impersonation into a successful compromise.
If you’re interested in seeing how Specops can support your identity security strategy, book a demo today.
Sponsored and written by Specops Software.









English (US) ·