Analysis
-
max time kernel
91s -
max time network
154s -
platform
windows10-2004_x64 -
resource
win10v2004-20220901-en -
resource tags
arch:x64arch:x86image:win10v2004-20220901-enlocale:en-usos:windows10-2004-x64system -
submitted
26-11-2022 04:21
Static task
static1
Behavioral task
behavioral1
Sample
4c2da4163626cfc3f5df2833244f62226e09029b60736efc4d8272d217b0bf1c.exe
Resource
win7-20221111-en
Behavioral task
behavioral2
Sample
4c2da4163626cfc3f5df2833244f62226e09029b60736efc4d8272d217b0bf1c.exe
Resource
win10v2004-20220901-en
General
-
Target
4c2da4163626cfc3f5df2833244f62226e09029b60736efc4d8272d217b0bf1c.exe
-
Size
828KB
-
MD5
177c62e5ce48ab97f565f1912cb46c55
-
SHA1
7c9822da841e6df900d306d799e460583eb332eb
-
SHA256
4c2da4163626cfc3f5df2833244f62226e09029b60736efc4d8272d217b0bf1c
-
SHA512
98e60eb2530aa8717f39dc0cec713c0d8e413fd44eb4aeb2578b7d979ece8a761c638f33a066eb3044d4679ee208b10a9f91ae3fd072b6b9ecfd8b6521e1ba77
-
SSDEEP
24576:2DFhwFzsQNLAr5bj/b4FKHrJ841gAQguqMwPt:mFhwFzPBYb02y4SA5Mw
Malware Config
Signatures
-
Checks BIOS information in registry 2 TTPs 3 IoCs
BIOS information is often read in order to detect sandboxing environments.
Processes:
4c2da4163626cfc3f5df2833244f62226e09029b60736efc4d8272d217b0bf1c.exe4c2da4163626cfc3f5df2833244f62226e09029b60736efc4d8272d217b0bf1c.exedescription ioc process Key value queried \REGISTRY\MACHINE\HARDWARE\DESCRIPTION\System\SystemBiosVersion 4c2da4163626cfc3f5df2833244f62226e09029b60736efc4d8272d217b0bf1c.exe Key value queried \REGISTRY\MACHINE\HARDWARE\DESCRIPTION\System\VideoBiosVersion 4c2da4163626cfc3f5df2833244f62226e09029b60736efc4d8272d217b0bf1c.exe Key value queried \REGISTRY\MACHINE\HARDWARE\DESCRIPTION\System\SystemBiosVersion 4c2da4163626cfc3f5df2833244f62226e09029b60736efc4d8272d217b0bf1c.exe -
Checks installed software on the system 1 TTPs
Looks up Uninstall key entries in the registry to enumerate software on the system.
-
Maps connected drives based on registry 3 TTPs 4 IoCs
Disk information is often read in order to detect sandboxing environments.
Processes:
4c2da4163626cfc3f5df2833244f62226e09029b60736efc4d8272d217b0bf1c.exe4c2da4163626cfc3f5df2833244f62226e09029b60736efc4d8272d217b0bf1c.exedescription ioc process Key opened \REGISTRY\MACHINE\SYSTEM\ControlSet001\Services\Disk\Enum 4c2da4163626cfc3f5df2833244f62226e09029b60736efc4d8272d217b0bf1c.exe Key value queried \REGISTRY\MACHINE\SYSTEM\ControlSet001\Services\disk\Enum\0 4c2da4163626cfc3f5df2833244f62226e09029b60736efc4d8272d217b0bf1c.exe Key opened \REGISTRY\MACHINE\SYSTEM\ControlSet001\Services\Disk\Enum 4c2da4163626cfc3f5df2833244f62226e09029b60736efc4d8272d217b0bf1c.exe Key value queried \REGISTRY\MACHINE\SYSTEM\ControlSet001\Services\disk\Enum\0 4c2da4163626cfc3f5df2833244f62226e09029b60736efc4d8272d217b0bf1c.exe -
Suspicious use of SetThreadContext 1 IoCs
Processes:
4c2da4163626cfc3f5df2833244f62226e09029b60736efc4d8272d217b0bf1c.exedescription pid process target process PID 4960 set thread context of 1664 4960 4c2da4163626cfc3f5df2833244f62226e09029b60736efc4d8272d217b0bf1c.exe 4c2da4163626cfc3f5df2833244f62226e09029b60736efc4d8272d217b0bf1c.exe -
Suspicious use of SetWindowsHookEx 6 IoCs
Processes:
4c2da4163626cfc3f5df2833244f62226e09029b60736efc4d8272d217b0bf1c.exepid process 1664 4c2da4163626cfc3f5df2833244f62226e09029b60736efc4d8272d217b0bf1c.exe 1664 4c2da4163626cfc3f5df2833244f62226e09029b60736efc4d8272d217b0bf1c.exe 1664 4c2da4163626cfc3f5df2833244f62226e09029b60736efc4d8272d217b0bf1c.exe 1664 4c2da4163626cfc3f5df2833244f62226e09029b60736efc4d8272d217b0bf1c.exe 1664 4c2da4163626cfc3f5df2833244f62226e09029b60736efc4d8272d217b0bf1c.exe 1664 4c2da4163626cfc3f5df2833244f62226e09029b60736efc4d8272d217b0bf1c.exe -
Suspicious use of WriteProcessMemory 10 IoCs
Processes:
4c2da4163626cfc3f5df2833244f62226e09029b60736efc4d8272d217b0bf1c.exedescription pid process target process PID 4960 wrote to memory of 1664 4960 4c2da4163626cfc3f5df2833244f62226e09029b60736efc4d8272d217b0bf1c.exe 4c2da4163626cfc3f5df2833244f62226e09029b60736efc4d8272d217b0bf1c.exe PID 4960 wrote to memory of 1664 4960 4c2da4163626cfc3f5df2833244f62226e09029b60736efc4d8272d217b0bf1c.exe 4c2da4163626cfc3f5df2833244f62226e09029b60736efc4d8272d217b0bf1c.exe PID 4960 wrote to memory of 1664 4960 4c2da4163626cfc3f5df2833244f62226e09029b60736efc4d8272d217b0bf1c.exe 4c2da4163626cfc3f5df2833244f62226e09029b60736efc4d8272d217b0bf1c.exe PID 4960 wrote to memory of 1664 4960 4c2da4163626cfc3f5df2833244f62226e09029b60736efc4d8272d217b0bf1c.exe 4c2da4163626cfc3f5df2833244f62226e09029b60736efc4d8272d217b0bf1c.exe PID 4960 wrote to memory of 1664 4960 4c2da4163626cfc3f5df2833244f62226e09029b60736efc4d8272d217b0bf1c.exe 4c2da4163626cfc3f5df2833244f62226e09029b60736efc4d8272d217b0bf1c.exe PID 4960 wrote to memory of 1664 4960 4c2da4163626cfc3f5df2833244f62226e09029b60736efc4d8272d217b0bf1c.exe 4c2da4163626cfc3f5df2833244f62226e09029b60736efc4d8272d217b0bf1c.exe PID 4960 wrote to memory of 1664 4960 4c2da4163626cfc3f5df2833244f62226e09029b60736efc4d8272d217b0bf1c.exe 4c2da4163626cfc3f5df2833244f62226e09029b60736efc4d8272d217b0bf1c.exe PID 4960 wrote to memory of 1664 4960 4c2da4163626cfc3f5df2833244f62226e09029b60736efc4d8272d217b0bf1c.exe 4c2da4163626cfc3f5df2833244f62226e09029b60736efc4d8272d217b0bf1c.exe PID 4960 wrote to memory of 1664 4960 4c2da4163626cfc3f5df2833244f62226e09029b60736efc4d8272d217b0bf1c.exe 4c2da4163626cfc3f5df2833244f62226e09029b60736efc4d8272d217b0bf1c.exe PID 4960 wrote to memory of 1664 4960 4c2da4163626cfc3f5df2833244f62226e09029b60736efc4d8272d217b0bf1c.exe 4c2da4163626cfc3f5df2833244f62226e09029b60736efc4d8272d217b0bf1c.exe
Processes
-
C:\Users\Admin\AppData\Local\Temp\4c2da4163626cfc3f5df2833244f62226e09029b60736efc4d8272d217b0bf1c.exe"C:\Users\Admin\AppData\Local\Temp\4c2da4163626cfc3f5df2833244f62226e09029b60736efc4d8272d217b0bf1c.exe"1⤵
- Checks BIOS information in registry
- Maps connected drives based on registry
- Suspicious use of SetThreadContext
- Suspicious use of WriteProcessMemory
-
C:\Users\Admin\AppData\Local\Temp\4c2da4163626cfc3f5df2833244f62226e09029b60736efc4d8272d217b0bf1c.exe"C:\Users\Admin\AppData\Local\Temp\4c2da4163626cfc3f5df2833244f62226e09029b60736efc4d8272d217b0bf1c.exe" Track="0001101000"2⤵
- Checks BIOS information in registry
- Maps connected drives based on registry
- Suspicious use of SetWindowsHookEx
Network
MITRE ATT&CK Matrix ATT&CK v6
Replay Monitor
Loading Replay Monitor...
Downloads
-
memory/1664-137-0x0000000000000000-mapping.dmp
-
memory/1664-138-0x0000000000400000-0x00000000005BC000-memory.dmpFilesize
1.7MB
-
memory/1664-139-0x0000000000400000-0x00000000005BC000-memory.dmpFilesize
1.7MB
-
memory/1664-141-0x0000000000400000-0x00000000005BC000-memory.dmpFilesize
1.7MB
-
memory/1664-142-0x0000000000400000-0x00000000005BC000-memory.dmpFilesize
1.7MB
-
memory/1664-143-0x0000000000400000-0x00000000005BC000-memory.dmpFilesize
1.7MB
-
memory/4960-135-0x0000000000650000-0x0000000000653000-memory.dmpFilesize
12KB
-
memory/4960-136-0x0000000000400000-0x00000000004F6000-memory.dmpFilesize
984KB
-
memory/4960-140-0x0000000000400000-0x00000000004F6000-memory.dmpFilesize
984KB