Analysis
-
max time kernel
32s -
max time network
42s -
platform
windows7_x64 -
resource
win7-20220812-en -
resource tags
arch:x64arch:x86image:win7-20220812-enlocale:en-usos:windows7-x64system -
submitted
23-11-2022 17:16
Static task
static1
Behavioral task
behavioral1
Sample
63836b8bcbce046a92178bd2a692f28d7e7ba65e41d026465e3d7782003934dd.exe
Resource
win7-20220812-en
Behavioral task
behavioral2
Sample
63836b8bcbce046a92178bd2a692f28d7e7ba65e41d026465e3d7782003934dd.exe
Resource
win10v2004-20220812-en
General
-
Target
63836b8bcbce046a92178bd2a692f28d7e7ba65e41d026465e3d7782003934dd.exe
-
Size
35KB
-
MD5
521604fea8ec8d79c735385fa562bd40
-
SHA1
b2847cbe91a2be73364f5935312c99caaadbf8d6
-
SHA256
63836b8bcbce046a92178bd2a692f28d7e7ba65e41d026465e3d7782003934dd
-
SHA512
83a6a289a57cab837cbc537421dd897dd293ee50b8bd75221da2672c0b0343398a4c5b70388a10407b038495e09a44223015ed74a608aa09016a56d03fd8badf
-
SSDEEP
768:t3bSr3Ome2Om19VtFtkMI47Jpx9GvhpA8nPWvLerq5y5WcUOpsYsM:t3bYOme2Om19VtFtkMI47PGppA8OvL8b
Malware Config
Signatures
-
Maps connected drives based on registry 3 TTPs 2 IoCs
Disk information is often read in order to detect sandboxing environments.
Processes:
63836b8bcbce046a92178bd2a692f28d7e7ba65e41d026465e3d7782003934dd.exedescription ioc process Key opened \REGISTRY\MACHINE\SYSTEM\ControlSet001\Services\Disk\Enum 63836b8bcbce046a92178bd2a692f28d7e7ba65e41d026465e3d7782003934dd.exe Key value queried \REGISTRY\MACHINE\SYSTEM\ControlSet001\services\Disk\Enum\0 63836b8bcbce046a92178bd2a692f28d7e7ba65e41d026465e3d7782003934dd.exe -
Suspicious use of SetThreadContext 1 IoCs
Processes:
63836b8bcbce046a92178bd2a692f28d7e7ba65e41d026465e3d7782003934dd.exedescription pid process target process PID 2000 set thread context of 1952 2000 63836b8bcbce046a92178bd2a692f28d7e7ba65e41d026465e3d7782003934dd.exe 63836b8bcbce046a92178bd2a692f28d7e7ba65e41d026465e3d7782003934dd.exe -
Suspicious use of SetWindowsHookEx 3 IoCs
Processes:
63836b8bcbce046a92178bd2a692f28d7e7ba65e41d026465e3d7782003934dd.exe63836b8bcbce046a92178bd2a692f28d7e7ba65e41d026465e3d7782003934dd.exepid process 2000 63836b8bcbce046a92178bd2a692f28d7e7ba65e41d026465e3d7782003934dd.exe 1952 63836b8bcbce046a92178bd2a692f28d7e7ba65e41d026465e3d7782003934dd.exe 1952 63836b8bcbce046a92178bd2a692f28d7e7ba65e41d026465e3d7782003934dd.exe -
Suspicious use of WriteProcessMemory 10 IoCs
Processes:
63836b8bcbce046a92178bd2a692f28d7e7ba65e41d026465e3d7782003934dd.exedescription pid process target process PID 2000 wrote to memory of 1952 2000 63836b8bcbce046a92178bd2a692f28d7e7ba65e41d026465e3d7782003934dd.exe 63836b8bcbce046a92178bd2a692f28d7e7ba65e41d026465e3d7782003934dd.exe PID 2000 wrote to memory of 1952 2000 63836b8bcbce046a92178bd2a692f28d7e7ba65e41d026465e3d7782003934dd.exe 63836b8bcbce046a92178bd2a692f28d7e7ba65e41d026465e3d7782003934dd.exe PID 2000 wrote to memory of 1952 2000 63836b8bcbce046a92178bd2a692f28d7e7ba65e41d026465e3d7782003934dd.exe 63836b8bcbce046a92178bd2a692f28d7e7ba65e41d026465e3d7782003934dd.exe PID 2000 wrote to memory of 1952 2000 63836b8bcbce046a92178bd2a692f28d7e7ba65e41d026465e3d7782003934dd.exe 63836b8bcbce046a92178bd2a692f28d7e7ba65e41d026465e3d7782003934dd.exe PID 2000 wrote to memory of 1952 2000 63836b8bcbce046a92178bd2a692f28d7e7ba65e41d026465e3d7782003934dd.exe 63836b8bcbce046a92178bd2a692f28d7e7ba65e41d026465e3d7782003934dd.exe PID 2000 wrote to memory of 1952 2000 63836b8bcbce046a92178bd2a692f28d7e7ba65e41d026465e3d7782003934dd.exe 63836b8bcbce046a92178bd2a692f28d7e7ba65e41d026465e3d7782003934dd.exe PID 2000 wrote to memory of 1952 2000 63836b8bcbce046a92178bd2a692f28d7e7ba65e41d026465e3d7782003934dd.exe 63836b8bcbce046a92178bd2a692f28d7e7ba65e41d026465e3d7782003934dd.exe PID 2000 wrote to memory of 1952 2000 63836b8bcbce046a92178bd2a692f28d7e7ba65e41d026465e3d7782003934dd.exe 63836b8bcbce046a92178bd2a692f28d7e7ba65e41d026465e3d7782003934dd.exe PID 2000 wrote to memory of 1952 2000 63836b8bcbce046a92178bd2a692f28d7e7ba65e41d026465e3d7782003934dd.exe 63836b8bcbce046a92178bd2a692f28d7e7ba65e41d026465e3d7782003934dd.exe PID 2000 wrote to memory of 1952 2000 63836b8bcbce046a92178bd2a692f28d7e7ba65e41d026465e3d7782003934dd.exe 63836b8bcbce046a92178bd2a692f28d7e7ba65e41d026465e3d7782003934dd.exe
Processes
-
C:\Users\Admin\AppData\Local\Temp\63836b8bcbce046a92178bd2a692f28d7e7ba65e41d026465e3d7782003934dd.exe"C:\Users\Admin\AppData\Local\Temp\63836b8bcbce046a92178bd2a692f28d7e7ba65e41d026465e3d7782003934dd.exe"1⤵
- Suspicious use of SetThreadContext
- Suspicious use of SetWindowsHookEx
- Suspicious use of WriteProcessMemory
PID:2000 -
C:\Users\Admin\AppData\Local\Temp\63836b8bcbce046a92178bd2a692f28d7e7ba65e41d026465e3d7782003934dd.exea|2⤵
- Maps connected drives based on registry
- Suspicious use of SetWindowsHookEx
PID:1952