Analysis
- max time kernel
4294180s - max time network
127s - platform
windows7_x64 - resource
win7-20220311-en - submitted
23/03/2022, 08:44
Static task
static1
Behavioral task
behavioral1
Sample
33f21440bd1754d6f34c3cbcdddc6d392cf46b9cec8f13abf16d00e5e9927758.dll
Resource
win7-20220311-en
General
- Target 33f21440bd1754d6f34c3cbcdddc6d392cf46b9cec8f13abf16d00e5e9927758.dll
- Size 688KB
- Sample220323-kner2aagg2
- SHA256 33f21440bd1754d6f34c3cbcdddc6d392cf46b9cec8f13abf16d00e5e9927758
- MD5 630040922bcc16ed4c81d293e469aac2
- SHA1 eb8444abea3680ee7f7d96449e2042fa8ed4593d
- SHA512 d48fba020133a313349c53ba94546cb6df9bfbe3b9d115a2b0c6877530308b998b9fed2307128bfe37fb0c3e558d9c62f78c80b3939f15dee6a8d94bacda7c69
- MD5 SHA1 SHA512
Malware Config
Extracted
-
emotet
-
Epoch4
-
45.76.1.145:443
-
217.182.25.250:8080
-
119.193.124.41:7080
-
192.99.251.50:443
-
146.59.226.45:443
-
173.212.193.249:8080
-
207.38.84.195:8080
-
45.118.135.203:7080
-
31.24.158.56:8080
-
209.126.98.206:8080
-
212.237.17.99:8080
-
216.158.226.206:443
-
50.30.40.196:8080
-
82.165.152.127:8080
-
159.8.59.82:8080
-
107.182.225.142:8080
-
110.232.117.186:8080
-
72.15.201.15:8080
-
5.9.116.246:8080
-
79.172.212.216:8080
-
212.24.98.99:8080
-
188.44.20.25:443
-
101.50.0.91:8080
-
203.114.109.124:443
-
151.106.112.196:8080
-
196.218.30.83:443
-
176.56.128.118:443
-
159.65.88.10:8080
-
195.154.133.20:443
-
176.104.106.96:8080
-
45.118.115.99:8080
-
129.232.188.93:443
-
45.176.232.124:443
-
158.69.222.101:443
-
45.142.114.231:8080
-
103.221.221.247:8080
-
103.43.46.182:443
-
185.157.82.211:8080
-
51.91.7.5:8080
-
103.75.201.2:443
-
167.99.115.35:8080
-
185.8.212.130:7080
-
46.55.222.11:443
-
197.242.150.244:8080
-
58.227.42.236:80
-
195.201.151.129:8080
-
51.254.140.238:7080
-
50.116.54.215:443
-
138.185.72.26:8080
-
178.79.147.66:8080
-
189.126.111.200:7080
-
153.126.146.25:7080
-
103.75.201.4:443
-
164.68.99.3:8080
-
131.100.24.231:80
-
1.234.2.232:8080
Signatures
- Suspicious behavior: EnumeratesProcesses 1 IoCs
pid Process 1016 regsvr32.exe - Suspicious use of WriteProcessMemory 7 IoCs
description pid Process procid_target PID 576 wrote to memory of 1016 576 regsvr32.exe 27 PID 576 wrote to memory of 1016 576 regsvr32.exe 27 PID 576 wrote to memory of 1016 576 regsvr32.exe 27 PID 576 wrote to memory of 1016 576 regsvr32.exe 27 PID 576 wrote to memory of 1016 576 regsvr32.exe 27 PID 576 wrote to memory of 1016 576 regsvr32.exe 27 PID 576 wrote to memory of 1016 576 regsvr32.exe 27
Processes
-
C:\Windows\system32\regsvr32.exeregsvr32 /s C:\Users\Admin\AppData\Local\Temp\33f21440bd1754d6f34c3cbcdddc6d392cf46b9cec8f13abf16d00e5e9927758.dll1⤵
- Suspicious use of WriteProcessMemory
PID:576 -
C:\Windows\SysWOW64\regsvr32.exe/s C:\Users\Admin\AppData\Local\Temp\33f21440bd1754d6f34c3cbcdddc6d392cf46b9cec8f13abf16d00e5e9927758.dll2⤵
- Suspicious behavior: EnumeratesProcesses
PID:1016
-