ESET has collaborated with Microsoft, BitSight, Lumen, Cloudflare, CleanDNS, and GMO Registry in a worldwide disruption operation in opposition to Lumma Stealer, an notorious malware-as-a-service (MaaS) infostealer. The operation focused Lumma Stealer infrastructure with all identified C&C servers previously yr, rendering the exfiltration community, or a big a part of it, nonoperational.
Key factors of this blogpost:
- ESET took half in a coordinated international operation to disrupt Lumma Stealer.
- ESET supplied technical evaluation and statistical info, and extracted important knowledge from tens of hundreds of malware samples.
- We offer an outline of the Lumma Stealer MaaS ecosystem.
- We additionally present technical evaluation and an outline of the evolution of Lumma Stealer’s key static and dynamic properties, which had been vital to the disruption effort.
Disruption contribution
ESET automated techniques processed tens of hundreds of Lumma Stealer samples, dissecting them to extract key parts, comparable to C&C servers and affiliate identifiers. This allowed us to constantly monitor Lumma Stealer’s exercise, monitor growth updates, cluster associates, and extra.
Infostealer malware households, like Lumma Stealer, are sometimes only a foreshadowing of a future, far more devastating assault. Harvested credentials are a valued commodity within the cybercrime underground, offered by preliminary entry brokers to numerous different cybercriminals, together with ransomware associates. Lumma Stealer has been one of the prevalent infostealers over the previous two years, and ESET telemetry (see Determine 1) confirms that it has left no a part of the world untouched.

Lumma Stealer builders had been actively creating and sustaining their malware. Now we have commonly seen code updates starting from minor bug fixes to finish substitute of string encryption algorithms and modifications to the community protocol. The operators additionally actively maintained the shared exfiltration community infrastructure. Between June 17th, 2024 and Might 1st, 2025, we noticed a complete of three,353 distinctive C&C domains, averaging roughly 74 new domains rising every week together with occasional updates to Telegram-based dead-drop resolvers (see Determine 2). We talk about the small print of the community infrastructure later within the blogpost.

This ongoing evolution underscores the numerous menace posed by Lumma Stealer and highlights the significance and complexity of the disruption effort.
Background
Over the previous two years, Lumma Stealer (also referred to as LummaC or LummaC2) has emerged as one of the lively infostealers within the cybercrime ecosystem, changing into a popular instrument amongst cybercriminals as a consequence of its lively growth of malware options and its infrastructure being offered as a service.
Malware as a service
Lumma Stealer adopts the idea of malware as a service (MaaS), the place associates pay a month-to-month price, based mostly on their tier, to obtain the newest malware builds and the community infrastructure obligatory for knowledge exfiltration. Associates have entry to a administration panel with a user-friendly interface the place they’ll obtain exfiltrated knowledge and harvested credentials.
The tiered subscription mannequin ranges from USD 250 to USD 1,000 per 30 days, every with more and more refined options. Decrease tiers embody fundamental filtering and log obtain choices, whereas greater tiers supply customized knowledge assortment, evasion instruments, and early entry to new options. The costliest plan emphasizes stealth and adaptableness, providing distinctive construct era and decreased detection.
The operators of Lumma Stealer have additionally created a Telegram market with a ranking system for associates to promote stolen knowledge with out intermediaries. {The marketplace} has been properly documented in Cybereason analysis. Furthermore, they keep public documentation of the administration panel for associates and periodically share updates and fixes on hacking boards, as proven in Determine 3.

Open documentation not solely helps associates with much less expertise to make use of the malware service, but in addition gives invaluable insights for safety researchers. Builders give attention to malware builds, knowledge pipelining, and infrastructure upkeep, whereas associates are answerable for distributing the malware. This info, mixed with the service’s reputation, ends in all kinds of compromise vectors.
Frequent distribution strategies embody phishing, cracked software program, and different malware downloaders together with SmokeLoader, DarkGate, Amadey, Vidar, and others. Fashionable phishing schemes contain ClickFix or pretend CAPTCHA net pages, fraudulent boards with cracked software program, pretend GitHub repositories, fraudulent hyperlinks on Reddit boards, and lots of extra.
Technical evaluation
Quite a few public analyses have already been written about Lumma Stealer and its compromise vectors. Our focus right here, nevertheless, is on the elements related to the disruption. On this part, we’ll briefly introduce the important thing static and dynamic properties that we’ve been actively extracting from Lumma Stealer.
Static properties of Lumma Stealer
Numerous info comes embedded in Lumma Stealer malware samples. This naturally presents a super goal for automated extraction. Apart from the apparent knowledge of curiosity – C&C server domains – the samples additionally include identifier strings that tie the pattern to a particular affiliate and a marketing campaign, and an optionally available identifier resulting in a customized dynamic configuration. These identifiers are utilized in community communication with the C&C server throughout knowledge exfiltration and requests for dynamic configuration. Within the sections under, we take a look at these properties in depth.
C&C domains
Every Lumma Stealer pattern accommodates an inventory of 9 encrypted C&C domains. Whereas the encryption strategies have advanced over time, the attribute array construction has remained constant as much as the time of writing.
Primarily based on Lumma Stealer’s inside pattern versioning, which is closely protected by stack string obfuscation, we all know that up till January 2025, the C&C domains within the samples had been protected by an XOR operate and base64 encoding (see Determine 4). When the base64-encoded string was decoded, it revealed a construction the place the primary 32 bytes served as an XOR key, and the remaining bytes contained the encrypted C&C area.

