Undocumented Google OAuth Endpoint Exploited for Session Hijacking: The MultiLogin Attack

In the world of cyber threats, information-stealing malware continues to evolve, employing sophisticated techniques to gain unauthorized access to sensitive data. A recent security breach uncovered the exploitation of an undocumented Google OAuth endpoint named MultiLogin. This endpoint enables threat actors to hijack user sessions, allowing continuous access to Google services even after a password reset. In this article, we delve into the critical exploit, its implications, various malware families incorporating it, the attack technique employed, Google’s response, recommendations for users to protect themselves, and the necessity for advanced security solutions.

Exploiting an undocumented Google OAuth endpoint named MultiLogin

MultiLogin, an authentication endpoint designed for synchronizing Google accounts across services, plays a central role in session hijacking. When users sign in to their accounts in the Chrome web browser, MultiLogin aids in seamless account synchronization. However, threat actors have discovered its hidden potential, leveraging it for unauthorized access to user sessions.

Understanding the Critical Exploit and Its Implications

This critical exploit provides threat actors with session persistence and cookie generation capabilities. As a result, they can maintain access to a valid session, even when unauthorized, compromising the integrity and security of Google services. The implications are far-reaching, potentially exposing sensitive user data and enabling further malicious activities.

Incorporation of the Exploit into Various Malware Families

The exploit has been integrated into several malware-as-a-service (MaaS) stealer families, including Lumma, Rhadamanthys, Stealc, Meduza, RisePro, and WhiteSnake. These malware variants gain access to Chrome’s token_service table of WebData, extracting tokens and account IDs of logged-in Chrome profiles.

The Technique Used in the Attack

Within the attack technique, threat actors target Chrome’s token_service table to extract the necessary tokens and account IDs. By obtaining the token:GAIA ID pair, they combine it with the MultiLogin endpoint to regenerate Google authentication cookies, achieving persistent access to compromised user sessions.

Google’s Response to the Attack Method

Acknowledging the existence of this attack method, Google emphasizes that users can mitigate the impact by revoking stolen sessions. By simply signing out of the affected browser or remotely revoking access via the user’s devices page, users can invalidate the stolen sessions and regain control over their accounts.

Recommendations for Users to Protect Themselves

In light of this security breach, it is crucial for users to take proactive measures to safeguard their accounts. Changing passwords and monitoring account activity for suspicious sessions from unfamiliar IP addresses and locations are essential steps to protect against session hijacking and unauthorized access.

The Need for Advanced Security Solutions to Combat Evolving Cyber Threats

This incident serves as a reminder of the ever-present need for more advanced security solutions to counter the constantly evolving landscape of cyber threats. The exploitation of undocumented endpoints like MultiLogin highlights the importance of a robust security infrastructure and a proactive approach to mitigate risks.

The exploitation of the undocumented Google OAuth endpoint, MultiLogin, for session hijacking poses a significant threat to user accounts and data security. Understanding the critical exploit, its implications, and the techniques employed by threat actors is crucial for users to protect themselves. By staying vigilant, implementing recommended security measures, and embracing advanced security solutions, users can strengthen their defenses and stay one step ahead of evolving cyber threats.

Explore more