Analysis
- max time kernel
154s - max time network
164s - platform
windows10-2004_x64 - resource
win10v2004-20220310-en - submitted
15/03/2022, 14:21
Static task
static1
Behavioral task
behavioral1
Sample
ff81cdc86b7c12c33ed8c106fb0c0b48.dll
Resource
win7-20220311-en
General
- Target ff81cdc86b7c12c33ed8c106fb0c0b48.dll
- Size 996KB
- Sample220315-rn1stscfd2
- SHA256 ad9f5e3ac5323892bb626eed057e2d41b652be8a1c89bea111e64aff8dae5040
- MD5 ff81cdc86b7c12c33ed8c106fb0c0b48
- SHA1 9ccfcb9a85cc9771b4696cfc1de4b954ab7fcecc
- SHA512 c5127f792a8dceec8a572c9d0605aad829caaae05690c47c53f2a63f914743a69d711091f80bdba112bf005c34759426a5f4d4c501b59d430bee71dca021ecec
- MD5 SHA1 SHA512
Malware Config
Extracted
-
emotet
-
Epoch5
-
51.75.33.122:443
-
186.250.48.5:80
-
168.119.39.118:443
-
207.148.81.119:8080
-
194.9.172.107:8080
-
139.196.72.155:8080
-
78.47.204.80:443
-
159.69.237.188:443
-
45.71.195.104:8080
-
54.37.106.167:8080
-
185.168.130.138:443
-
37.44.244.177:8080
-
185.184.25.78:8080
-
185.148.168.15:8080
-
128.199.192.135:8080
-
37.59.209.141:8080
-
103.41.204.169:8080
-
185.148.168.220:8080
-
103.42.58.120:7080
-
78.46.73.125:443
-
68.183.93.250:443
-
190.90.233.66:443
-
5.56.132.177:8080
-
62.171.178.147:8080
-
196.44.98.190:8080
-
168.197.250.14:80
-
66.42.57.149:443
-
59.148.253.194:443
-
104.131.62.48:8080
-
191.252.103.16:80
-
54.37.228.122:443
-
88.217.172.165:8080
-
195.77.239.39:8080
-
116.124.128.206:8080
-
93.104.209.107:8080
-
118.98.72.86:443
-
217.182.143.207:443
-
87.106.97.83:7080
-
210.57.209.142:8080
-
54.38.242.185:443
-
195.154.146.35:443
-
203.153.216.46:443
-
198.199.98.78:8080
-
85.214.67.203:8080
Signatures
- Loads dropped DLL 1 IoCs
pid Process 2276 regsvr32.exe - Drops file in System32 directory 1 IoCs
description ioc Process File opened for modification C:\Windows\SysWOW64\Ryuwlwppibgda\sxviuoyt.dgz regsvr32.exe - Suspicious behavior: EnumeratesProcesses 2 IoCs
pid Process 2276 regsvr32.exe 2276 regsvr32.exe - Suspicious behavior: RenamesItself 1 IoCs
pid Process 4880 regsvr32.exe - Suspicious use of WriteProcessMemory 6 IoCs
description pid Process procid_target PID 532 wrote to memory of 4880 532 regsvr32.exe 81 PID 532 wrote to memory of 4880 532 regsvr32.exe 81 PID 532 wrote to memory of 4880 532 regsvr32.exe 81 PID 4880 wrote to memory of 2276 4880 regsvr32.exe 87 PID 4880 wrote to memory of 2276 4880 regsvr32.exe 87 PID 4880 wrote to memory of 2276 4880 regsvr32.exe 87
Processes
-
C:\Windows\system32\regsvr32.exeregsvr32 /s C:\Users\Admin\AppData\Local\Temp\ff81cdc86b7c12c33ed8c106fb0c0b48.dll1⤵
- Suspicious use of WriteProcessMemory
PID:532 -
C:\Windows\SysWOW64\regsvr32.exe/s C:\Users\Admin\AppData\Local\Temp\ff81cdc86b7c12c33ed8c106fb0c0b48.dll2⤵
- Drops file in System32 directory
- Suspicious behavior: RenamesItself
- Suspicious use of WriteProcessMemory
PID:4880 -
C:\Windows\SysWOW64\regsvr32.exeC:\Windows\SysWOW64\regsvr32.exe /s "C:\Windows\SysWOW64\Ryuwlwppibgda\sxviuoyt.dgz"3⤵
- Loads dropped DLL
- Suspicious behavior: EnumeratesProcesses
PID:2276
-
-