In January 2025, Lumma Stealer transitioned the safety of the C&C listing to ChaCha20 encryption with a single hardcoded key and nonce (see Determine 5). This safety of the C&C listing within the Lumma Stealer binaries has remained the identical up till the time of publication.

Useless-drop resolvers
Since June 2024, every Lumma Stealer construct got here with a brand new characteristic for acquiring a backup C&C. If no C&C server from the static config responds to Lumma Stealer, then the backup C&C is extracted from a dummy Steam profile net web page appearing as a dead-drop resolver. The Steam profile URL is closely protected within the binary, the identical method because the model string. The encrypted backup C&C URL is ready within the Steam profile identify, as proven in Determine 6, and the safety is an easy Caesar cipher (ROT11).

In February 2025, Lumma Stealer acquired an replace that included a characteristic for acquiring a brand new, major C&C URL from a Telegram channel dead-drop resolver. The C&C URL is extracted from the Telegram channel’s title subject, and it’s protected by the identical algorithm as within the case of the Steam profile dead-drop resolver. The primary distinction within the utilization of the Telegram and Steam profile dead-drop resolvers is that the Telegram choice is examined first, whereas the Steam profile is used as a final resort if profitable communication has not been established with beforehand obtained C&C servers (Determine 16).
Furthermore, we imagine that the Telegram dead-drop resolver is accessible for greater tier subscriptions. It’s because many samples would not have the Telegram URL set, and due to this fact the malware skips this technique.
Lumma Stealer identifier
Every Lumma Stealer pattern accommodates a singular hardcoded affiliate identifier generally known as LID. It’s embedded in plaintext type and utilized for communication with C&C servers. Up till March 2025, the LID parameter string adopted a structured format, delimited by two dashes (Determine 7). A detailed evaluation of the LID affiliate string is supplied in an upcoming part.

Though probably the most prevalent LID noticed throughout our monitoring begins with the string uz4s1o; the second commonest LID, which begins with LPnhqo, gives a greater instance for visualizing typical LID variability. Within the phrase cloud in Determine 8, we current the highest 200 LIDs collected throughout our monitoring, beginning with LPnhqo.

Nevertheless, in early March 2025, Lumma Stealer transitioned to utilizing hexadecimal identifiers, referred to internally as UID (see Determine 9).

Non-obligatory configuration identifier
Along with the LID parameter, Lumma Stealer samples may include an optionally available parameter referred to internally as J. When current, this parameter is in cleartext and formatted as a 32-byte ASCII hex string (see Determine 10). The J parameter is utilized within the C&C request for dynamic configuration with extra definitions for exfiltration. We speak about dynamic configuration in additional element in a following part.

If the J parameter is lacking within the Lumma Stealer pattern, an empty string is used within the C&C request and a default configuration is retrieved. Not like LID, the J parameter isn’t current in Lumma Stealer samples. Nevertheless, it performs a vital position when current, because it permits retrieving a dynamic configuration that considerably will increase the stealer’s capabilities, making it a extra versatile exfiltration instrument for menace actors.
In March 2025, when the LID parameter was renamed to UID and its format modified, the J parameter was renamed to CID however with no change to its format or operate.
Evaluation of static properties
From our long-term monitoring and statistical evaluation of LID parameters, we imagine that the primary phase of the LID identifies the affiliate, whereas the second phase differentiates between campaigns. Primarily based on this assumption you possibly can see the highest 200 affiliate identifiers in Determine 11.

Furthermore, we’ve been in a position to create a visualization of the associates’ actions over the previous yr (see Determine 12). This visualization highlights per week in January 2025. These kinds of visualizations have supplied us with invaluable insights into the patterns and behaviors of various menace actors. Moreover, the visualizations reveal a shared, domain-based C&C infrastructure amongst most Lumma Stealer associates. On the identical time, we had been in a position to determine much less regularly used C&C domains, which we suspect have been reserved for greater tier associates or extra essential campaigns.

