Analysis
-
max time kernel
149s -
max time network
194s -
platform
windows10-2004_x64 -
resource
win10v2004-20221111-en -
resource tags
arch:x64arch:x86image:win10v2004-20221111-enlocale:en-usos:windows10-2004-x64system -
submitted
23-11-2022 12:45
Static task
static1
Behavioral task
behavioral1
Sample
60f5021132d35db743954c0f0e102456cd8d71e44cfa569b495275b31eb9785a.exe
Resource
win7-20221111-en
Behavioral task
behavioral2
Sample
60f5021132d35db743954c0f0e102456cd8d71e44cfa569b495275b31eb9785a.exe
Resource
win10v2004-20221111-en
General
-
Target
60f5021132d35db743954c0f0e102456cd8d71e44cfa569b495275b31eb9785a.exe
-
Size
1.6MB
-
MD5
63a806ecb8376c61a45a6c10e709dd5a
-
SHA1
8c3cc108d38b956722412fc8c0713738defe60a3
-
SHA256
60f5021132d35db743954c0f0e102456cd8d71e44cfa569b495275b31eb9785a
-
SHA512
1f9a319c439739d286f1660765b7b05fc37b03ab741da58fe757cd6b4c0aeffa5aca68dcd33143d5c0122acc731e734d223e773107ef17bd12d29d1fdb745057
-
SSDEEP
24576:NzD5urNhRWx2Mk4JJQByw7Imlq3g495S0PwbphrpgXXOZuv/rTWeR5j4UwJZQUYC:n6/ye0PIphrp9Zuvjqa0UidJ
Malware Config
Signatures
-
Suspicious use of SetThreadContext 1 IoCs
Processes:
60f5021132d35db743954c0f0e102456cd8d71e44cfa569b495275b31eb9785a.exedescription pid process target process PID 1900 set thread context of 3332 1900 60f5021132d35db743954c0f0e102456cd8d71e44cfa569b495275b31eb9785a.exe 60f5021132d35db743954c0f0e102456cd8d71e44cfa569b495275b31eb9785a.exe -
Suspicious use of SetWindowsHookEx 5 IoCs
Processes:
60f5021132d35db743954c0f0e102456cd8d71e44cfa569b495275b31eb9785a.exepid process 3332 60f5021132d35db743954c0f0e102456cd8d71e44cfa569b495275b31eb9785a.exe 3332 60f5021132d35db743954c0f0e102456cd8d71e44cfa569b495275b31eb9785a.exe 3332 60f5021132d35db743954c0f0e102456cd8d71e44cfa569b495275b31eb9785a.exe 3332 60f5021132d35db743954c0f0e102456cd8d71e44cfa569b495275b31eb9785a.exe 3332 60f5021132d35db743954c0f0e102456cd8d71e44cfa569b495275b31eb9785a.exe -
Suspicious use of WriteProcessMemory 10 IoCs
Processes:
60f5021132d35db743954c0f0e102456cd8d71e44cfa569b495275b31eb9785a.exedescription pid process target process PID 1900 wrote to memory of 3332 1900 60f5021132d35db743954c0f0e102456cd8d71e44cfa569b495275b31eb9785a.exe 60f5021132d35db743954c0f0e102456cd8d71e44cfa569b495275b31eb9785a.exe PID 1900 wrote to memory of 3332 1900 60f5021132d35db743954c0f0e102456cd8d71e44cfa569b495275b31eb9785a.exe 60f5021132d35db743954c0f0e102456cd8d71e44cfa569b495275b31eb9785a.exe PID 1900 wrote to memory of 3332 1900 60f5021132d35db743954c0f0e102456cd8d71e44cfa569b495275b31eb9785a.exe 60f5021132d35db743954c0f0e102456cd8d71e44cfa569b495275b31eb9785a.exe PID 1900 wrote to memory of 3332 1900 60f5021132d35db743954c0f0e102456cd8d71e44cfa569b495275b31eb9785a.exe 60f5021132d35db743954c0f0e102456cd8d71e44cfa569b495275b31eb9785a.exe PID 1900 wrote to memory of 3332 1900 60f5021132d35db743954c0f0e102456cd8d71e44cfa569b495275b31eb9785a.exe 60f5021132d35db743954c0f0e102456cd8d71e44cfa569b495275b31eb9785a.exe PID 1900 wrote to memory of 3332 1900 60f5021132d35db743954c0f0e102456cd8d71e44cfa569b495275b31eb9785a.exe 60f5021132d35db743954c0f0e102456cd8d71e44cfa569b495275b31eb9785a.exe PID 1900 wrote to memory of 3332 1900 60f5021132d35db743954c0f0e102456cd8d71e44cfa569b495275b31eb9785a.exe 60f5021132d35db743954c0f0e102456cd8d71e44cfa569b495275b31eb9785a.exe PID 1900 wrote to memory of 3332 1900 60f5021132d35db743954c0f0e102456cd8d71e44cfa569b495275b31eb9785a.exe 60f5021132d35db743954c0f0e102456cd8d71e44cfa569b495275b31eb9785a.exe PID 1900 wrote to memory of 3332 1900 60f5021132d35db743954c0f0e102456cd8d71e44cfa569b495275b31eb9785a.exe 60f5021132d35db743954c0f0e102456cd8d71e44cfa569b495275b31eb9785a.exe PID 1900 wrote to memory of 3332 1900 60f5021132d35db743954c0f0e102456cd8d71e44cfa569b495275b31eb9785a.exe 60f5021132d35db743954c0f0e102456cd8d71e44cfa569b495275b31eb9785a.exe
Processes
-
C:\Users\Admin\AppData\Local\Temp\60f5021132d35db743954c0f0e102456cd8d71e44cfa569b495275b31eb9785a.exe"C:\Users\Admin\AppData\Local\Temp\60f5021132d35db743954c0f0e102456cd8d71e44cfa569b495275b31eb9785a.exe"1⤵
- Suspicious use of SetThreadContext
- Suspicious use of WriteProcessMemory
-
C:\Users\Admin\AppData\Local\Temp\60f5021132d35db743954c0f0e102456cd8d71e44cfa569b495275b31eb9785a.exe"C:\Users\Admin\AppData\Local\Temp\60f5021132d35db743954c0f0e102456cd8d71e44cfa569b495275b31eb9785a.exe"2⤵
- Suspicious use of SetWindowsHookEx
Network
MITRE ATT&CK Matrix
Replay Monitor
Loading Replay Monitor...
Downloads
-
memory/3332-132-0x0000000000000000-mapping.dmp
-
memory/3332-133-0x0000000000400000-0x00000000004DF000-memory.dmpFilesize
892KB
-
memory/3332-134-0x0000000000400000-0x00000000004DF000-memory.dmpFilesize
892KB
-
memory/3332-135-0x0000000000400000-0x00000000004DF000-memory.dmpFilesize
892KB
-
memory/3332-136-0x0000000000400000-0x00000000004DF000-memory.dmpFilesize
892KB
-
memory/3332-137-0x0000000000400000-0x00000000004DF000-memory.dmpFilesize
892KB
-
memory/3332-138-0x0000000000400000-0x00000000004DF000-memory.dmpFilesize
892KB