Edit tour
Windows
Analysis Report
file.exe
Overview
General Information
Detection
LummaC
Score: | 100 |
Range: | 0 - 100 |
Whitelisted: | false |
Confidence: | 100% |
Signatures
Antivirus / Scanner detection for submitted sample
Found malware configuration
Multi AV Scanner detection for submitted file
Suricata IDS alerts for network traffic
Yara detected LummaC Stealer
C2 URLs / IPs found in malware configuration
Found many strings related to Crypto-Wallets (likely being stolen)
Hides threads from debuggers
LummaC encrypted strings found
Machine Learning detection for sample
PE file contains section with special chars
Query firmware table information (likely to detect VMs)
Tries to detect process monitoring tools (Task Manager, Process Explorer etc.)
Tries to detect sandboxes / dynamic malware analysis system (registry check)
Tries to detect sandboxes and other dynamic analysis tools (window names)
Tries to detect virtualization through RDTSC time measurements
Tries to evade debugger and weak emulator (self modifying code)
Tries to harvest and steal browser information (history, passwords, etc)
Tries to steal Crypto Currency Wallets
AV process strings found (often used to terminate AV products)
Checks for debuggers (devices)
Checks if Antivirus/Antispyware/Firewall program is installed (via WMI)
Checks if the current process is being debugged
Contains capabilities to detect virtual machines
Creates a process in suspended mode (likely to inject code)
Downloads executable code via HTTP
Entry point lies outside standard sections
IP address seen in connection with other malware
JA3 SSL client fingerprint seen in connection with other malware
May sleep (evasive loops) to hinder dynamic analysis
Monitors certain registry keys / values for changes (often done to protect autostart functionality)
PE file contains an invalid checksum
PE file contains sections with non-standard names
Queries sensitive BIOS Information (via WMI, Win32_Bios & Win32_BaseBoard, often done to detect virtual machines)
Queries the volume information (name, serial number etc) of a device
Sample file is different than original file name gathered from version info
Searches for user specific document files
Suricata IDS alerts with low severity for network traffic
Uses 32bit PE files
Uses code obfuscation techniques (call, push, ret)
Yara detected Credential Stealer
Classification
- System is w10x64
- file.exe (PID: 6568 cmdline:
"C:\Users\ user\Deskt op\file.ex e" MD5: 27FA50C74212925790649267140710F1) - chrome.exe (PID: 6376 cmdline:
"C:\Progra m Files\Go ogle\Chrom e\Applicat ion\chrome .exe" --st art-maximi zed --sing le-argumen t http://g o.microsof t.com/fwli nk/?prd=11 324&pver=4 .5&sbp=App Launch2&pl cid=0x409& o1=SHIM_NO VERSION_FO UND&versio n=(null)&p rocessName =file.exe& platform=0 009&osver= 6&isServer =0&shimver =4.0.30319 .0 MD5: 45DE480806D1B5D462A7DDE4DCEFC4E4) - chrome.exe (PID: 8 cmdline:
"C:\Progra m Files\Go ogle\Chrom e\Applicat ion\chrome .exe" --ty pe=utility --utility -sub-type= network.mo jom.Networ kService - -lang=en-U S --servic e-sandbox- type=none --mojo-pla tform-chan nel-handle =2084 --fi eld-trial- handle=193 2,i,640070 8159271862 020,179943 3509390324 7733,26214 4 --disabl e-features =Optimizat ionGuideMo delDownloa ding,Optim izationHin ts,Optimiz ationHints Fetching,O ptimizatio nTargetPre diction /p refetch:8 MD5: 45DE480806D1B5D462A7DDE4DCEFC4E4) - chrome.exe (PID: 7428 cmdline:
"C:\Progra m Files\Go ogle\Chrom e\Applicat ion\chrome .exe" --st art-maximi zed --sing le-argumen t http://g o.microsof t.com/fwli nk/?prd=11 324&pver=4 .5&sbp=App Launch2&pl cid=0x409& o1=SHIM_NO VERSION_FO UND&versio n=(null)&p rocessName =file.exe& platform=0 009&osver= 6&isServer =0&shimver =4.0.30319 .0 MD5: 45DE480806D1B5D462A7DDE4DCEFC4E4) - chrome.exe (PID: 7620 cmdline:
"C:\Progra m Files\Go ogle\Chrom e\Applicat ion\chrome .exe" --ty pe=utility --utility -sub-type= network.mo jom.Networ kService - -lang=en-U S --servic e-sandbox- type=none --mojo-pla tform-chan nel-handle =1908 --fi eld-trial- handle=199 6,i,980852 0038763490 769,513243 5854326033 979,262144 --disable -features= Optimizati onGuideMod elDownload ing,Optimi zationHint s,Optimiza tionHintsF etching,Op timization TargetPred iction /pr efetch:8 MD5: 45DE480806D1B5D462A7DDE4DCEFC4E4)
- cleanup
Name | Description | Attribution | Blogpost URLs | Link |
---|---|---|---|---|
Lumma Stealer, LummaC2 Stealer | Lumma Stealer (aka LummaC2 Stealer) is an information stealer written in C language that has been available through a Malware-as-a-Service (MaaS) model on Russian-speaking forums since at least August 2022. It is believed to have been developed by the threat actor "Shamel", who goes by the alias "Lumma". Lumma Stealer primarily targets cryptocurrency wallets and two-factor authentication (2FA) browser extensions, before ultimately stealing sensitive information from the victim's machine. Once the targeted data is obtained, it is exfiltrated to a C2 server via HTTP POST requests using the user agent "TeslaBrowser/5.5"." The stealer also features a non-resident loader that is capable of delivering additional payloads via EXE, DLL, and PowerShell. | No Attribution |
{"C2 url": ["p3ar11fter.sbs", "processhol.sbs", "p10tgrace.sbs", "peepburry828.sbs", "3xp3cts1aim.sbs"], "Build id": "LOGS11--LiveTraffic"}
Source | Rule | Description | Author | Strings |
---|---|---|---|---|
JoeSecurity_LummaCStealer_3 | Yara detected LummaC Stealer | Joe Security |
Source | Rule | Description | Author | Strings |
---|---|---|---|---|
JoeSecurity_CredentialStealer | Yara detected Credential Stealer | Joe Security | ||
JoeSecurity_CredentialStealer | Yara detected Credential Stealer | Joe Security | ||
JoeSecurity_CredentialStealer | Yara detected Credential Stealer | Joe Security | ||
JoeSecurity_CredentialStealer | Yara detected Credential Stealer | Joe Security | ||
JoeSecurity_LummaCStealer | Yara detected LummaC Stealer | Joe Security |
⊘No Sigma rule has matched
Timestamp | SID | Severity | Classtype | Source IP | Source Port | Destination IP | Destination Port | Protocol |
---|---|---|---|---|---|---|---|---|
2024-11-22T04:25:58.615154+0100 | 2028371 | 3 | Unknown Traffic | 192.168.2.4 | 49730 | 172.67.155.248 | 443 | TCP |
2024-11-22T04:26:00.643140+0100 | 2028371 | 3 | Unknown Traffic | 192.168.2.4 | 49731 | 172.67.155.248 | 443 | TCP |
2024-11-22T04:26:03.090889+0100 | 2028371 | 3 | Unknown Traffic | 192.168.2.4 | 49732 | 172.67.155.248 | 443 | TCP |
2024-11-22T04:26:05.421205+0100 | 2028371 | 3 | Unknown Traffic | 192.168.2.4 | 49733 | 172.67.155.248 | 443 | TCP |
2024-11-22T04:26:07.756352+0100 | 2028371 | 3 | Unknown Traffic | 192.168.2.4 | 49734 | 172.67.155.248 | 443 | TCP |
2024-11-22T04:26:10.828021+0100 | 2028371 | 3 | Unknown Traffic | 192.168.2.4 | 49735 | 172.67.155.248 | 443 | TCP |
2024-11-22T04:26:14.194126+0100 | 2028371 | 3 | Unknown Traffic | 192.168.2.4 | 49737 | 172.67.155.248 | 443 | TCP |
2024-11-22T04:26:20.513664+0100 | 2028371 | 3 | Unknown Traffic | 192.168.2.4 | 49742 | 172.67.155.248 | 443 | TCP |
Timestamp | SID | Severity | Classtype | Source IP | Source Port | Destination IP | Destination Port | Protocol |
---|---|---|---|---|---|---|---|---|
2024-11-22T04:25:59.321357+0100 | 2054653 | 1 | A Network Trojan was detected | 192.168.2.4 | 49730 | 172.67.155.248 | 443 | TCP |
2024-11-22T04:26:01.368243+0100 | 2054653 | 1 | A Network Trojan was detected | 192.168.2.4 | 49731 | 172.67.155.248 | 443 | TCP |
2024-11-22T04:26:21.234927+0100 | 2054653 | 1 | A Network Trojan was detected | 192.168.2.4 | 49742 | 172.67.155.248 | 443 | TCP |
Timestamp | SID | Severity | Classtype | Source IP | Source Port | Destination IP | Destination Port | Protocol |
---|---|---|---|---|---|---|---|---|
2024-11-22T04:25:59.321357+0100 | 2049836 | 1 | A Network Trojan was detected | 192.168.2.4 | 49730 | 172.67.155.248 | 443 | TCP |
Timestamp | SID | Severity | Classtype | Source IP | Source Port | Destination IP | Destination Port | Protocol |
---|---|---|---|---|---|---|---|---|
2024-11-22T04:26:01.368243+0100 | 2049812 | 1 | A Network Trojan was detected | 192.168.2.4 | 49731 | 172.67.155.248 | 443 | TCP |
Timestamp | SID | Severity | Classtype | Source IP | Source Port | Destination IP | Destination Port | Protocol |
---|---|---|---|---|---|---|---|---|
2024-11-22T04:25:58.615154+0100 | 2057731 | 1 | Domain Observed Used for C2 Detected | 192.168.2.4 | 49730 | 172.67.155.248 | 443 | TCP |
2024-11-22T04:26:00.643140+0100 | 2057731 | 1 | Domain Observed Used for C2 Detected | 192.168.2.4 | 49731 | 172.67.155.248 | 443 | TCP |
2024-11-22T04:26:03.090889+0100 | 2057731 | 1 | Domain Observed Used for C2 Detected | 192.168.2.4 | 49732 | 172.67.155.248 | 443 | TCP |
2024-11-22T04:26:05.421205+0100 | 2057731 | 1 | Domain Observed Used for C2 Detected | 192.168.2.4 | 49733 | 172.67.155.248 | 443 | TCP |
2024-11-22T04:26:07.756352+0100 | 2057731 | 1 | Domain Observed Used for C2 Detected | 192.168.2.4 | 49734 | 172.67.155.248 | 443 | TCP |
2024-11-22T04:26:10.828021+0100 | 2057731 | 1 | Domain Observed Used for C2 Detected | 192.168.2.4 | 49735 | 172.67.155.248 | 443 | TCP |
2024-11-22T04:26:14.194126+0100 | 2057731 | 1 | Domain Observed Used for C2 Detected | 192.168.2.4 | 49737 | 172.67.155.248 | 443 | TCP |
2024-11-22T04:26:20.513664+0100 | 2057731 | 1 | Domain Observed Used for C2 Detected | 192.168.2.4 | 49742 | 172.67.155.248 | 443 | TCP |
Timestamp | SID | Severity | Classtype | Source IP | Source Port | Destination IP | Destination Port | Protocol |
---|---|---|---|---|---|---|---|---|
2024-11-22T04:26:22.804895+0100 | 2019714 | 2 | Potentially Bad Traffic | 192.168.2.4 | 49744 | 185.215.113.16 | 80 | TCP |
Timestamp | SID | Severity | Classtype | Source IP | Source Port | Destination IP | Destination Port | Protocol |
---|---|---|---|---|---|---|---|---|
2024-11-22T04:25:57.186382+0100 | 2057730 | 1 | Domain Observed Used for C2 Detected | 192.168.2.4 | 64495 | 1.1.1.1 | 53 | UDP |
Timestamp | SID | Severity | Classtype | Source IP | Source Port | Destination IP | Destination Port | Protocol |
---|---|---|---|---|---|---|---|---|
2024-11-22T04:26:11.568197+0100 | 2048094 | 1 | Malware Command and Control Activity Detected | 192.168.2.4 | 49735 | 172.67.155.248 | 443 | TCP |
Timestamp | SID | Severity | Classtype | Source IP | Source Port | Destination IP | Destination Port | Protocol |
---|---|---|---|---|---|---|---|---|
2024-11-22T04:26:14.198969+0100 | 2843864 | 1 | A Network Trojan was detected | 192.168.2.4 | 49737 | 172.67.155.248 | 443 | TCP |
Click to jump to signature section
Show All Signature Results
AV Detection |
---|
Source: | Avira: |
Source: | Malware Configuration Extractor: |
Source: | Virustotal: | Perma Link |
Source: | Joe Sandbox ML: |
Source: | HTTP Parser: | ||
Source: | HTTP Parser: | ||
Source: | HTTP Parser: | ||
Source: | HTTP Parser: |
Source: | Static PE information: |
Source: | HTTPS traffic detected: | ||
Source: | HTTPS traffic detected: | ||
Source: | HTTPS traffic detected: | ||
Source: | HTTPS traffic detected: | ||
Source: | HTTPS traffic detected: | ||
Source: | HTTPS traffic detected: | ||
Source: | HTTPS traffic detected: | ||
Source: | HTTPS traffic detected: | ||
Source: | HTTPS traffic detected: | ||
Source: | HTTPS traffic detected: | ||
Source: | HTTPS traffic detected: | ||
Source: | HTTPS traffic detected: | ||
Source: | HTTPS traffic detected: |
Networking |
---|
Source: | Suricata IDS: | ||
Source: | Suricata IDS: | ||
Source: | Suricata IDS: | ||
Source: | Suricata IDS: | ||
Source: | Suricata IDS: | ||
Source: | Suricata IDS: | ||
Source: | Suricata IDS: | ||
Source: | Suricata IDS: | ||
Source: | Suricata IDS: | ||
Source: | Suricata IDS: | ||
Source: | Suricata IDS: | ||
Source: | Suricata IDS: | ||
Source: | Suricata IDS: | ||
Source: | Suricata IDS: | ||
Source: | Suricata IDS: | ||
Source: | Suricata IDS: |
Source: | URLs: | ||
Source: | URLs: | ||
Source: | URLs: | ||
Source: | URLs: | ||
Source: | URLs: |
Source: | HTTP traffic detected: |