Analysis
-
max time kernel
163s -
max time network
229s -
platform
windows10-2004_x64 -
resource
win10v2004-20221111-en -
resource tags
arch:x64arch:x86image:win10v2004-20221111-enlocale:en-usos:windows10-2004-x64system -
submitted
03/12/2022, 17:47
Behavioral task
behavioral1
Sample
92fa06f11a2b691c6f678248be1eb5fb03b618173b860f6130a519be5ffd3470.exe
Resource
win7-20220812-en
5 signatures
150 seconds
Behavioral task
behavioral2
Sample
92fa06f11a2b691c6f678248be1eb5fb03b618173b860f6130a519be5ffd3470.exe
Resource
win10v2004-20221111-en
5 signatures
150 seconds
General
-
Target
92fa06f11a2b691c6f678248be1eb5fb03b618173b860f6130a519be5ffd3470.exe
-
Size
57KB
-
MD5
85a5c5d598a7066a458dec18df2cdc52
-
SHA1
cbf8a6a61e0cd1ff54efbd68e78bded6943b6dc1
-
SHA256
92fa06f11a2b691c6f678248be1eb5fb03b618173b860f6130a519be5ffd3470
-
SHA512
6f7f9222e0450d43d51d9e2e018d09e60165fa5211a53598327f1703ca43b762e1139f4b4df18474f347cf01585b0bd97b95651147188b3bb55b550fd6b69327
-
SSDEEP
768:w6GXE4XQNnpDnvj2/mpN8AGKkKTrPBcf4Aqrd2lHEj2cdFG8s5q:w6eDgN2CyA7kKhU4brkkHdfs5q
Score
8/10
Malware Config
Signatures
-
resource yara_rule behavioral2/memory/4936-137-0x0000000000400000-0x000000000040C000-memory.dmp upx -
Suspicious use of SetThreadContext 1 IoCs
description pid Process procid_target PID 4936 set thread context of 4356 4936 92fa06f11a2b691c6f678248be1eb5fb03b618173b860f6130a519be5ffd3470.exe 84 -
Program crash 1 IoCs
pid pid_target Process procid_target 4904 4356 WerFault.exe 84 -
Suspicious use of SetWindowsHookEx 1 IoCs
pid Process 4936 92fa06f11a2b691c6f678248be1eb5fb03b618173b860f6130a519be5ffd3470.exe -
Suspicious use of WriteProcessMemory 7 IoCs
description pid Process procid_target PID 4936 wrote to memory of 4356 4936 92fa06f11a2b691c6f678248be1eb5fb03b618173b860f6130a519be5ffd3470.exe 84 PID 4936 wrote to memory of 4356 4936 92fa06f11a2b691c6f678248be1eb5fb03b618173b860f6130a519be5ffd3470.exe 84 PID 4936 wrote to memory of 4356 4936 92fa06f11a2b691c6f678248be1eb5fb03b618173b860f6130a519be5ffd3470.exe 84 PID 4936 wrote to memory of 4356 4936 92fa06f11a2b691c6f678248be1eb5fb03b618173b860f6130a519be5ffd3470.exe 84 PID 4936 wrote to memory of 4356 4936 92fa06f11a2b691c6f678248be1eb5fb03b618173b860f6130a519be5ffd3470.exe 84 PID 4936 wrote to memory of 4356 4936 92fa06f11a2b691c6f678248be1eb5fb03b618173b860f6130a519be5ffd3470.exe 84 PID 4936 wrote to memory of 4356 4936 92fa06f11a2b691c6f678248be1eb5fb03b618173b860f6130a519be5ffd3470.exe 84
Processes
-
C:\Users\Admin\AppData\Local\Temp\92fa06f11a2b691c6f678248be1eb5fb03b618173b860f6130a519be5ffd3470.exe"C:\Users\Admin\AppData\Local\Temp\92fa06f11a2b691c6f678248be1eb5fb03b618173b860f6130a519be5ffd3470.exe"1⤵
- Suspicious use of SetThreadContext
- Suspicious use of SetWindowsHookEx
- Suspicious use of WriteProcessMemory
PID:4936 -
C:\Users\Admin\AppData\Local\Temp\92fa06f11a2b691c6f678248be1eb5fb03b618173b860f6130a519be5ffd3470.exeC:\Users\Admin\AppData\Local\Temp\92fa06f11a2b691c6f678248be1eb5fb03b618173b860f6130a519be5ffd3470.exe2⤵PID:4356
-
C:\Windows\SysWOW64\WerFault.exeC:\Windows\SysWOW64\WerFault.exe -u -p 4356 -s 4563⤵
- Program crash
PID:4904
-
-
-
C:\Windows\SysWOW64\WerFault.exeC:\Windows\SysWOW64\WerFault.exe -pss -s 408 -p 4356 -ip 43561⤵PID:3624