Analysis
-
max time kernel
26s -
max time network
30s -
platform
windows10_x64 -
resource
win10v200722 -
submitted
28-07-2020 22:27
Static task
static1
General
-
Target
f0df82c8613c5f9fd46cc65b7996a6e6318755411a2dff3d324a8f3d758ea797.exe
-
Size
612KB
-
MD5
19f6c263014dd09aa205d15e2b36f043
-
SHA1
65f543d942b03f316795bd310c0dd1dd73d182cb
-
SHA256
f0df82c8613c5f9fd46cc65b7996a6e6318755411a2dff3d324a8f3d758ea797
-
SHA512
a6d8c8f8acb0a55dd4493a3b57c7156d8a63bcef49c14b2989fca635143caf1a74832c61c297be510ded4f36097201abbd979ad57f01877552e7ec31f6dd936a
Malware Config
Extracted
emotet
177.37.81.212:443
74.207.230.187:8080
190.164.75.175:80
87.252.100.28:80
105.209.239.55:80
163.172.107.70:8080
37.208.106.146:8080
24.157.25.203:80
212.112.113.235:80
140.207.113.106:443
75.139.38.211:80
192.210.217.94:8080
46.49.124.53:80
75.127.14.170:8080
87.106.231.60:8080
139.59.12.63:8080
181.167.35.84:80
201.214.108.231:80
74.208.173.91:8080
189.146.1.78:443
212.156.133.218:80
37.70.131.107:80
181.113.229.139:443
144.139.91.187:80
50.116.78.109:8080
46.32.229.152:8080
80.211.32.88:8080
157.7.164.178:8081
113.161.148.81:80
37.46.129.215:8080
216.75.37.196:8080
78.188.170.128:80
192.241.220.183:8080
77.74.78.80:443
81.214.253.80:443
45.118.136.92:8080
113.160.180.109:80
143.95.101.72:8080
181.143.101.19:8080
190.111.215.4:8080
192.163.221.191:8080
203.153.216.182:7080
46.105.131.68:8080
177.144.130.105:443
51.38.201.19:7080
190.55.233.156:80
181.134.9.162:80
178.33.167.120:8080
41.185.29.128:8080
78.189.111.208:443
181.164.110.7:80
203.153.216.178:7080
115.79.195.246:80
195.201.56.70:8080
179.5.118.12:80
185.142.236.163:443
91.83.93.103:443
Signatures
-
Emotet Payload 2 IoCs
Detects Emotet payload in memory.
Processes:
resource yara_rule behavioral1/memory/408-0-0x0000000000740000-0x000000000074C000-memory.dmp emotet behavioral1/memory/664-3-0x0000000000710000-0x000000000071C000-memory.dmp emotet -
Drops file in System32 directory 1 IoCs
Processes:
f0df82c8613c5f9fd46cc65b7996a6e6318755411a2dff3d324a8f3d758ea797.exedescription ioc process File opened for modification C:\Windows\SysWOW64\DeviceFlows.DataModel\prevhost.exe f0df82c8613c5f9fd46cc65b7996a6e6318755411a2dff3d324a8f3d758ea797.exe -
Suspicious use of SetWindowsHookEx 4 IoCs
Processes:
f0df82c8613c5f9fd46cc65b7996a6e6318755411a2dff3d324a8f3d758ea797.exeprevhost.exepid process 408 f0df82c8613c5f9fd46cc65b7996a6e6318755411a2dff3d324a8f3d758ea797.exe 408 f0df82c8613c5f9fd46cc65b7996a6e6318755411a2dff3d324a8f3d758ea797.exe 664 prevhost.exe 664 prevhost.exe -
Suspicious behavior: RenamesItself 1 IoCs
Processes:
f0df82c8613c5f9fd46cc65b7996a6e6318755411a2dff3d324a8f3d758ea797.exepid process 408 f0df82c8613c5f9fd46cc65b7996a6e6318755411a2dff3d324a8f3d758ea797.exe -
Suspicious use of WriteProcessMemory 3 IoCs
Processes:
f0df82c8613c5f9fd46cc65b7996a6e6318755411a2dff3d324a8f3d758ea797.exedescription pid process target process PID 408 wrote to memory of 664 408 f0df82c8613c5f9fd46cc65b7996a6e6318755411a2dff3d324a8f3d758ea797.exe prevhost.exe PID 408 wrote to memory of 664 408 f0df82c8613c5f9fd46cc65b7996a6e6318755411a2dff3d324a8f3d758ea797.exe prevhost.exe PID 408 wrote to memory of 664 408 f0df82c8613c5f9fd46cc65b7996a6e6318755411a2dff3d324a8f3d758ea797.exe prevhost.exe -
Executes dropped EXE 1 IoCs
Processes:
prevhost.exepid process 664 prevhost.exe -
Suspicious behavior: EnumeratesProcesses 4 IoCs
Processes:
prevhost.exepid process 664 prevhost.exe 664 prevhost.exe 664 prevhost.exe 664 prevhost.exe
Processes
-
C:\Users\Admin\AppData\Local\Temp\f0df82c8613c5f9fd46cc65b7996a6e6318755411a2dff3d324a8f3d758ea797.exe"C:\Users\Admin\AppData\Local\Temp\f0df82c8613c5f9fd46cc65b7996a6e6318755411a2dff3d324a8f3d758ea797.exe"1⤵
- Drops file in System32 directory
- Suspicious use of SetWindowsHookEx
- Suspicious behavior: RenamesItself
- Suspicious use of WriteProcessMemory
PID:408 -
C:\Windows\SysWOW64\DeviceFlows.DataModel\prevhost.exe"C:\Windows\SysWOW64\DeviceFlows.DataModel\prevhost.exe"2⤵
- Suspicious use of SetWindowsHookEx
- Executes dropped EXE
- Suspicious behavior: EnumeratesProcesses
PID:664