Threat intelligence reports indicate that the Lapsus$ extortion group, which was significantly disrupted in 2022, has reformed and is active once again. This new iteration of the group appears to have evolved, incorporating tactics and techniques from other criminal syndicates. The primary shift in their methodology is a move towards more sophisticated identity-based extortion schemes. Rather than relying solely on data theft and leaking, the resurgent group is leveraging compromised employee identities to conduct more subtle, persistent, and damaging attacks. This evolution makes detection more challenging and raises the threat level for large enterprises, particularly in the technology sector.
The original Lapsus$ group was infamous for its brazen attacks against major companies like Microsoft, Nvidia, and Okta. Their TTPs included a unique blend of social engineering, SIM swapping, and paying insiders for access. The group's primary goal was extortion, threatening to leak stolen source code and data if their demands were not met.
This new report suggests that the group's core members or affiliates have regrouped. The key evolution is the integration of techniques from other criminal operations and a refined focus on identity. This could mean they are moving beyond simple credential theft to more advanced forms of identity compromise, such as:
By focusing on identity, the group can achieve deeper and more persistent access, making their extortion threats more potent.
While specific TTPs of the new group are still emerging, they are likely building upon their old playbook with new enhancements.
T1589 - Gather Victim Identity Information: The core of their new focus. This includes gathering information on employees, their roles, and access levels.T1656 - Impersonation: Using compromised identities to socially engineer help desks or other employees.T1078 - Valid Accounts: Abusing stolen credentials, a hallmark of the original group.T1621 - Multi-Factor Authentication Request Generation: The infamous "MFA fatigue" or "MFA bombing" attack, where they spam a user with push notifications until one is approved by mistake.T1111 - Two-Factor Authentication Interception: Historically achieved through SIM swapping.The resurgence of an advanced group like Lapsus$ poses a significant threat. Their proven ability to breach well-defended, major technology companies demonstrates their skill and determination. An identity-focused approach increases the potential impact, as it can lead to a complete takeover of an individual's corporate access, allowing for subtle data exfiltration, source code manipulation, and sabotage over a long period. The financial and reputational damage from a successful attack by this group can be immense.
D3-UBA: User Behavior Analysis to baseline normal identity behavior and alert on deviations that could indicate a compromised account.M1032 - Multi-factor Authentication.Deploying phishing-resistant MFA (e.g., FIDO2) is the most effective technical control against many of Lapsus$'s known TTPs, including MFA fatigue and SIM swapping.
Mapped D3FEND Techniques:
Train all employees, especially IT help desk staff, to recognize and resist social engineering attempts.
Implement policies and technical controls to limit the number of MFA pushes a user can receive, mitigating MFA fatigue attacks.
Mapped D3FEND Techniques:
To counter the specific identity-based attacks favored by Lapsus$, organizations must prioritize the deployment of phishing-resistant MFA. Standard push-based or TOTP MFA are vulnerable to the group's known MFA fatigue and social engineering tactics. The gold standard is FIDO2/WebAuthn, which uses hardware security keys or platform authenticators (like Windows Hello). This method is not susceptible to phishing or credential theft. A strategic rollout should target privileged users, administrators, developers with access to source code, and help desk staff first, as these are all high-value targets for Lapsus$. This single control is the most powerful mitigation against the group's core TTPs.
To specifically combat the MFA fatigue attack (T1621), organizations should configure their Identity Provider (IdP) to limit the rate and number of MFA prompts. For example, set a threshold to only allow a maximum of 3 MFA push requests within a 5-minute window for a single user. After this threshold is met, the account should be temporarily locked, and an alert should be sent to the security team and the user via a separate channel (e.g., email). This technical control prevents the attacker from overwhelming the user with notifications and provides a clear, high-fidelity signal of an attack in progress, allowing for a rapid response.
Lapsus$ has repeatedly demonstrated its ability to exploit weak processes at IT help desks. Organizations must harden these processes. Implement a 'no exceptions' policy for identity verification. For sensitive actions like a password reset or MFA device change for a privileged user, require multi-channel verification. For example, the help desk agent must initiate a video call to visually confirm the user's identity or use a pre-registered alternate phone number. Remove social-media-based or knowledge-based questions (e.g., 'What was your first car?') as verification methods, as this information is often publicly available and used by Lapsus$ for social engineering.

Cybersecurity professional with over 10 years of specialized experience in security operations, threat intelligence, incident response, and security automation. Expertise spans SOAR/XSOAR orchestration, threat intelligence platforms, SIEM/UEBA analytics, and building cyber fusion centers. Background includes technical enablement, solution architecture for enterprise and government clients, and implementing security automation workflows across IR, TIP, and SOC use cases.
Help others stay informed about cybersecurity threats