Analysis
-
max time kernel
146s -
max time network
150s -
platform
windows10-2004_x64 -
resource
win10v2004-20220812-en -
resource tags
arch:x64arch:x86image:win10v2004-20220812-enlocale:en-usos:windows10-2004-x64system -
submitted
12/10/2022, 15:23
Behavioral task
behavioral1
Sample
232e143beece4b5309dfabe7992ae47946f7a43a0b0e17815451c9b57151c22d.exe
Resource
win7-20220812-en
Behavioral task
behavioral2
Sample
232e143beece4b5309dfabe7992ae47946f7a43a0b0e17815451c9b57151c22d.exe
Resource
win10v2004-20220812-en
General
-
Target
232e143beece4b5309dfabe7992ae47946f7a43a0b0e17815451c9b57151c22d.exe
-
Size
1.4MB
-
MD5
60c2a4f146d2c135ecb47c5752da87e3
-
SHA1
8fdc11d813ee957524d21cecaaee8bdf9b8a8c7e
-
SHA256
232e143beece4b5309dfabe7992ae47946f7a43a0b0e17815451c9b57151c22d
-
SHA512
6e343ce230a9a4693e0a63c232305f138122ffaa599a86343d46c4623a4a082eb663ad7dc61e503921c7502e639d90a2d247f130158dbd487343b81f436e6922
-
SSDEEP
24576:1tAR2X07y9rxHgoA/38YTmP8RDfU3kHqIl4eZ94bNaQu:1tAR2ke91SSkRDfXqUFukF
Malware Config
Signatures
-
resource yara_rule behavioral2/memory/2604-132-0x0000000000400000-0x00000000004E6000-memory.dmp upx behavioral2/memory/2604-134-0x0000000000400000-0x00000000004E6000-memory.dmp upx -
AutoIT Executable 2 IoCs
AutoIT scripts compiled to PE executables.
resource yara_rule behavioral2/memory/2604-132-0x0000000000400000-0x00000000004E6000-memory.dmp autoit_exe behavioral2/memory/2604-134-0x0000000000400000-0x00000000004E6000-memory.dmp autoit_exe -
Suspicious use of SetThreadContext 1 IoCs
description pid Process procid_target PID 2604 set thread context of 4528 2604 232e143beece4b5309dfabe7992ae47946f7a43a0b0e17815451c9b57151c22d.exe 82 -
Enumerates physical storage devices 1 TTPs
Attempts to interact with connected storage/optical drive(s). Likely ransomware behaviour.
-
Program crash 2 IoCs
pid pid_target Process procid_target 2728 4528 WerFault.exe 82 4808 4528 WerFault.exe 82 -
Suspicious use of WriteProcessMemory 7 IoCs
description pid Process procid_target PID 2604 wrote to memory of 4528 2604 232e143beece4b5309dfabe7992ae47946f7a43a0b0e17815451c9b57151c22d.exe 82 PID 2604 wrote to memory of 4528 2604 232e143beece4b5309dfabe7992ae47946f7a43a0b0e17815451c9b57151c22d.exe 82 PID 2604 wrote to memory of 4528 2604 232e143beece4b5309dfabe7992ae47946f7a43a0b0e17815451c9b57151c22d.exe 82 PID 2604 wrote to memory of 4528 2604 232e143beece4b5309dfabe7992ae47946f7a43a0b0e17815451c9b57151c22d.exe 82 PID 2604 wrote to memory of 4528 2604 232e143beece4b5309dfabe7992ae47946f7a43a0b0e17815451c9b57151c22d.exe 82 PID 2604 wrote to memory of 4528 2604 232e143beece4b5309dfabe7992ae47946f7a43a0b0e17815451c9b57151c22d.exe 82 PID 2604 wrote to memory of 4528 2604 232e143beece4b5309dfabe7992ae47946f7a43a0b0e17815451c9b57151c22d.exe 82
Processes
-
C:\Users\Admin\AppData\Local\Temp\232e143beece4b5309dfabe7992ae47946f7a43a0b0e17815451c9b57151c22d.exe"C:\Users\Admin\AppData\Local\Temp\232e143beece4b5309dfabe7992ae47946f7a43a0b0e17815451c9b57151c22d.exe"1⤵
- Suspicious use of SetThreadContext
- Suspicious use of WriteProcessMemory
PID:2604 -
C:\Users\Admin\AppData\Local\Temp\232e143beece4b5309dfabe7992ae47946f7a43a0b0e17815451c9b57151c22d.exe"C:\Users\Admin\AppData\Local\Temp\232e143beece4b5309dfabe7992ae47946f7a43a0b0e17815451c9b57151c22d.exe"2⤵PID:4528
-
C:\Windows\SysWOW64\WerFault.exeC:\Windows\SysWOW64\WerFault.exe -u -p 4528 -s 123⤵
- Program crash
PID:2728
-
-
C:\Windows\SysWOW64\WerFault.exeC:\Windows\SysWOW64\WerFault.exe -u -p 4528 -s 203⤵
- Program crash
PID:4808
-
-
-
C:\Windows\SysWOW64\WerFault.exeC:\Windows\SysWOW64\WerFault.exe -pss -s 428 -p 4528 -ip 45281⤵PID:4972
-
C:\Windows\SysWOW64\WerFault.exeC:\Windows\SysWOW64\WerFault.exe -pss -s 504 -p 4528 -ip 45281⤵PID:4712