Analysis
-
max time kernel
4294183s -
max time network
127s -
platform
windows7_x64 -
resource
win7-20220310-en -
submitted
28-03-2022 15:34
Static task
static1
Behavioral task
behavioral1
Sample
3a9397af4dfc720df6b8d7c2949bcac307fd5c2540ca114904f43c162e0f4a4b.exe
Resource
win7-20220310-en
0 signatures
0 seconds
General
-
Target
3a9397af4dfc720df6b8d7c2949bcac307fd5c2540ca114904f43c162e0f4a4b.exe
-
Size
670KB
-
MD5
cebad7507c9b80980e1f6d9f829a7e41
-
SHA1
21a3b8876d3ed54da07825f9696bfb5597c47439
-
SHA256
3a9397af4dfc720df6b8d7c2949bcac307fd5c2540ca114904f43c162e0f4a4b
-
SHA512
5406f08f884584b88df81e3968b9dc37eb3cf4bccfb3d84dffedb7a421a8166f616d9c0b9d036067a06ac5ae59f3141974ee9759a8df18ebb29e2a618bea5bab
Malware Config
Signatures
-
suricata: ET MALWARE VNCStartServer BOT Variant CnC Beacon
suricata: ET MALWARE VNCStartServer BOT Variant CnC Beacon
-
suricata: ET MALWARE VNCStartServer USR Variant CnC Beacon
suricata: ET MALWARE VNCStartServer USR Variant CnC Beacon
-
DarkVNC Payload 2 IoCs
resource yara_rule behavioral1/memory/1704-59-0x0000000010000000-0x0000000010089000-memory.dmp darkvnc behavioral1/memory/1704-64-0x00000000030C0000-0x0000000003200000-memory.dmp darkvnc -
Suspicious use of SetThreadContext 1 IoCs
description pid Process procid_target PID 1704 set thread context of 2000 1704 3a9397af4dfc720df6b8d7c2949bcac307fd5c2540ca114904f43c162e0f4a4b.exe 29 -
Enumerates physical storage devices 1 TTPs
Attempts to interact with connected storage/optical drive(s). Likely ransomware behaviour.
-
Suspicious behavior: MapViewOfSection 1 IoCs
pid Process 1704 3a9397af4dfc720df6b8d7c2949bcac307fd5c2540ca114904f43c162e0f4a4b.exe -
Suspicious use of UnmapMainImage 1 IoCs
pid Process 1704 3a9397af4dfc720df6b8d7c2949bcac307fd5c2540ca114904f43c162e0f4a4b.exe -
Suspicious use of WriteProcessMemory 7 IoCs
description pid Process procid_target PID 1704 wrote to memory of 2000 1704 3a9397af4dfc720df6b8d7c2949bcac307fd5c2540ca114904f43c162e0f4a4b.exe 29 PID 1704 wrote to memory of 2000 1704 3a9397af4dfc720df6b8d7c2949bcac307fd5c2540ca114904f43c162e0f4a4b.exe 29 PID 1704 wrote to memory of 2000 1704 3a9397af4dfc720df6b8d7c2949bcac307fd5c2540ca114904f43c162e0f4a4b.exe 29 PID 1704 wrote to memory of 2000 1704 3a9397af4dfc720df6b8d7c2949bcac307fd5c2540ca114904f43c162e0f4a4b.exe 29 PID 1704 wrote to memory of 2000 1704 3a9397af4dfc720df6b8d7c2949bcac307fd5c2540ca114904f43c162e0f4a4b.exe 29 PID 1704 wrote to memory of 2000 1704 3a9397af4dfc720df6b8d7c2949bcac307fd5c2540ca114904f43c162e0f4a4b.exe 29 PID 1704 wrote to memory of 2000 1704 3a9397af4dfc720df6b8d7c2949bcac307fd5c2540ca114904f43c162e0f4a4b.exe 29
Processes
-
C:\Users\Admin\AppData\Local\Temp\3a9397af4dfc720df6b8d7c2949bcac307fd5c2540ca114904f43c162e0f4a4b.exe"C:\Users\Admin\AppData\Local\Temp\3a9397af4dfc720df6b8d7c2949bcac307fd5c2540ca114904f43c162e0f4a4b.exe"1⤵
- Suspicious use of SetThreadContext
- Suspicious behavior: MapViewOfSection
- Suspicious use of UnmapMainImage
- Suspicious use of WriteProcessMemory
PID:1704 -
C:\Windows\system32\WerFault.exeC:\Windows\system32\WerFault.exe2⤵PID:2000
-