Critical Copilot vulnerability allowed hackers to steal 2FA code from users
- Published
- Jun 16, 2026 — 11:15 UTC
A significant security vulnerability has been identified in Microsoft’s Copilot, which could allow hackers to steal users’ two-factor authentication (2FA) codes. This issue is particularly pressing as the industry grapples with ongoing challenges in securing large language models (LLMs). The exploit, dubbed SearchLeak, underscores the persistent failures in the industry’s approach to LLM security, highlighting the urgent need for improved safeguards.
The SearchLeak vulnerability demonstrates a critical flaw in how LLMs handle sensitive information, potentially compromising user security on a large scale. The exploit allows malicious actors to intercept 2FA codes, which are crucial for protecting user accounts from unauthorized access. This revelation comes at a time when the reliance on 2FA has increased, making the implications of such vulnerabilities even more severe. As noted by Ars Technica, the incident raises questions about the robustness of security measures currently employed by AI developers.
The broader competitive landscape is also affected, as other companies in the AI space may face scrutiny regarding their security protocols. With the rise of AI-driven tools, the potential for similar vulnerabilities exists across various platforms. This incident could prompt a reevaluation of security practices not just within Microsoft but across the industry, as companies strive to protect user data and maintain trust. The implications are significant; if users feel their accounts are at risk, they may hesitate to adopt AI tools, stunting innovation and growth in the sector.
As the industry continues to confront these security challenges, the SearchLeak exploit serves as a cautionary tale. Companies must prioritize the development of more secure LLM frameworks to prevent similar breaches in the future. The ongoing dialogue about AI security will likely intensify, pushing for more stringent regulations and standards to safeguard user information.
Looking ahead, it will be crucial to monitor how Microsoft and other AI developers respond to this vulnerability and what measures they implement to enhance security protocols.
By Callan Zhang · Jun 16, 2026 · Editorial standards →
Summarised from the primary source with AI assistance under human editorial oversight. Turing Wire is not a primary source — read the original for the authoritative account.
Source: Ars Technica AI