Analysis
- max time kernel
4294213s - max time network
161s - platform
windows7_x64 - resource
win7-20220310-en - submitted
14/03/2022, 12:13
Static task
static1
Behavioral task
behavioral1
Sample
638329065ac481714f4235ec68072798.dll
Resource
win7-20220310-en
General
- Target 638329065ac481714f4235ec68072798.dll
- Size 801KB
- Sample220314-pdrq3aghhm
- SHA256 dd20054e64e6c8d824827b0c86cfe3d725eff4ef0e3bf3ab57a5c5119df86f11
- MD5 638329065ac481714f4235ec68072798
- SHA1 1c4f68ff7c7cc8d154f7e507ee68509e121c748c
- SHA512 e4869b5ed175099bb345532ca970dc6c8263970e5a79427e346bb56e01160b71a22940f090392f1feaea9270ed81ac34442d80877d3f269f2a0b94917d9992c3
- 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
- suricata: ET MALWARE W32/Emotet CnC Beacon 3
suricata: ET MALWARE W32/Emotet CnC Beacon 3
- Drops file in System32 directory 1 IoCs
description ioc Process File opened for modification C:\Windows\SysWOW64\Badqns\olfedbsqxxkphk.bms regsvr32.exe - Suspicious behavior: EnumeratesProcesses 1 IoCs
pid Process 1940 regsvr32.exe - Suspicious behavior: RenamesItself 1 IoCs
pid Process 964 regsvr32.exe - Suspicious use of WriteProcessMemory 14 IoCs
description pid Process procid_target PID 948 wrote to memory of 964 948 regsvr32.exe 27 PID 948 wrote to memory of 964 948 regsvr32.exe 27 PID 948 wrote to memory of 964 948 regsvr32.exe 27 PID 948 wrote to memory of 964 948 regsvr32.exe 27 PID 948 wrote to memory of 964 948 regsvr32.exe 27 PID 948 wrote to memory of 964 948 regsvr32.exe 27 PID 948 wrote to memory of 964 948 regsvr32.exe 27 PID 964 wrote to memory of 1940 964 regsvr32.exe 28 PID 964 wrote to memory of 1940 964 regsvr32.exe 28 PID 964 wrote to memory of 1940 964 regsvr32.exe 28 PID 964 wrote to memory of 1940 964 regsvr32.exe 28 PID 964 wrote to memory of 1940 964 regsvr32.exe 28 PID 964 wrote to memory of 1940 964 regsvr32.exe 28 PID 964 wrote to memory of 1940 964 regsvr32.exe 28
Processes
-
C:\Windows\system32\regsvr32.exeregsvr32 /s C:\Users\Admin\AppData\Local\Temp\638329065ac481714f4235ec68072798.dll1⤵
- Suspicious use of WriteProcessMemory
PID:948 -
C:\Windows\SysWOW64\regsvr32.exe/s C:\Users\Admin\AppData\Local\Temp\638329065ac481714f4235ec68072798.dll2⤵
- Drops file in System32 directory
- Suspicious behavior: RenamesItself
- Suspicious use of WriteProcessMemory
PID:964 -
C:\Windows\SysWOW64\regsvr32.exeC:\Windows\SysWOW64\regsvr32.exe /s "C:\Windows\SysWOW64\Badqns\olfedbsqxxkphk.bms"3⤵
- Suspicious behavior: EnumeratesProcesses
PID:1940
-
-