Analysis
-
max time kernel
40s -
max time network
45s -
platform
windows7_x64 -
resource
win7-20220812-en -
resource tags
arch:x64arch:x86image:win7-20220812-enlocale:en-usos:windows7-x64system -
submitted
26-11-2022 04:13
Static task
static1
Behavioral task
behavioral1
Sample
640ec1f3d053f145abbc471ce754a3d0b0f1a9c1f5b5258c2210ae768f1b7439.exe
Resource
win7-20220812-en
Behavioral task
behavioral2
Sample
640ec1f3d053f145abbc471ce754a3d0b0f1a9c1f5b5258c2210ae768f1b7439.exe
Resource
win10v2004-20220812-en
General
-
Target
640ec1f3d053f145abbc471ce754a3d0b0f1a9c1f5b5258c2210ae768f1b7439.exe
-
Size
828KB
-
MD5
0b397d32bed3b670e484f93919fa9303
-
SHA1
561a6f86087ff0b77e452dec57a31310a71012ae
-
SHA256
640ec1f3d053f145abbc471ce754a3d0b0f1a9c1f5b5258c2210ae768f1b7439
-
SHA512
415cba124b32f7bfab65b83a453123c427f7bea16b1e3b31079d1cebffd7a6e7aff9fd3cd72ac24d6a50ad7b52234b38251808caf8997df526718e7510d30453
-
SSDEEP
24576:fDFhwFzsQNLAr5bj/b4FKHrJ841gAQguqMwPJ:bFhwFzPBYb02y4SA5M0
Malware Config
Signatures
-
Checks BIOS information in registry 2 TTPs 3 IoCs
BIOS information is often read in order to detect sandboxing environments.
Processes:
640ec1f3d053f145abbc471ce754a3d0b0f1a9c1f5b5258c2210ae768f1b7439.exe640ec1f3d053f145abbc471ce754a3d0b0f1a9c1f5b5258c2210ae768f1b7439.exedescription ioc process Key value queried \REGISTRY\MACHINE\HARDWARE\DESCRIPTION\System\VideoBiosVersion 640ec1f3d053f145abbc471ce754a3d0b0f1a9c1f5b5258c2210ae768f1b7439.exe Key value queried \REGISTRY\MACHINE\HARDWARE\DESCRIPTION\System\SystemBiosVersion 640ec1f3d053f145abbc471ce754a3d0b0f1a9c1f5b5258c2210ae768f1b7439.exe Key value queried \REGISTRY\MACHINE\HARDWARE\DESCRIPTION\System\SystemBiosVersion 640ec1f3d053f145abbc471ce754a3d0b0f1a9c1f5b5258c2210ae768f1b7439.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:
640ec1f3d053f145abbc471ce754a3d0b0f1a9c1f5b5258c2210ae768f1b7439.exe640ec1f3d053f145abbc471ce754a3d0b0f1a9c1f5b5258c2210ae768f1b7439.exedescription ioc process Key opened \REGISTRY\MACHINE\SYSTEM\ControlSet001\Services\Disk\Enum 640ec1f3d053f145abbc471ce754a3d0b0f1a9c1f5b5258c2210ae768f1b7439.exe Key value queried \REGISTRY\MACHINE\SYSTEM\ControlSet001\services\Disk\Enum\0 640ec1f3d053f145abbc471ce754a3d0b0f1a9c1f5b5258c2210ae768f1b7439.exe Key opened \REGISTRY\MACHINE\SYSTEM\ControlSet001\Services\Disk\Enum 640ec1f3d053f145abbc471ce754a3d0b0f1a9c1f5b5258c2210ae768f1b7439.exe Key value queried \REGISTRY\MACHINE\SYSTEM\ControlSet001\services\Disk\Enum\0 640ec1f3d053f145abbc471ce754a3d0b0f1a9c1f5b5258c2210ae768f1b7439.exe -
Suspicious use of SetThreadContext 1 IoCs
Processes:
640ec1f3d053f145abbc471ce754a3d0b0f1a9c1f5b5258c2210ae768f1b7439.exedescription pid process target process PID 1248 set thread context of 952 1248 640ec1f3d053f145abbc471ce754a3d0b0f1a9c1f5b5258c2210ae768f1b7439.exe 640ec1f3d053f145abbc471ce754a3d0b0f1a9c1f5b5258c2210ae768f1b7439.exe -
Processes:
640ec1f3d053f145abbc471ce754a3d0b0f1a9c1f5b5258c2210ae768f1b7439.exedescription ioc process Key created \REGISTRY\USER\S-1-5-21-999675638-2867687379-27515722-1000\Software\Microsoft\Internet Explorer\Main 640ec1f3d053f145abbc471ce754a3d0b0f1a9c1f5b5258c2210ae768f1b7439.exe -
Suspicious use of SetWindowsHookEx 6 IoCs
Processes:
640ec1f3d053f145abbc471ce754a3d0b0f1a9c1f5b5258c2210ae768f1b7439.exepid process 952 640ec1f3d053f145abbc471ce754a3d0b0f1a9c1f5b5258c2210ae768f1b7439.exe 952 640ec1f3d053f145abbc471ce754a3d0b0f1a9c1f5b5258c2210ae768f1b7439.exe 952 640ec1f3d053f145abbc471ce754a3d0b0f1a9c1f5b5258c2210ae768f1b7439.exe 952 640ec1f3d053f145abbc471ce754a3d0b0f1a9c1f5b5258c2210ae768f1b7439.exe 952 640ec1f3d053f145abbc471ce754a3d0b0f1a9c1f5b5258c2210ae768f1b7439.exe 952 640ec1f3d053f145abbc471ce754a3d0b0f1a9c1f5b5258c2210ae768f1b7439.exe -
Suspicious use of WriteProcessMemory 11 IoCs
Processes:
640ec1f3d053f145abbc471ce754a3d0b0f1a9c1f5b5258c2210ae768f1b7439.exedescription pid process target process PID 1248 wrote to memory of 952 1248 640ec1f3d053f145abbc471ce754a3d0b0f1a9c1f5b5258c2210ae768f1b7439.exe 640ec1f3d053f145abbc471ce754a3d0b0f1a9c1f5b5258c2210ae768f1b7439.exe PID 1248 wrote to memory of 952 1248 640ec1f3d053f145abbc471ce754a3d0b0f1a9c1f5b5258c2210ae768f1b7439.exe 640ec1f3d053f145abbc471ce754a3d0b0f1a9c1f5b5258c2210ae768f1b7439.exe PID 1248 wrote to memory of 952 1248 640ec1f3d053f145abbc471ce754a3d0b0f1a9c1f5b5258c2210ae768f1b7439.exe 640ec1f3d053f145abbc471ce754a3d0b0f1a9c1f5b5258c2210ae768f1b7439.exe PID 1248 wrote to memory of 952 1248 640ec1f3d053f145abbc471ce754a3d0b0f1a9c1f5b5258c2210ae768f1b7439.exe 640ec1f3d053f145abbc471ce754a3d0b0f1a9c1f5b5258c2210ae768f1b7439.exe PID 1248 wrote to memory of 952 1248 640ec1f3d053f145abbc471ce754a3d0b0f1a9c1f5b5258c2210ae768f1b7439.exe 640ec1f3d053f145abbc471ce754a3d0b0f1a9c1f5b5258c2210ae768f1b7439.exe PID 1248 wrote to memory of 952 1248 640ec1f3d053f145abbc471ce754a3d0b0f1a9c1f5b5258c2210ae768f1b7439.exe 640ec1f3d053f145abbc471ce754a3d0b0f1a9c1f5b5258c2210ae768f1b7439.exe PID 1248 wrote to memory of 952 1248 640ec1f3d053f145abbc471ce754a3d0b0f1a9c1f5b5258c2210ae768f1b7439.exe 640ec1f3d053f145abbc471ce754a3d0b0f1a9c1f5b5258c2210ae768f1b7439.exe PID 1248 wrote to memory of 952 1248 640ec1f3d053f145abbc471ce754a3d0b0f1a9c1f5b5258c2210ae768f1b7439.exe 640ec1f3d053f145abbc471ce754a3d0b0f1a9c1f5b5258c2210ae768f1b7439.exe PID 1248 wrote to memory of 952 1248 640ec1f3d053f145abbc471ce754a3d0b0f1a9c1f5b5258c2210ae768f1b7439.exe 640ec1f3d053f145abbc471ce754a3d0b0f1a9c1f5b5258c2210ae768f1b7439.exe PID 1248 wrote to memory of 952 1248 640ec1f3d053f145abbc471ce754a3d0b0f1a9c1f5b5258c2210ae768f1b7439.exe 640ec1f3d053f145abbc471ce754a3d0b0f1a9c1f5b5258c2210ae768f1b7439.exe PID 1248 wrote to memory of 952 1248 640ec1f3d053f145abbc471ce754a3d0b0f1a9c1f5b5258c2210ae768f1b7439.exe 640ec1f3d053f145abbc471ce754a3d0b0f1a9c1f5b5258c2210ae768f1b7439.exe
Processes
-
C:\Users\Admin\AppData\Local\Temp\640ec1f3d053f145abbc471ce754a3d0b0f1a9c1f5b5258c2210ae768f1b7439.exe"C:\Users\Admin\AppData\Local\Temp\640ec1f3d053f145abbc471ce754a3d0b0f1a9c1f5b5258c2210ae768f1b7439.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\640ec1f3d053f145abbc471ce754a3d0b0f1a9c1f5b5258c2210ae768f1b7439.exe"C:\Users\Admin\AppData\Local\Temp\640ec1f3d053f145abbc471ce754a3d0b0f1a9c1f5b5258c2210ae768f1b7439.exe" Track="0001001000"2⤵
- Checks BIOS information in registry
- Maps connected drives based on registry
- Modifies Internet Explorer settings
- Suspicious use of SetWindowsHookEx
Network
MITRE ATT&CK Matrix ATT&CK v6
Replay Monitor
Loading Replay Monitor...
Downloads
-
memory/952-69-0x00000000004BAFB0-mapping.dmp
-
memory/952-72-0x0000000075351000-0x0000000075353000-memory.dmpFilesize
8KB
-
memory/952-56-0x0000000000400000-0x00000000005BC000-memory.dmpFilesize
1.7MB
-
memory/952-57-0x0000000000400000-0x00000000005BC000-memory.dmpFilesize
1.7MB
-
memory/952-65-0x0000000000400000-0x00000000005BC000-memory.dmpFilesize
1.7MB
-
memory/952-61-0x0000000000400000-0x00000000005BC000-memory.dmpFilesize
1.7MB
-
memory/952-75-0x0000000000400000-0x00000000005BC000-memory.dmpFilesize
1.7MB
-
memory/952-63-0x0000000000400000-0x00000000005BC000-memory.dmpFilesize
1.7MB
-
memory/952-59-0x0000000000400000-0x00000000005BC000-memory.dmpFilesize
1.7MB
-
memory/952-68-0x0000000000400000-0x00000000005BC000-memory.dmpFilesize
1.7MB
-
memory/952-74-0x0000000000400000-0x00000000005BC000-memory.dmpFilesize
1.7MB
-
memory/952-73-0x0000000000400000-0x00000000005BC000-memory.dmpFilesize
1.7MB
-
memory/1248-54-0x0000000000230000-0x0000000000233000-memory.dmpFilesize
12KB
-
memory/1248-70-0x0000000000400000-0x00000000004F6000-memory.dmpFilesize
984KB
-
memory/1248-67-0x0000000002390000-0x0000000002486000-memory.dmpFilesize
984KB
-
memory/1248-55-0x0000000000400000-0x00000000004F6000-memory.dmpFilesize
984KB