Lumma Stealer turns one careless click on a fake CAPTCHA or cracked download into a bundle of passwords, session cookies and tokens that someone else can use to sign in as your staff and services. Europol called it "the world's most significant infostealer threat" in 2025; it survived a coordinated Microsoft, US Department of Justice and Europol disruption in May 2025, and was back at normal volumes within weeks. This guide profiles Lumma specifically: who runs it, how it is delivered, what it takes, how stolen sessions are reused, and the endpoint and identity controls that blunt it. It builds on the Infostealer Threat Guide, which covers the stealer economy as a whole, and is written for SOC, endpoint and identity teams.
Key takeaways
- Lumma is a service, not a single attacker. Microsoft tracks the developer as Storm-2477 and has seen ransomware-linked actors including Octo Tempest and Storm-1607 among its customers, so a Lumma infection can lead anywhere.
- Delivery relies on the user running it. Fake CAPTCHA pages that ask users to paste a command into the Windows Run dialog, malvertising for software downloads, cracked software and GitHub-hosted lures account for most of the documented chains.
- Session cookies are the real prize. ATT&CK records Lumma stealing browser cookies and two-factor authentication extension data, which lets attackers replay a signed-in session and skip MFA entirely.
- Disruption bought weeks, not months. The May 2025 action took down about 2,300 domains, but Trend Micro saw targeting recover through June and July 2025 on new hosting providers.
- Treat an infection as an identity incident. Reimaging the laptop is not enough: revoke sessions, rotate every credential and token the browser and disk held, and check where they were used.
Who they are (names and aliases)
Lumma Stealer, also called LummaC2, is an information stealer sold as malware-as-a-service. MITRE ATT&CK records it as software S1213, in use since at least 2022, with captured data sold in criminal markets to initial access brokers. Microsoft's Digital Crimes Unit names the primary developer as Russia-based and using the alias "Shamel". Affiliates rent access to a panel and builder; Microsoft identified six versions and notes that affiliates can pay extra for a personal command and control (C2) domain.
| Name | Used by | Refers to |
|---|---|---|
| Lumma Stealer (S1213), LummaStealer | MITRE ATT&CK | The malware family |
| LummaC2 | US DOJ, FBI | Same family; name used in the seizure warrants |
| Storm-2477 | Microsoft | The developer and maintainer of the service |
| Water Kurita | Trend Micro | Trend Micro's name for the developer |
| Octo Tempest, Storm-1607, Storm-1113, Storm-1674 | Microsoft | Separate actors observed using Lumma, not aliases of it |
Do not confuse the customers with the developer. A report that "Octo Tempest used Lumma" says nothing about who wrote it. See the Threat Actor Groups Guide for how naming schemes differ.
Targeting and motivation
- Motivation: financial. Logs are sold or used for fraud, account takeover, cryptocurrency theft and as an entry point for ransomware.
- Scale: Microsoft identified more than 394,000 infected Windows computers worldwide between 16 March and 16 May 2025. FBI affidavits cited by the DOJ describe at least 1.7 million instances of LummaC2 stealing browser data, autofill, credentials and seed phrases.
- Victims: mostly opportunistic. Microsoft cites reports of Lumma use against manufacturing, telecommunications, logistics, finance, healthcare and education, and against gaming communities, where cracks and cheats are the lure.
- Corporate exposure through personal use: in the Snowflake customer campaign, Mandiant found infostealer infections, Lumma among them, on contractor systems also used for gaming and pirated software. The Snowflake breach shows how logs bought years later became access to about 165 customer environments that lacked MFA.
Tactics and techniques (MITRE ATT&CK)
All IDs are ATT&CK v20. Rows marked (Microsoft) describe behaviour from Microsoft's analysis mapped to the closest technique; the rest are relationships recorded against S1213.
| Stage | Technique | What sources describe | Primary defence |
|---|---|---|---|
| Delivery | T1566.001 Spearphishing Attachment; T1566.002 Spearphishing Link | Brand-impersonating emails, hotel booking and invoice themes, routed through the Prometheus traffic distribution system (Microsoft) | Mail filtering; detonation; user reporting |
| Delivery | T1583.008 Malvertising (Microsoft); T1195 Supply Chain Compromise | Search ads for downloads such as Notepad++ leading to cloned sites; cracked software bundles | Software only from a managed catalogue; DNS and web filtering |
| Execution | T1204 User Execution; T1204.004 Malicious Copy and Paste (Microsoft); T1059.001 PowerShell | Fake CAPTCHA tells the user to press Windows+R and paste a Base64-encoded PowerShell command | Restrict the Run dialog and PowerShell for standard users; ClickFix detection |
| Execution | T1204.002 Malicious File; T1218.005 Mshta; T1059.010 AutoHotKey & AutoIT | Executables in ZIP, MSI in RAR, mshta.exe and AutoIt scripts | Application control; ASR rules for downloaded content |
| Stealth | T1055.012 Process Hollowing; T1574.001 DLL; T1620 Reflective Code Loading; T1027.013 Encrypted/Encoded File | Payload hollowed into msbuild.exe, regasm.exe, regsvcs.exe, explorer.exe or BitLockerToGo.exe | EDR in block mode; alert on these binaries making outbound connections |
| Defence impairment | T1685 Disable or Modify Tools; T1553.002 Code Signing | AMSI bypass by removing AmsiScanBuffer from clr.dll in memory; signed binaries | Tamper protection; certificate reputation, not signature alone |
| Credential access | T1555.003 Credentials from Web Browsers; T1539 Steal Web Session Cookie; T1217 Browser Information Discovery | Passwords, cookies, autofill from Chromium and Gecko browsers; 2FA extension data | Device-bound sessions; no saved passwords in browsers on admin devices |
| Persistence | T1547.001 Registry Run Keys; T1176.001 Browser Extensions | HKCU Run key; malicious extension for Chrome, Edge, Opera and Brave | Extension allowlisting; Run key monitoring |
| Collection and C2 | T1119 Automated Collection; T1113 Screen Capture; T1071.001 Web Protocols; T1102.001 Dead Drop Resolver (Microsoft); T1041 Exfiltration Over C2 Channel | Wallets, .ovpn files, email, FTP and Telegram data, documents; HTTPS C2 behind Cloudflare; fallback addresses on Telegram then Steam profiles | Egress inspection; block newly registered domains |
For the paste-and-run delivery pattern in depth, see the ClickFix and Fake CAPTCHA Paste-and-Run Attacks Guide.
How they abuse identities and credentials
Lumma is a credential collection tool. What makes it dangerous to organisations is that a browser on a work laptop holds much more than passwords.
- Session cookies: a stolen cookie for a SaaS app or identity provider can be replayed (ATT&CK T1550.004 Web Session Cookie) from another machine, already past MFA. Short session lifetimes, re-authentication for sensitive actions and device binding limit the window. See the Session Hijacking and Cookie Theft Guide.
- Cloud and SaaS accounts: saved passwords for cloud consoles, data platforms and admin portals become T1078.004 Cloud Accounts abuse when MFA is missing, as Snowflake showed.
- Non-human credentials on developer machines: stealers collect documents and files, and a developer workstation often holds API keys, cloud access keys, VPN profiles and tokens in plain files. These credentials do not expire with the user's session and are rarely covered by MFA. See the Infostealer Logs and Session Token Abuse Guide.
- Resale: logs reach initial access brokers (ATT&CK T1650 Acquire Access for the buyer). Mandiant found that at least 79.7 per cent of accounts used in the Snowflake campaign had prior credential exposure, some dating back to November 2020: old logs stay useful as long as nobody rotates.
Notable incidents
| Event | Date | What is public |
|---|---|---|
| Snowflake customer campaign (UNC5537) | 2024 | Mandiant lists Lumma with Vidar, RisePro, RedLine, Raccoon and META as sources of the credentials used against customer tenants without MFA. |
| Microsoft civil action | Filed 13 May 2025 | Filed in the US District Court for the Northern District of Georgia; about 2,300 domains seized, suspended or blocked; more than 1,300 redirected to Microsoft sinkholes, including 300 actioned by law enforcement with Europol support. |
| DOJ seizure | 19 to 21 May 2025 | Five domains hosting the LummaC2 user panels seized, including three replacements the operators set up on 20 May. |
| Europol coordination | May 2025 | EC3 coordinated European law enforcement and called Lumma "the world's most significant infostealer threat"; Japan's JC3 also took part. |
| Resurgence | June to July 2025 | Trend Micro saw account targeting return to usual levels, hosting shifted from Cloudflare to other providers including Selectel, and lures spread through GitHub, YouTube, Google Sites and Facebook. |
The lesson for defenders: takedowns reset infrastructure, not the credentials already stolen. Logs collected before May 2025 remained valid wherever passwords and tokens were not rotated.
Detection and defence
Detection signals
| Signal | Where to look | Notes |
|---|---|---|
| New entries in HKCU\Software\Microsoft\Windows\CurrentVersion\Explorer\RunMRU containing powershell, mshta or encoded strings | EDR registry telemetry | Microsoft publishes a RunMRU hunting query for ClickFix |
| explorer.exe spawning powershell.exe with -enc or long Base64 arguments | Process creation (Sysmon event 1 or Security event 4688 with command line) | Classic paste-and-run trace |
| msbuild.exe, regasm.exe, regsvcs.exe or BitLockerToGo.exe making outbound HTTPS connections | EDR network events | Process hollowing hosts |
| Non-browser process reading browser Login Data or Cookies files | EDR file access | Core stealer behaviour |
| Traffic to Steam profiles or Telegram from non-user processes | Proxy and DNS logs | Fallback C2 lookup |
| Same session token or cookie used from a new IP, ASN or device | Identity provider and SaaS sign-in logs | Post-theft replay; often the first sign you see |
| Defender detections such as Trojan:Win32/LummaStealer, Trojan:HTML/FakeCaptcha, Behavior:Win32/ClickFix | Antivirus and XDR alerts | Treat every hit as possible credential loss, even if blocked late |
Prevention, in rollout order
- Endpoint baseline: enable tamper protection, network and web protection, and EDR in block mode, as Microsoft recommends for Lumma.
- Attack surface reduction rules: start in audit mode for two to four weeks, review hits, then enforce. Microsoft lists the rules for executables that do not meet prevalence, age or trusted-list criteria, potentially obfuscated scripts, JavaScript or VBScript launching downloaded executables, and use of copied or impersonated system tools. Roll back a single rule to audit if it breaks a business application.
- Restrict paste-and-run: limit PowerShell for standard users through application control (AppLocker or WDAC) and constrained language mode, and consider removing the Run dialog by policy for users who do not need it.
- Software sourcing: block installs outside a managed catalogue and filter malvertising and newly registered domains at DNS.
- Browser controls: allowlist extensions, disable the built-in password manager on managed profiles where an enterprise password manager exists, and separate admin browsing onto privileged access workstations.
- Identity controls: phishing-resistant MFA, Conditional Access authentication strength for critical apps, and token binding where available. Microsoft Entra Token Protection is generally available for native apps on Windows, macOS and iOS and in preview for some browser scenarios; pilot it in report-only mode first. See the Token and Session Security Guide.
Response when Lumma is found
- Isolate the host and capture the EDR timeline for the infection window.
- List every account, SaaS session, VPN profile, wallet and file-based secret present on the device.
- Revoke refresh tokens and sessions for the user in the identity provider and in key SaaS apps, then reset passwords.
- Rotate API keys, cloud access keys and tokens found on disk, and check their recent use in cloud and SaaS audit logs.
- Reimage, then watch the user's accounts for replay from new locations for at least 30 days.
Decision guidance
- Small organisations: standard users without local admin, a managed browser with extension allowlisting, and MFA everywhere give most of the benefit; consider an infostealer log monitoring service rather than building one.
- Large organisations: invest in session-replay detection at the identity provider and automated token revocation from EDR alerts; that closes the gap between infection and abuse.
- Unmanaged and personal devices: block them from admin portals and data platforms, or require device compliance, because Lumma infections often start on home machines.
Metrics
- Time to revoke: minutes from stealer alert to session and token revocation (target: under one hour).
- Exposure rate: corporate credentials seen in stealer logs per month, and percentage rotated within 24 hours.
- Control coverage: percentage of endpoints with ASR rules in block mode and tamper protection on.
- Session binding: percentage of sign-ins to critical apps from compliant or token-protected devices.
- Repeat infection: number of users infected more than once in a quarter.
Framework mapping
| Control area | NIST CSF 2.0 | NIST SP 800-53 Rev. 5 | MITRE ATT&CK addressed |
|---|---|---|---|
| Malware protection on endpoints | DE.CM-09 | SI-3 | T1204, T1055.012 |
| Authentication and re-authentication | PR.AA-03 | IA-2, IA-11 | T1078.004 |
| Session protection and termination | PR.AA-03 | SC-23, AC-12 | T1539, T1550.004 |
| Eradication including credential rotation | RS.MI-02 | SI-3 | T1555.003 |
Practitioner checklist
- Hunt for RunMRU entries and explorer.exe launching encoded PowerShell across the estate.
- Enforce ASR rules for obfuscated scripts and downloaded executables after an audit period.
- Block software installs outside a managed catalogue and filter malvertising domains.
- Allowlist browser extensions and keep saved passwords out of browsers on admin devices.
- Require phishing-resistant MFA and device compliance for cloud consoles and data platforms.
- Pilot token binding such as Entra Token Protection in report-only mode for high-value users.
- Write a stealer playbook that revokes sessions and rotates file-based secrets, not just reimages.
- Subscribe to stealer log monitoring and rotate any exposed credential within 24 hours.
Standards and references
- MITRE ATT&CK: Lumma Stealer (S1213)
- Microsoft Threat Intelligence: Lumma Stealer, Breaking Down the Delivery Techniques and Capabilities
- US Department of Justice: Justice Department Seizes Domains Behind Major Information-Stealing Malware Operation
- Microsoft: Disrupting Lumma Stealer
- Europol: Europol and Microsoft Disrupt World's Largest Infostealer Lumma
- Microsoft Learn: Token Protection in Microsoft Entra Conditional Access
- Trend Micro: Lumma Stealer Returns
- Google Cloud Mandiant: UNC5537 Targets Snowflake Customer Instances
Related NHI Mgmt Group resources: Infostealer Threat Guide · Infostealer Logs and Session Token Abuse Guide · Session Hijacking and Cookie Theft Guide