Dynamic properties of Lumma Stealer
Lumma Stealer retrieves a dynamic configuration from the C&C server, which accommodates definitions specifying what to scan for exfiltration (see Desk 1). The first focus is on stealing net browser extension knowledge and databases containing passwords, session cookies, net searching historical past, and autofill knowledge. Apart from net browsers, it additionally focuses on stealing knowledge from password managers, VPNs, FTP purchasers, cloud providers, distant desktop functions, e mail purchasers, cryptocurrency wallets, and note-taking functions.
Desk 1. Dynamic config’s JSON fields
Key | Description |
v | Dynamic config model. |
se | Choice for taking a screenshot of the sufferer’s machine for exfiltration. |
ex | Checklist of Chromium-based browser extensions to focus on for exfiltration. Every entry consists of: · The extension ID, saved as en. · The extension identify, saved as ez. |
c | Definition of information focused for exfiltration. Essentially the most fascinating entries are: · The trail for file scanning, saved as p. · The file extension listing filter for exfiltration, saved as m. · The utmost folder scanning depth, saved as d. · The utmost file dimension for exfiltration, saved as fs. |
Although we haven’t seen important modifications within the default configurations, this characteristic enhances the malware’s capability to carry out focused exfiltration (see Determine 13). A complete overview of the configuration fields has already been properly documented on this analysis by SpyCloud.

The configuration is in JSON format, and it’s downloaded from the C&C server utilizing an HTTPS POST request that features the LID identifier, optionally available J parameter, and a particular hardcoded Consumer-Agent string.
The safety of the dynamic configuration has modified a couple of instances not too long ago. Previously, it was protected in the identical method because the static C&C listing, by a 32-byte XOR operate and base64 encoding. In March 2025 the safety modified to ChaCha20, the place the important thing and nonce had been prepended to the encrypted configuration.
The Consumer-Agent string is essential to observe, as offering it accurately is important for receiving the dynamic configuration. In April 2025, Lumma Stealer launched a further layer of obfuscation by encrypting JSON values utilizing an 8-byte XOR operate (see Determine 14).

