Analysis
-
max time kernel
48s -
max time network
52s -
platform
windows7_x64 -
resource
win7-20220901-en -
resource tags
arch:x64arch:x86image:win7-20220901-enlocale:en-usos:windows7-x64system -
submitted
26-11-2022 04:27
Static task
static1
Behavioral task
behavioral1
Sample
3bdb6d767e8ef7ce6d1a80f41fe6d2717a99d6cd2ebb4814e0eb8b1cc3f0272f.exe
Resource
win7-20220901-en
Behavioral task
behavioral2
Sample
3bdb6d767e8ef7ce6d1a80f41fe6d2717a99d6cd2ebb4814e0eb8b1cc3f0272f.exe
Resource
win10v2004-20220812-en
General
-
Target
3bdb6d767e8ef7ce6d1a80f41fe6d2717a99d6cd2ebb4814e0eb8b1cc3f0272f.exe
-
Size
828KB
-
MD5
352978436db8c8015e51c378bcc9e843
-
SHA1
04bc3d763528b03483d2ae751621dc55895a6185
-
SHA256
3bdb6d767e8ef7ce6d1a80f41fe6d2717a99d6cd2ebb4814e0eb8b1cc3f0272f
-
SHA512
ec90df4ad1957352e47a0d5566c44673ca614b209acc364c0acef01eacbf250d5615e2961bf7af1d203bce4d1f6369679d2cc62e538787adf1f3e400a179db2f
-
SSDEEP
24576:ADFhwFzsQNLAr5bj/b4FKHrJ841gAQguqMwPp:cFhwFzPBYb02y4SA5MM
Malware Config
Signatures
-
Checks BIOS information in registry 2 TTPs 3 IoCs
BIOS information is often read in order to detect sandboxing environments.
Processes:
3bdb6d767e8ef7ce6d1a80f41fe6d2717a99d6cd2ebb4814e0eb8b1cc3f0272f.exe3bdb6d767e8ef7ce6d1a80f41fe6d2717a99d6cd2ebb4814e0eb8b1cc3f0272f.exedescription ioc process Key value queried \REGISTRY\MACHINE\HARDWARE\DESCRIPTION\System\SystemBiosVersion 3bdb6d767e8ef7ce6d1a80f41fe6d2717a99d6cd2ebb4814e0eb8b1cc3f0272f.exe Key value queried \REGISTRY\MACHINE\HARDWARE\DESCRIPTION\System\SystemBiosVersion 3bdb6d767e8ef7ce6d1a80f41fe6d2717a99d6cd2ebb4814e0eb8b1cc3f0272f.exe Key value queried \REGISTRY\MACHINE\HARDWARE\DESCRIPTION\System\VideoBiosVersion 3bdb6d767e8ef7ce6d1a80f41fe6d2717a99d6cd2ebb4814e0eb8b1cc3f0272f.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:
3bdb6d767e8ef7ce6d1a80f41fe6d2717a99d6cd2ebb4814e0eb8b1cc3f0272f.exe3bdb6d767e8ef7ce6d1a80f41fe6d2717a99d6cd2ebb4814e0eb8b1cc3f0272f.exedescription ioc process Key opened \REGISTRY\MACHINE\SYSTEM\ControlSet001\Services\Disk\Enum 3bdb6d767e8ef7ce6d1a80f41fe6d2717a99d6cd2ebb4814e0eb8b1cc3f0272f.exe Key value queried \REGISTRY\MACHINE\SYSTEM\ControlSet001\services\Disk\Enum\0 3bdb6d767e8ef7ce6d1a80f41fe6d2717a99d6cd2ebb4814e0eb8b1cc3f0272f.exe Key opened \REGISTRY\MACHINE\SYSTEM\ControlSet001\Services\Disk\Enum 3bdb6d767e8ef7ce6d1a80f41fe6d2717a99d6cd2ebb4814e0eb8b1cc3f0272f.exe Key value queried \REGISTRY\MACHINE\SYSTEM\ControlSet001\services\Disk\Enum\0 3bdb6d767e8ef7ce6d1a80f41fe6d2717a99d6cd2ebb4814e0eb8b1cc3f0272f.exe -
Suspicious use of SetThreadContext 1 IoCs
Processes:
3bdb6d767e8ef7ce6d1a80f41fe6d2717a99d6cd2ebb4814e0eb8b1cc3f0272f.exedescription pid process target process PID 1376 set thread context of 472 1376 3bdb6d767e8ef7ce6d1a80f41fe6d2717a99d6cd2ebb4814e0eb8b1cc3f0272f.exe 3bdb6d767e8ef7ce6d1a80f41fe6d2717a99d6cd2ebb4814e0eb8b1cc3f0272f.exe -
Processes:
3bdb6d767e8ef7ce6d1a80f41fe6d2717a99d6cd2ebb4814e0eb8b1cc3f0272f.exedescription ioc process Key created \REGISTRY\USER\S-1-5-21-4063495947-34355257-727531523-1000\Software\Microsoft\Internet Explorer\Main 3bdb6d767e8ef7ce6d1a80f41fe6d2717a99d6cd2ebb4814e0eb8b1cc3f0272f.exe -
Suspicious use of SetWindowsHookEx 6 IoCs
Processes:
3bdb6d767e8ef7ce6d1a80f41fe6d2717a99d6cd2ebb4814e0eb8b1cc3f0272f.exepid process 472 3bdb6d767e8ef7ce6d1a80f41fe6d2717a99d6cd2ebb4814e0eb8b1cc3f0272f.exe 472 3bdb6d767e8ef7ce6d1a80f41fe6d2717a99d6cd2ebb4814e0eb8b1cc3f0272f.exe 472 3bdb6d767e8ef7ce6d1a80f41fe6d2717a99d6cd2ebb4814e0eb8b1cc3f0272f.exe 472 3bdb6d767e8ef7ce6d1a80f41fe6d2717a99d6cd2ebb4814e0eb8b1cc3f0272f.exe 472 3bdb6d767e8ef7ce6d1a80f41fe6d2717a99d6cd2ebb4814e0eb8b1cc3f0272f.exe 472 3bdb6d767e8ef7ce6d1a80f41fe6d2717a99d6cd2ebb4814e0eb8b1cc3f0272f.exe -
Suspicious use of WriteProcessMemory 11 IoCs
Processes:
3bdb6d767e8ef7ce6d1a80f41fe6d2717a99d6cd2ebb4814e0eb8b1cc3f0272f.exedescription pid process target process PID 1376 wrote to memory of 472 1376 3bdb6d767e8ef7ce6d1a80f41fe6d2717a99d6cd2ebb4814e0eb8b1cc3f0272f.exe 3bdb6d767e8ef7ce6d1a80f41fe6d2717a99d6cd2ebb4814e0eb8b1cc3f0272f.exe PID 1376 wrote to memory of 472 1376 3bdb6d767e8ef7ce6d1a80f41fe6d2717a99d6cd2ebb4814e0eb8b1cc3f0272f.exe 3bdb6d767e8ef7ce6d1a80f41fe6d2717a99d6cd2ebb4814e0eb8b1cc3f0272f.exe PID 1376 wrote to memory of 472 1376 3bdb6d767e8ef7ce6d1a80f41fe6d2717a99d6cd2ebb4814e0eb8b1cc3f0272f.exe 3bdb6d767e8ef7ce6d1a80f41fe6d2717a99d6cd2ebb4814e0eb8b1cc3f0272f.exe PID 1376 wrote to memory of 472 1376 3bdb6d767e8ef7ce6d1a80f41fe6d2717a99d6cd2ebb4814e0eb8b1cc3f0272f.exe 3bdb6d767e8ef7ce6d1a80f41fe6d2717a99d6cd2ebb4814e0eb8b1cc3f0272f.exe PID 1376 wrote to memory of 472 1376 3bdb6d767e8ef7ce6d1a80f41fe6d2717a99d6cd2ebb4814e0eb8b1cc3f0272f.exe 3bdb6d767e8ef7ce6d1a80f41fe6d2717a99d6cd2ebb4814e0eb8b1cc3f0272f.exe PID 1376 wrote to memory of 472 1376 3bdb6d767e8ef7ce6d1a80f41fe6d2717a99d6cd2ebb4814e0eb8b1cc3f0272f.exe 3bdb6d767e8ef7ce6d1a80f41fe6d2717a99d6cd2ebb4814e0eb8b1cc3f0272f.exe PID 1376 wrote to memory of 472 1376 3bdb6d767e8ef7ce6d1a80f41fe6d2717a99d6cd2ebb4814e0eb8b1cc3f0272f.exe 3bdb6d767e8ef7ce6d1a80f41fe6d2717a99d6cd2ebb4814e0eb8b1cc3f0272f.exe PID 1376 wrote to memory of 472 1376 3bdb6d767e8ef7ce6d1a80f41fe6d2717a99d6cd2ebb4814e0eb8b1cc3f0272f.exe 3bdb6d767e8ef7ce6d1a80f41fe6d2717a99d6cd2ebb4814e0eb8b1cc3f0272f.exe PID 1376 wrote to memory of 472 1376 3bdb6d767e8ef7ce6d1a80f41fe6d2717a99d6cd2ebb4814e0eb8b1cc3f0272f.exe 3bdb6d767e8ef7ce6d1a80f41fe6d2717a99d6cd2ebb4814e0eb8b1cc3f0272f.exe PID 1376 wrote to memory of 472 1376 3bdb6d767e8ef7ce6d1a80f41fe6d2717a99d6cd2ebb4814e0eb8b1cc3f0272f.exe 3bdb6d767e8ef7ce6d1a80f41fe6d2717a99d6cd2ebb4814e0eb8b1cc3f0272f.exe PID 1376 wrote to memory of 472 1376 3bdb6d767e8ef7ce6d1a80f41fe6d2717a99d6cd2ebb4814e0eb8b1cc3f0272f.exe 3bdb6d767e8ef7ce6d1a80f41fe6d2717a99d6cd2ebb4814e0eb8b1cc3f0272f.exe
Processes
-
C:\Users\Admin\AppData\Local\Temp\3bdb6d767e8ef7ce6d1a80f41fe6d2717a99d6cd2ebb4814e0eb8b1cc3f0272f.exe"C:\Users\Admin\AppData\Local\Temp\3bdb6d767e8ef7ce6d1a80f41fe6d2717a99d6cd2ebb4814e0eb8b1cc3f0272f.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\3bdb6d767e8ef7ce6d1a80f41fe6d2717a99d6cd2ebb4814e0eb8b1cc3f0272f.exe"C:\Users\Admin\AppData\Local\Temp\3bdb6d767e8ef7ce6d1a80f41fe6d2717a99d6cd2ebb4814e0eb8b1cc3f0272f.exe" Track="0001101000"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/472-63-0x0000000000400000-0x00000000005BC000-memory.dmpFilesize
1.7MB
-
memory/472-67-0x0000000000400000-0x00000000005BC000-memory.dmpFilesize
1.7MB
-
memory/472-56-0x0000000000400000-0x00000000005BC000-memory.dmpFilesize
1.7MB
-
memory/472-57-0x0000000000400000-0x00000000005BC000-memory.dmpFilesize
1.7MB
-
memory/472-59-0x0000000000400000-0x00000000005BC000-memory.dmpFilesize
1.7MB
-
memory/472-61-0x0000000000400000-0x00000000005BC000-memory.dmpFilesize
1.7MB
-
memory/472-74-0x0000000000400000-0x00000000005BC000-memory.dmpFilesize
1.7MB
-
memory/472-65-0x0000000000400000-0x00000000005BC000-memory.dmpFilesize
1.7MB
-
memory/472-73-0x0000000000400000-0x00000000005BC000-memory.dmpFilesize
1.7MB
-
memory/472-68-0x00000000004BAFB0-mapping.dmp
-
memory/472-72-0x0000000000400000-0x00000000005BC000-memory.dmpFilesize
1.7MB
-
memory/472-71-0x0000000075091000-0x0000000075093000-memory.dmpFilesize
8KB
-
memory/1376-70-0x0000000000400000-0x00000000004F6000-memory.dmpFilesize
984KB
-
memory/1376-54-0x0000000000230000-0x0000000000233000-memory.dmpFilesize
12KB
-
memory/1376-55-0x0000000000400000-0x00000000004F6000-memory.dmpFilesize
984KB