Analysis
-
max time kernel
149s -
max time network
152s -
platform
windows10-2004_x64 -
resource
win10v2004-20220812-en -
resource tags
arch:x64arch:x86image:win10v2004-20220812-enlocale:en-usos:windows10-2004-x64system -
submitted
27-11-2022 08:29
Static task
static1
Behavioral task
behavioral1
Sample
1da96f88bcd814dea20448b23a7c8bf3b23691f53b28ed84ae2cebe89c93d313.exe
Resource
win7-20221111-en
Behavioral task
behavioral2
Sample
1da96f88bcd814dea20448b23a7c8bf3b23691f53b28ed84ae2cebe89c93d313.exe
Resource
win10v2004-20220812-en
General
-
Target
1da96f88bcd814dea20448b23a7c8bf3b23691f53b28ed84ae2cebe89c93d313.exe
-
Size
1.0MB
-
MD5
d68c6c29a59a91be6bf91c560a5681c6
-
SHA1
f24265a921d7af5b6e49a1c81a7b0fbd417ccca4
-
SHA256
1da96f88bcd814dea20448b23a7c8bf3b23691f53b28ed84ae2cebe89c93d313
-
SHA512
4be2b9aed42ae9d9f5024d6e8a2a21f4510f6bb45c1d8012d77ba57788ed25e88e284c90d83b994d28b46209986584e28881098a040b59ff5a366411ec256f8c
-
SSDEEP
24576:ilafNPaNMDJOpKROZRpulZBVOkeOLimGHCmO+:CaANaRGRpuHetmGimZ
Malware Config
Signatures
-
Checks BIOS information in registry 2 TTPs 2 IoCs
BIOS information is often read in order to detect sandboxing environments.
Processes:
1da96f88bcd814dea20448b23a7c8bf3b23691f53b28ed84ae2cebe89c93d313.exedescription ioc process Key value queried \REGISTRY\MACHINE\HARDWARE\DESCRIPTION\System\SystemBiosVersion 1da96f88bcd814dea20448b23a7c8bf3b23691f53b28ed84ae2cebe89c93d313.exe Key value queried \REGISTRY\MACHINE\HARDWARE\DESCRIPTION\System\VideoBiosVersion 1da96f88bcd814dea20448b23a7c8bf3b23691f53b28ed84ae2cebe89c93d313.exe -
Maps connected drives based on registry 3 TTPs 2 IoCs
Disk information is often read in order to detect sandboxing environments.
Processes:
1da96f88bcd814dea20448b23a7c8bf3b23691f53b28ed84ae2cebe89c93d313.exedescription ioc process Key opened \REGISTRY\MACHINE\SYSTEM\ControlSet001\Services\Disk\Enum 1da96f88bcd814dea20448b23a7c8bf3b23691f53b28ed84ae2cebe89c93d313.exe Key value queried \REGISTRY\MACHINE\SYSTEM\ControlSet001\Services\disk\Enum\0 1da96f88bcd814dea20448b23a7c8bf3b23691f53b28ed84ae2cebe89c93d313.exe -
Suspicious use of SetThreadContext 1 IoCs
Processes:
1da96f88bcd814dea20448b23a7c8bf3b23691f53b28ed84ae2cebe89c93d313.exedescription pid process target process PID 5072 set thread context of 4976 5072 1da96f88bcd814dea20448b23a7c8bf3b23691f53b28ed84ae2cebe89c93d313.exe 1da96f88bcd814dea20448b23a7c8bf3b23691f53b28ed84ae2cebe89c93d313.exe -
Suspicious use of SetWindowsHookEx 6 IoCs
Processes:
1da96f88bcd814dea20448b23a7c8bf3b23691f53b28ed84ae2cebe89c93d313.exepid process 4976 1da96f88bcd814dea20448b23a7c8bf3b23691f53b28ed84ae2cebe89c93d313.exe 4976 1da96f88bcd814dea20448b23a7c8bf3b23691f53b28ed84ae2cebe89c93d313.exe 4976 1da96f88bcd814dea20448b23a7c8bf3b23691f53b28ed84ae2cebe89c93d313.exe 4976 1da96f88bcd814dea20448b23a7c8bf3b23691f53b28ed84ae2cebe89c93d313.exe 4976 1da96f88bcd814dea20448b23a7c8bf3b23691f53b28ed84ae2cebe89c93d313.exe 4976 1da96f88bcd814dea20448b23a7c8bf3b23691f53b28ed84ae2cebe89c93d313.exe -
Suspicious use of WriteProcessMemory 10 IoCs
Processes:
1da96f88bcd814dea20448b23a7c8bf3b23691f53b28ed84ae2cebe89c93d313.exedescription pid process target process PID 5072 wrote to memory of 4976 5072 1da96f88bcd814dea20448b23a7c8bf3b23691f53b28ed84ae2cebe89c93d313.exe 1da96f88bcd814dea20448b23a7c8bf3b23691f53b28ed84ae2cebe89c93d313.exe PID 5072 wrote to memory of 4976 5072 1da96f88bcd814dea20448b23a7c8bf3b23691f53b28ed84ae2cebe89c93d313.exe 1da96f88bcd814dea20448b23a7c8bf3b23691f53b28ed84ae2cebe89c93d313.exe PID 5072 wrote to memory of 4976 5072 1da96f88bcd814dea20448b23a7c8bf3b23691f53b28ed84ae2cebe89c93d313.exe 1da96f88bcd814dea20448b23a7c8bf3b23691f53b28ed84ae2cebe89c93d313.exe PID 5072 wrote to memory of 4976 5072 1da96f88bcd814dea20448b23a7c8bf3b23691f53b28ed84ae2cebe89c93d313.exe 1da96f88bcd814dea20448b23a7c8bf3b23691f53b28ed84ae2cebe89c93d313.exe PID 5072 wrote to memory of 4976 5072 1da96f88bcd814dea20448b23a7c8bf3b23691f53b28ed84ae2cebe89c93d313.exe 1da96f88bcd814dea20448b23a7c8bf3b23691f53b28ed84ae2cebe89c93d313.exe PID 5072 wrote to memory of 4976 5072 1da96f88bcd814dea20448b23a7c8bf3b23691f53b28ed84ae2cebe89c93d313.exe 1da96f88bcd814dea20448b23a7c8bf3b23691f53b28ed84ae2cebe89c93d313.exe PID 5072 wrote to memory of 4976 5072 1da96f88bcd814dea20448b23a7c8bf3b23691f53b28ed84ae2cebe89c93d313.exe 1da96f88bcd814dea20448b23a7c8bf3b23691f53b28ed84ae2cebe89c93d313.exe PID 5072 wrote to memory of 4976 5072 1da96f88bcd814dea20448b23a7c8bf3b23691f53b28ed84ae2cebe89c93d313.exe 1da96f88bcd814dea20448b23a7c8bf3b23691f53b28ed84ae2cebe89c93d313.exe PID 5072 wrote to memory of 4976 5072 1da96f88bcd814dea20448b23a7c8bf3b23691f53b28ed84ae2cebe89c93d313.exe 1da96f88bcd814dea20448b23a7c8bf3b23691f53b28ed84ae2cebe89c93d313.exe PID 5072 wrote to memory of 4976 5072 1da96f88bcd814dea20448b23a7c8bf3b23691f53b28ed84ae2cebe89c93d313.exe 1da96f88bcd814dea20448b23a7c8bf3b23691f53b28ed84ae2cebe89c93d313.exe
Processes
-
C:\Users\Admin\AppData\Local\Temp\1da96f88bcd814dea20448b23a7c8bf3b23691f53b28ed84ae2cebe89c93d313.exe"C:\Users\Admin\AppData\Local\Temp\1da96f88bcd814dea20448b23a7c8bf3b23691f53b28ed84ae2cebe89c93d313.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\1da96f88bcd814dea20448b23a7c8bf3b23691f53b28ed84ae2cebe89c93d313.exe"C:\Users\Admin\AppData\Local\Temp\1da96f88bcd814dea20448b23a7c8bf3b23691f53b28ed84ae2cebe89c93d313.exe" Track="0001001000"2⤵
- Suspicious use of SetWindowsHookEx
Network
MITRE ATT&CK Matrix ATT&CK v6
Replay Monitor
Loading Replay Monitor...
Downloads
-
memory/4976-134-0x0000000000000000-mapping.dmp
-
memory/4976-135-0x0000000000400000-0x00000000004F6000-memory.dmpFilesize
984KB
-
memory/4976-136-0x0000000000400000-0x00000000004F6000-memory.dmpFilesize
984KB
-
memory/4976-138-0x0000000000400000-0x00000000004F6000-memory.dmpFilesize
984KB
-
memory/4976-139-0x0000000000400000-0x00000000004F6000-memory.dmpFilesize
984KB
-
memory/4976-140-0x0000000000400000-0x00000000004F6000-memory.dmpFilesize
984KB
-
memory/5072-132-0x0000000000730000-0x0000000000733000-memory.dmpFilesize
12KB
-
memory/5072-133-0x0000000000400000-0x0000000000581000-memory.dmpFilesize
1.5MB
-
memory/5072-137-0x0000000000400000-0x0000000000581000-memory.dmpFilesize
1.5MB