This encrypted variant of the dynamic configuration is delivered when a barely up to date Consumer-Agent string is specified (see Desk 2).
Desk 2. Consumer-Agent variants
Consumer-Agent | Description |
Mozilla/5.0 (Home windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/119.0.0.0 Safari/537.36 | Previous Consumer-Agent string leading to a dynamic configuration variant proven in Determine 13. |
Mozilla/5.0 (Home windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/109.0.0.0 Safari/537.36 | New Consumer-Agent string leading to a dynamic configuration variant with encryption of some values (Determine 14). |
Apart from this dynamic configuration method, Lumma Stealer samples nonetheless include hardcoded directions for exfiltrating information. These embody knowledge from functions comparable to Outlook or Thunderbird, Steam account info, and Discord account tokens (see this SpyCloud blogpost). This mixture of dynamic and hardcoded configurations ensures that Lumma Stealer can successfully acquire a variety of invaluable knowledge.
To summarize all of the static and dynamic modifications talked about thus far, we’ve created a timeline (Determine 15) highlighting probably the most important developments noticed within the Lumma Stealer malware over the previous yr.

C&C communication
All through our Lumma Stealer monitoring interval, all extracted C&C domains persistently led to Cloudflare providers, that are utilized to hide Lumma Stealer’s actual C&C infrastructure. Cloudflare providers are additionally employed for C&C servers situated through dead-drop resolvers.
First, Lumma Stealer must receive an lively C&C server. The mechanism of this alternative is illustrated within the circulation chart proven in Determine 16.

Handshake
Though the precise handshake request to the C&C server will not be current within the newest Lumma Stealer builds, it’s price mentioning as a result of it was a characteristic of our monitoring for a very long time. The handshake request was an HTTPS POST request containing act=stay and a hardcoded Consumer-Agent. Energetic servers responded with a cleartext okay message.
Configuration request
When Lumma Stealer identifies an lively C&C server, it requests the configuration through an HTTPS POST request (Determine 17), which incorporates the LID and J parameters as knowledge. If the J parameter will not be current within the pattern, Lumma Stealer retrieves the default configuration from the C&C server. This configuration specifies what to scan for exfiltration, permitting the malware to adapt to completely different targets and environments.
Further payload execution
After Lumma Stealer efficiently exfiltrates delicate knowledge and harvested credentials, it points one remaining HTTPS POST request to the C&C server – this time, with a further sufferer {hardware} ID known as hwid. This remaining request retrieves a configuration of a further payload to be executed on the sufferer’s machine. The payload or a URL to obtain from is a part of that configuration. Notice that such a payload will not be at all times supplied.

Anti-analysis obfuscation strategies
Lumma Stealer employs a couple of, however efficient, anti-emulation strategies to make evaluation as sophisticated as doable. These strategies are designed to evade detection and hinder the efforts of safety analysts.
Oblique leap obfuscation
One of many major obfuscation strategies utilized by Lumma Stealer is oblique management circulation flattening, proven in Determine 18. This technique successfully disrupts the code blocks of the capabilities, making it practically inconceivable to maintain monitor of the operate logic. By flattening the management circulation, the malware obfuscates its operations, complicating the evaluation course of. For an in depth exploration of this system and thorough evaluation of those obfuscation patterns, together with a top level view of the answer, you possibly can confer with this complete article by Mandiant.

Stack strings
One other approach employed by Lumma Stealer is the usage of encrypted stack strings, as illustrated in Determine 19. This technique successfully hides binary knowledge and lots of essential strings within the Lumma Stealer pattern, making static evaluation of the binary tough. Furthermore, every encrypted string has its personal distinctive mathematical operate for decryption, including one other layer of complexity to the evaluation course of.

Import API obfuscation
In Lumma Stealer, imports are resolved at runtime. Import names are hashed utilizing the FNV-1a algorithm with every construct utilizing a customized offset foundation. As proven in Determine 20, since August 25th, 2024, Lumma Stealer additionally obfuscates the FNV hash algorithm parameters through the use of stack strings.

Conclusion
This international disruption operation was made doable by our long-term monitoring of Lumma Stealer, which we’ve supplied an outline of on this blogpost. Now we have described the modus operandi of the Lumma Stealer group and its service. Moreover, we’ve documented the essential static identifiers and C&C communication in addition to its evolution during the last yr. Lastly, we summarized the important thing obfuscation strategies that make the evaluation of Lumma Stealer difficult.
The disruption operation, led by Microsoft, goals to grab all identified Lumma Stealer C&C domains, rendering Lumma Stealer’s exfiltration infrastructure nonfunctional. ESET will proceed to trace different infostealers whereas intently monitoring for Lumma Stealer exercise following this disruption operation.
For any inquiries about our analysis revealed on WeLiveSecurity, please contact us at threatintel@eset.com.ESET Analysis presents non-public APT intelligence experiences and knowledge feeds. For any inquiries about this service, go to the ESET Risk Intelligence web page.
IoCs
SHA-1
Filename
Detection
Description
6F94CFAABB19491F2B8E 719D74AD032D4BEB3F29
AcroRd32.exe
Win32/Spy.Lumma Stealer.B
Lumma Stealer pattern – Construct 2024-06-27.
C5D3278284666863D758 7F1B31B06F407C592AC4
Notion.exe
Win32/Spy.Lumma Stealer.B
Lumma Stealer pattern – Construct 2024-07-14.
5FA1EDC42ABB42D54D98 FEE0D282DA453E200E99
explorer.exe
Win32/Spy.Lumma Stealer.B
Lumma Stealer pattern – Construct 2024-08-08.
0D744811CF41606DEB41 596119EC7615FFEB0355
aspnet_regiis .exe
Win32/Spy.Lumma Stealer.B
Lumma Stealer pattern – Construct 2024-08-25.
2E3D4C2A7C68DE2DD31A 8E0043D9CF7E7E20FDE1
nslookup.exe
Win32/Spy.Lumma Stealer.B
Lumma Stealer pattern – Construct 2024-09-20.
09734D99A278B3CF59FE 82E96EE3019067AF2AC5
nslookup.exe
Win32/Spy.Lumma Stealer.B
Lumma Stealer pattern – Construct 2024-10-04.
1435D389C72A5855A5D6 655D6299B4D7E78A0127
BitLockerToGo .exe
Win32/Spy.Lumma Stealer.B
Lumma Stealer pattern – Construct 2024-11-09.
2CCCEA9E1990D6BC7755 CE5C3B9B0E4C9A8F0B59
exterior.exe
Win32/Spy.Lumma Stealer.B
Lumma Stealer pattern – Construct 2024-12-23.
658550E697D9499DB782 1CBBBF59FFD39EB59053
Wemod-Premium-Unlocker-2025
MSIL/GenKryptik.HGWU
Lumma Stealer pattern – Construct 2025-01-18.
070A001AC12139CC1238 017D795A2B43AC52770D
khykuQw.exe
Win32/Kryptik.HYUC
Lumma Stealer pattern – Construct 2025-02-27.
1FD806B1A0425340704F 435CBF916B748801A387
Begin.exe
Win64/Injector.WR
Lumma Stealer pattern – Construct 2025-03-24.
F4840C887CAAFF0D5E07 3600AEC7C96099E32030
loader.exe
Win64/Kryptik.FAZ
Lumma Stealer pattern – Construct 2025-04-15.
8F58C4A16717176DFE3C D531C7E41BEF8CDF6CFE
Set-up.exe
Win32/Spy.Lumma Stealer.B
Lumma Stealer pattern – Construct 2025-04-23.
Community
IP | Area | Internet hosting supplier | First seen | Particulars |
172.67.134[.]100 | cooperatvassquaidmew[.]xyz | Cloudflare, Inc. | 2024‑06‑27 | Lumma Stealer C&C server. |
172.67.175[.]165 | crisisrottenyjs[.]xyz | Cloudflare, Inc. | 2024‑06‑27 | Lumma Stealer C&C server. |
188.114.96[.]1 | deadtrainingactioniw[.]xyz tamedgeesy[.]sbs nighetwhisper[.]prime |
Cloudflare, Inc. | 2024‑06‑27 | Lumma Stealer C&C server. |
172.67.141[.]43 | exuberanttjdkwo[.]xyz | Cloudflare, Inc. | 2024‑06‑27 | Lumma Stealer C&C server. |
188.114.96[.]3 | grandcommonyktsju[.]xyz | Cloudflare, Inc. | 2024‑06‑27 | Lumma Stealer C&C server. |
104.21.92[.]96 | qualificationjdwko[.]xyz | Cloudflare, Inc. | 2024‑06‑27 | Lumma Stealer C&C server. |
172.67.209[.]200 | sweetcalcutangkdow[.]xyz | Cloudflare, Inc. | 2024‑06‑27 | Lumma Stealer C&C server. |
104.21.49[.]80 | wordingnatturedowo[.]xyz | Cloudflare, Inc. | 2024‑06‑27 | Lumma Stealer C&C server. |
188.114.97[.]0 | bigmouthudiop[.]store froytnewqowv[.]store locatedblsoqp[.]store stagedchheiqwo[.]store |
Cloudflare, Inc. | 2024‑07‑16 | Lumma Stealer C&C server. |
104.21.19[.]156 | callosallsaospz[.]store | Cloudflare, Inc. | 2024‑07‑18 | Lumma Stealer C&C server. |
172.67.153[.]40 | indexterityszcoxp[.]store | Cloudflare, Inc. | 2024‑07‑18 | Lumma Stealer C&C server. |
172.67.192[.]52 | lariatedzugspd[.]store | Cloudflare, Inc. | 2024‑07‑18 | Lumma Stealer C&C server. |
172.67.213[.]85 | liernessfornicsa[.]store | Cloudflare, Inc. | 2024‑07‑18 | Lumma Stealer C&C server. |
172.67.137[.]78 | outpointsozp[.]store | Cloudflare, Inc. | 2024‑07‑18 | Lumma Stealer C&C server. |
172.67.221[.]214 | shepherdlyopzc[.]store | Cloudflare, Inc. | 2024‑07‑18 | Lumma Stealer C&C server. |
172.67.204[.]158 | unseaffarignsk[.]store | Cloudflare, Inc. | 2024‑07‑18 | Lumma Stealer C&C server. |
172.67.178[.]194 | upknittsoappz[.]store | Cloudflare, Inc. | 2024‑07‑18 | Lumma Stealer C&C server. |
188.114.97[.]3 | bassizcellskz[.]store byteplusx[.]digital sparkiob[.]digital longitudde[.]digital |
Cloudflare, Inc. | 2024‑08‑07 | Lumma Stealer C&C server. |
104.21.47[.]141 | celebratioopz[.]store | Cloudflare, Inc. | 2024‑08‑07 | Lumma Stealer C&C server. |
172.67.158[.]159 | complaintsipzzx[.]store | Cloudflare, Inc. | 2024‑08‑07 | Lumma Stealer C&C server. |
172.67.204[.]20 | deallerospfosu[.]store | Cloudflare, Inc. | 2024‑08‑07 | Lumma Stealer C&C server. |
104.21.35[.]48 | languagedscie[.]store | Cloudflare, Inc. | 2024‑08‑07 | Lumma Stealer C&C server. |
104.21.73[.]43 | mennyudosirso[.]store | Cloudflare, Inc. | 2024‑08‑07 | Lumma Stealer C&C server. |
188.114.97[.]9 | quialitsuzoxm[.]store | Cloudflare, Inc. | 2024‑08‑07 | Lumma Stealer C&C server. |
172.67.166[.]231 | writerospzm[.]store | Cloudflare, Inc. | 2024‑08‑07 | Lumma Stealer C&C server. |
104.21.16[.]180 | caffegclasiqwp[.]store | Cloudflare, Inc. | 2024‑08‑24 | Lumma Stealer C&C server. |
172.67.146[.]35 | condedqpwqm[.]store | Cloudflare, Inc. | 2024‑08‑24 | Lumma Stealer C&C server. |
N/A | evoliutwoqm[.]store | N/A | 2024‑08‑24 | Lumma Stealer C&C server. |
188.114.96[.]0 | millyscroqwp[.]store stamppreewntnq[.]store advennture[.]prime |
Cloudflare, Inc. | 2024‑08‑24 | Lumma Stealer C&C server. |
104.21.67[.]155 | traineiwnqo[.]store | Cloudflare, Inc. | 2024‑08‑24 | Lumma Stealer C&C server. |
94.140.14[.]33 | achievenmtynwjq[.]store carrtychaintnyw[.]store chickerkuso[.]store metallygaricwo[.]store milldymarskwom[.]store opponnentduei[.]store puredoffustow[.]store quotamkdsdqo[.]store bemuzzeki[.]sbs exemplarou[.]sbs exilepolsiy[.]sbs frizzettei[.]sbs invinjurhey[.]sbs isoplethui[.]sbs laddyirekyi[.]sbs wickedneatr[.]sbs |
Cloudflare, Inc. | 2024‑09‑21 | Lumma Stealer C&C server. |
188.114.97[.]4 | usseorganizedw[.]store bellflamre[.]click on tripfflux[.]world |
Cloudflare, Inc. | 2024‑09‑24 | Lumma Stealer C&C server. |
104.21.44[.]84 | beerishint[.]sbs | Cloudflare, Inc. | 2024‑10‑06 | Lumma Stealer C&C server. |
104.21.64[.]84 | 1212tank.activitydmy[.]icu | Cloudflare, Inc. | 2024‑11‑12 | Lumma Stealer C&C server. |
104.21.93[.]246 | brownieyuz[.]sbs | Cloudflare, Inc. | 2024‑11‑08 | Lumma Stealer C&C server. |
172.67.189[.]210 | ducksringjk[.]sbs | Cloudflare, Inc. | 2024‑11‑08 | Lumma Stealer C&C server. |
172.67.146[.]64 | explainvees[.]sbs | Cloudflare, Inc. | 2024‑11‑08 | Lumma Stealer C&C server. |
104.21.90[.]226 | relalingj[.]sbs | Cloudflare, Inc. | 2024‑11‑08 | Lumma Stealer C&C server. |
104.21.14[.]17 | repostebhu[.]sbs | Cloudflare, Inc. | 2024‑11‑08 | Lumma Stealer C&C server. |
172.67.192[.]43 | rottieud[.]sbs | Cloudflare, Inc. | 2024‑11‑08 | Lumma Stealer C&C server. |
188.114.97[.]1 | thinkyyokej[.]sbs | Cloudflare, Inc. | 2024‑11‑08 | Lumma Stealer C&C server. |
188.114.97[.]7 | bashfulacid[.]lat tentabatte[.]lat |
Cloudflare, Inc. | 2024‑12‑23 | Lumma Stealer C&C server. |
104.21.86[.]54 | curverpluch[.]lat | Cloudflare, Inc. | 2024‑12‑23 | Lumma Stealer C&C server. |
104.21.66[.]86 | lev‑tolstoi[.]com | Cloudflare, Inc. | 2024‑12‑17 | Lumma Stealer C&C server. |
172.64.80[.]1 | manyrestro[.]lat toppyneedus[.]biz |
Cloudflare, Inc. | 2024‑12‑23 | Lumma Stealer C&C server. |
188.114.97[.]2 | shapestickyr[.]lat | Cloudflare, Inc. | 2024‑12‑23 | Lumma Stealer C&C server. |
172.67.192[.]247 | slipperyloo[.]lat | Cloudflare, Inc. | 2024‑12‑23 | Lumma Stealer C&C server. |
104.105.90[.]131 | steamcommunity[.]com steamcommunity[.]com |
Akamai Applied sciences, Inc. | 2024‑06‑27 | Steam profile lifeless‑drop resolvers. |
172.67.146[.]68 | talkynicer[.]lat | Cloudflare, Inc. | 2024‑12‑23 | Lumma Stealer C&C server. |
172.67.184[.]241 | wordyfindy[.]lat | Cloudflare, Inc. | 2024‑12‑23 | Lumma Stealer C&C server. |
N/A | beevasyeip[.]bond | N/A | 2025‑01‑22 | Lumma Stealer C&C server. |
N/A | broadecatez[.]bond | N/A | 2025‑01‑22 | Lumma Stealer C&C server. |
N/A | encirelk[.]cyou | N/A | 2025‑01‑28 | Lumma Stealer C&C server. |
N/A | granystearr[.]bond | N/A | 2025‑01‑22 | Lumma Stealer C&C server. |
N/A | quarrelepek[.]bond | N/A | 2025‑01‑22 | Lumma Stealer C&C server. |
N/A | rockemineu[.]bond | N/A | 2025‑01‑28 | Lumma Stealer C&C server. |
104.21.19[.]91 | suggestyuoz[.]biz | Cloudflare, Inc. | 2025‑01‑22 | Lumma Stealer C&C server. |
N/A | tranuqlekper[.]bond | N/A | 2025‑01‑22 | Lumma Stealer C&C server. |
104.21.69[.]194 | codxefusion[.]prime | Cloudflare, Inc. | 2025‑02‑28 | Lumma Stealer C&C server. |
104.21.80[.]1 | earthsymphzony[.]at this time climatologfy[.]prime |
Cloudflare, Inc. | 2025‑02‑26 | Lumma Stealer C&C server. |
104.21.88[.]16 | experimentalideas[.]at this time | Cloudflare, Inc. | 2025‑03‑01 | Lumma Stealer C&C server. |
172.67.146[.]181 | gadgethgfub[.]icu | Cloudflare, Inc. | 2025‑03‑01 | Lumma Stealer C&C server. |
104.21.48[.]238 | hardrwarehaven[.]run | Cloudflare, Inc. | 2025‑02‑28 | Lumma Stealer C&C server. |
104.21.16[.]1 | hardswarehub[.]at this time pixtreev[.]run |
Cloudflare, Inc. | 2025‑02‑28 | Lumma Stealer C&C server. |
104.21.39[.]95 | quietswtreams[.]life | Cloudflare, Inc. | 2025‑02‑26 | Lumma Stealer C&C server. |
172.67.222[.]46 | socialsscesforum[.]icu | Cloudflare, Inc. | 2025‑03‑03 | Lumma Stealer C&C server. |
172.67.191[.]187 | techmindzs[.]stay | Cloudflare, Inc. | 2025‑03‑01 | Lumma Stealer C&C server. |
172.67.214[.]226 | techspherxe[.]prime | Cloudflare, Inc. | 2025‑03‑01 | Lumma Stealer C&C server. |
104.21.26[.]124 | appgridn[.]stay | Cloudflare, Inc. | 2025‑03‑24 | Lumma Stealer C&C server. |
172.67.178[.]7 | lunoxorn[.]prime | Cloudflare, Inc. | 2025‑03‑31 | Lumma Stealer C&C server. |
104.21.47[.]117 | skynetxc[.]stay | Cloudflare, Inc. | 2025‑03‑24 | Lumma Stealer C&C server. |
104.21.72[.]121 | targett[.]prime | Cloudflare, Inc. | 2025‑03‑20 | Lumma Stealer C&C server. |
188.114.96[.]2 | travewlio[.]store | Cloudflare, Inc. | 2025‑03‑20 | Lumma Stealer C&C server. |
104.21.42[.]7 | changeaie[.]prime | Cloudflare, Inc. | 2025‑04‑08 | Lumma Stealer C&C server. |
104.21.85[.]126 | clarmodq[.]prime | Cloudflare, Inc. | 2025‑04‑08 | Lumma Stealer C&C server. |
172.67.161[.]40 | liftally[.]prime | Cloudflare, Inc. | 2025‑04‑08 | Lumma Stealer C&C server. |
172.67.176[.]107 | piratetwrath[.]run | Cloudflare, Inc. | 2025‑04‑17 | Lumma Stealer C&C server. |
172.67.215[.]114 | quilltayle[.]stay | Cloudflare, Inc. | 2025‑04‑17 | Lumma Stealer C&C server. |
172.67.143[.]12 | salaccgfa[.]prime | Cloudflare, Inc. | 2025‑04‑08 | Lumma Stealer C&C server. |
104.21.5[.]146 | starofliught[.]prime | Cloudflare, Inc. | 2025‑04‑17 | Lumma Stealer C&C server. |
104.21.32[.]1 | zestmodp[.]prime | Cloudflare, Inc. | 2025‑04‑08 | Lumma Stealer C&C server. |
172.67.147[.]123 | equatorf[.]run | Cloudflare, Inc. | 2025‑04‑21 | Lumma Stealer C&C server. |
104.21.112[.]1 | hemispherexz[.]prime | Cloudflare, Inc. | 2025‑04‑21 | Lumma Stealer C&C server. |
104.21.20[.]106 | latitudert[.]stay | Cloudflare, Inc. | 2025‑04‑21 | Lumma Stealer C&C server. |
172.67.216[.]12 | sectorecoo[.]stay | Cloudflare, Inc. | 2025‑04‑19 | Lumma Stealer C&C server. |
MITRE ATT&CK strategies
This desk was constructed utilizing model 17 of the MITRE ATT&CK framework.
Tactic | ID | Identify | Description |
Useful resource Growth | T1587.001 | Develop Capabilities: Malware | Lumma Stealer operators actively developed their malware as a product for his or her service. |
T1583.001 | Purchase Infrastructure: Domains | Lumma Stealer operators registered domains for his or her exfiltration infrastructure. | |
T1583.006 | Purchase Infrastructure: Net Providers | Lumma Stealer operators used Cloudflare providers to cover their infrastructure. Lumma Stealer additionally hid its C&C URLs in public providers like dummy Steam profiles or empty Telegram channels. | |
Execution | T1059.003 | Command-Line Interface: Home windows Command Shell | Lumma Stealer executes cmd.exe to delete short-term information. |
T1106 | Native API | Lumma Stealer executes quite a lot of Home windows APIs, together with VirtualAlloc, LoadLibraryA, and GetProcAddress. | |
T1204.001 | Consumer Execution: Malicious Hyperlink | Lumma Stealer operators supply a easy LNK packing characteristic for his or her malware builds. | |
T1047 | Home windows Administration Instrumentation | Lumma Stealer makes use of WMI queries to assemble system info. | |
Protection Evasion | T1622 | Debugger Evasion | Lumma Stealer checks for debugger presence. |
T1140 | Deobfuscate/Decode Information or Info | Lumma Stealer makes use of ChaCha20 for C&C listing and dynamic config encryption. | |
T1027.007 | Obfuscated Information or Info: Dynamic API Decision | Lumma Stealer resolves API names at runtime utilizing the FNV-1a hash algorithm. | |
T1027.013 | Obfuscated Information or Info: Encrypted/Encoded File | Lumma Stealer encrypts strings and essential binary knowledge utilizing stack strings or ChaCha20. | |
Credential Entry | T1555.003 | Credentials from Password Shops: Credentials from Net Browsers | Lumma Stealer gathers credentials from a number of browsers. |
T1539 | Steal Net Session Cookie | Lumma Stealer gathers cookies from a number of browsers. | |
Discovery | T1217 | Browser Bookmark Discovery | Lumma Stealer checks and collects varied details about put in browsers on victims’ machines. |
T1012 | Question Registry | Lumma Stealer queries registry keys to listing put in software program on victims’ machines. | |
T1057 | Course of Discovery | Lumma Stealer sends the method listing to its C&C server. | |
T1518 | Software program Discovery | Lumma Stealer sends an inventory of put in software program to its C&C server. | |
T1082 | System Info Discovery | Lumma Stealer sends system info to its C&C server. | |
T1124 | System Time Discovery | Lumma Stealer sends the present system time and time zone to its C&C server. | |
Assortment | T1560 | Archive Collected Information | Lumma Stealer compresses gathered knowledge earlier than exfiltration to its C&C server. |
T1119 | Automated Assortment | Lumma Stealer’s exfiltration capabilities are absolutely automated and based mostly on a configuration file. | |
T1113 | Display screen Seize | Lumma Stealer takes screenshots of victims’ machines based mostly on dynamic configuration. | |
T1005 | Information from Native System | Lumma Stealer collects native system knowledge from victims’ machines. | |
Command and Management | T1071.001 | Utility Layer Protocol: Net Protocols | Lumma Stealer makes use of HTTPS communication with its C&C servers. |
T1132.001 | Information Encoding: Commonplace Encoding | Lumma Stealer used base64 encoding for acquiring its configuration from the C&C server. | |
T1573.001 | Encrypted Channel: Symmetric Cryptography | Lumma Stealer makes use of extra ChaCha20 encryption underneath the HTTPS community protocol. | |
T1008 | Fallback Channels | Lumma Stealer employs backup dead-drop resolvers in Steam profiles and Telegram channels. | |
T1102.001 | Net Service: Useless Drop Resolver | Lumma Stealer employs backup dead-drop resolvers in Steam profiles and Telegram channels. | |
Exfiltration | T1020 | Automated Exfiltration | Lumma Stealer exfiltrates stolen credentials and knowledge over the C&C channel. |
T1041 | Exfiltration Over C2 Channel | Lumma Stealer exfiltrates stolen credentials and knowledge over the C&C channel. |