Analysis
- max time kernel
93s - max time network
98s - platform
windows10-2004_x64 - resource
win10v2004-20240508-en - resource tags
arch:x64arch:x86image:win10v2004-20240508-enlocale:en-usos:windows10-2004-x64system - submitted
03/07/2024, 05:32
Static task
static1
1 signatures
Behavioral task
behavioral1
Sample
2fd72d0d0fbc053a53adee5d9ec6cffde3fb5a3c6ba0c0490e24552b264d5449.exe
Resource
win10v2004-20240508-en
4 signatures
150 seconds
Behavioral task
behavioral2
Sample
2fd72d0d0fbc053a53adee5d9ec6cffde3fb5a3c6ba0c0490e24552b264d5449.exe
Resource
win11-20240419-en
3 signatures
150 seconds
General
- Target 2fd72d0d0fbc053a53adee5d9ec6cffde3fb5a3c6ba0c0490e24552b264d5449.exe
- Size 937KB
- Sample240703-f8dcgstdmp
- SHA256 2fd72d0d0fbc053a53adee5d9ec6cffde3fb5a3c6ba0c0490e24552b264d5449
- MD5 168c5908924803d268d26965c32a5620
- SHA1 9e0e2dc9c7e931c4ee860c32d83711c433f7b1a3
- SHA512 749f0e4da8d6fde35b53e769b0b594c2e63835f970eedc54c8c15889863811b5fb296650ae9f5e255bafdd4b942ad3434a60c48e05f1283820c378d30645f1c1
- SSDEEP 24576:YlrD4dQCg30l8cwMKAWgXkALsi3XoiHbL1/2E47kRh2gPilPfy:6RE6cwMKAHO6XoGR/Slhi
- MD5 SHA1 SHA512 SSDEEP
Malware Config
Extracted
Family
-
lumma
C2
-
https://civilizzzationo.shop/api
-
https://bouncedgowp.shop/api
-
https://bannngwko.shop/api
-
https://bargainnykwo.shop/api
-
https://affecthorsedpo.shop/api
-
https://radiationnopp.shop/api
-
https://answerrsdo.shop/api
-
https://publicitttyps.shop/api
-
https://benchillppwo.shop/api
-
https://reinforcedirectorywd.shop/api
Signatures
- Suspicious use of SetThreadContext 1 IoCs
description pid Process procid_target PID 2896 set thread context of 1792 2896 2fd72d0d0fbc053a53adee5d9ec6cffde3fb5a3c6ba0c0490e24552b264d5449.exe 81 - Program crash 1 IoCs
pid pid_target Process procid_target 1148 2896 WerFault.exe 79 - Suspicious use of WriteProcessMemory 12 IoCs
description pid Process procid_target PID 2896 wrote to memory of 2180 2896 2fd72d0d0fbc053a53adee5d9ec6cffde3fb5a3c6ba0c0490e24552b264d5449.exe 80 PID 2896 wrote to memory of 2180 2896 2fd72d0d0fbc053a53adee5d9ec6cffde3fb5a3c6ba0c0490e24552b264d5449.exe 80 PID 2896 wrote to memory of 2180 2896 2fd72d0d0fbc053a53adee5d9ec6cffde3fb5a3c6ba0c0490e24552b264d5449.exe 80 PID 2896 wrote to memory of 1792 2896 2fd72d0d0fbc053a53adee5d9ec6cffde3fb5a3c6ba0c0490e24552b264d5449.exe 81 PID 2896 wrote to memory of 1792 2896 2fd72d0d0fbc053a53adee5d9ec6cffde3fb5a3c6ba0c0490e24552b264d5449.exe 81 PID 2896 wrote to memory of 1792 2896 2fd72d0d0fbc053a53adee5d9ec6cffde3fb5a3c6ba0c0490e24552b264d5449.exe 81 PID 2896 wrote to memory of 1792 2896 2fd72d0d0fbc053a53adee5d9ec6cffde3fb5a3c6ba0c0490e24552b264d5449.exe 81 PID 2896 wrote to memory of 1792 2896 2fd72d0d0fbc053a53adee5d9ec6cffde3fb5a3c6ba0c0490e24552b264d5449.exe 81 PID 2896 wrote to memory of 1792 2896 2fd72d0d0fbc053a53adee5d9ec6cffde3fb5a3c6ba0c0490e24552b264d5449.exe 81 PID 2896 wrote to memory of 1792 2896 2fd72d0d0fbc053a53adee5d9ec6cffde3fb5a3c6ba0c0490e24552b264d5449.exe 81 PID 2896 wrote to memory of 1792 2896 2fd72d0d0fbc053a53adee5d9ec6cffde3fb5a3c6ba0c0490e24552b264d5449.exe 81 PID 2896 wrote to memory of 1792 2896 2fd72d0d0fbc053a53adee5d9ec6cffde3fb5a3c6ba0c0490e24552b264d5449.exe 81
Processes
-
C:\Users\Admin\AppData\Local\Temp\2fd72d0d0fbc053a53adee5d9ec6cffde3fb5a3c6ba0c0490e24552b264d5449.exe"C:\Users\Admin\AppData\Local\Temp\2fd72d0d0fbc053a53adee5d9ec6cffde3fb5a3c6ba0c0490e24552b264d5449.exe"1⤵
- Suspicious use of SetThreadContext
- Suspicious use of WriteProcessMemory
PID:2896 -
C:\Windows\Microsoft.NET\Framework\v4.0.30319\RegAsm.exe"C:\Windows\Microsoft.NET\Framework\v4.0.30319\RegAsm.exe"2⤵PID:2180
-
-
C:\Windows\Microsoft.NET\Framework\v4.0.30319\RegAsm.exe"C:\Windows\Microsoft.NET\Framework\v4.0.30319\RegAsm.exe"2⤵PID:1792
-
-
C:\Windows\SysWOW64\WerFault.exeC:\Windows\SysWOW64\WerFault.exe -u -p 2896 -s 3082⤵
- Program crash
PID:1148
-
-
C:\Windows\SysWOW64\WerFault.exeC:\Windows\SysWOW64\WerFault.exe -pss -s 456 -p 2896 -ip 28961⤵PID:880