Analysis
-
max time kernel
237s -
max time network
249s -
platform
windows10-2004_x64 -
resource
win10v2004-20221111-en -
resource tags
arch:x64arch:x86image:win10v2004-20221111-enlocale:en-usos:windows10-2004-x64system -
submitted
24-11-2022 04:31
Static task
static1
Behavioral task
behavioral1
Sample
abdf3bd81bd36252fc0dbc2d834a1e37de96adb97d13dbe72a896c5d9ea74d8c.exe
Resource
win7-20220901-en
Behavioral task
behavioral2
Sample
abdf3bd81bd36252fc0dbc2d834a1e37de96adb97d13dbe72a896c5d9ea74d8c.exe
Resource
win10v2004-20221111-en
General
-
Target
abdf3bd81bd36252fc0dbc2d834a1e37de96adb97d13dbe72a896c5d9ea74d8c.exe
-
Size
1.1MB
-
MD5
8f2e4341286e4ee2d8e5b95e8c2ac09f
-
SHA1
2660f3a5c4dbe4a70def6b4aea31a2f9729fad4c
-
SHA256
abdf3bd81bd36252fc0dbc2d834a1e37de96adb97d13dbe72a896c5d9ea74d8c
-
SHA512
c0e8d4b1379e109f5a32732f9d0f8480879e66cb5981612121972c6f743884b718687c1037c3a26f0425cc0bbdbe8fc48f2daa9376e8a418ba3a3fd9aa3f462e
-
SSDEEP
24576:6MjtdFF1r7tQLf/9fOeEfJkgvvEEWhtkk9vrinJ:ljtHf1oJA1iWyvrC
Malware Config
Signatures
-
Checks BIOS information in registry 2 TTPs 2 IoCs
BIOS information is often read in order to detect sandboxing environments.
Processes:
abdf3bd81bd36252fc0dbc2d834a1e37de96adb97d13dbe72a896c5d9ea74d8c.exedescription ioc process Key value queried \REGISTRY\MACHINE\HARDWARE\DESCRIPTION\System\SystemBiosVersion abdf3bd81bd36252fc0dbc2d834a1e37de96adb97d13dbe72a896c5d9ea74d8c.exe Key value queried \REGISTRY\MACHINE\HARDWARE\DESCRIPTION\System\VideoBiosVersion abdf3bd81bd36252fc0dbc2d834a1e37de96adb97d13dbe72a896c5d9ea74d8c.exe -
Maps connected drives based on registry 3 TTPs 2 IoCs
Disk information is often read in order to detect sandboxing environments.
Processes:
abdf3bd81bd36252fc0dbc2d834a1e37de96adb97d13dbe72a896c5d9ea74d8c.exedescription ioc process Key opened \REGISTRY\MACHINE\SYSTEM\ControlSet001\Services\Disk\Enum abdf3bd81bd36252fc0dbc2d834a1e37de96adb97d13dbe72a896c5d9ea74d8c.exe Key value queried \REGISTRY\MACHINE\SYSTEM\ControlSet001\Services\disk\Enum\0 abdf3bd81bd36252fc0dbc2d834a1e37de96adb97d13dbe72a896c5d9ea74d8c.exe -
Suspicious use of SetThreadContext 1 IoCs
Processes:
abdf3bd81bd36252fc0dbc2d834a1e37de96adb97d13dbe72a896c5d9ea74d8c.exedescription pid process target process PID 3472 set thread context of 1688 3472 abdf3bd81bd36252fc0dbc2d834a1e37de96adb97d13dbe72a896c5d9ea74d8c.exe abdf3bd81bd36252fc0dbc2d834a1e37de96adb97d13dbe72a896c5d9ea74d8c.exe -
Suspicious use of SetWindowsHookEx 5 IoCs
Processes:
abdf3bd81bd36252fc0dbc2d834a1e37de96adb97d13dbe72a896c5d9ea74d8c.exepid process 1688 abdf3bd81bd36252fc0dbc2d834a1e37de96adb97d13dbe72a896c5d9ea74d8c.exe 1688 abdf3bd81bd36252fc0dbc2d834a1e37de96adb97d13dbe72a896c5d9ea74d8c.exe 1688 abdf3bd81bd36252fc0dbc2d834a1e37de96adb97d13dbe72a896c5d9ea74d8c.exe 1688 abdf3bd81bd36252fc0dbc2d834a1e37de96adb97d13dbe72a896c5d9ea74d8c.exe 1688 abdf3bd81bd36252fc0dbc2d834a1e37de96adb97d13dbe72a896c5d9ea74d8c.exe -
Suspicious use of WriteProcessMemory 10 IoCs
Processes:
abdf3bd81bd36252fc0dbc2d834a1e37de96adb97d13dbe72a896c5d9ea74d8c.exedescription pid process target process PID 3472 wrote to memory of 1688 3472 abdf3bd81bd36252fc0dbc2d834a1e37de96adb97d13dbe72a896c5d9ea74d8c.exe abdf3bd81bd36252fc0dbc2d834a1e37de96adb97d13dbe72a896c5d9ea74d8c.exe PID 3472 wrote to memory of 1688 3472 abdf3bd81bd36252fc0dbc2d834a1e37de96adb97d13dbe72a896c5d9ea74d8c.exe abdf3bd81bd36252fc0dbc2d834a1e37de96adb97d13dbe72a896c5d9ea74d8c.exe PID 3472 wrote to memory of 1688 3472 abdf3bd81bd36252fc0dbc2d834a1e37de96adb97d13dbe72a896c5d9ea74d8c.exe abdf3bd81bd36252fc0dbc2d834a1e37de96adb97d13dbe72a896c5d9ea74d8c.exe PID 3472 wrote to memory of 1688 3472 abdf3bd81bd36252fc0dbc2d834a1e37de96adb97d13dbe72a896c5d9ea74d8c.exe abdf3bd81bd36252fc0dbc2d834a1e37de96adb97d13dbe72a896c5d9ea74d8c.exe PID 3472 wrote to memory of 1688 3472 abdf3bd81bd36252fc0dbc2d834a1e37de96adb97d13dbe72a896c5d9ea74d8c.exe abdf3bd81bd36252fc0dbc2d834a1e37de96adb97d13dbe72a896c5d9ea74d8c.exe PID 3472 wrote to memory of 1688 3472 abdf3bd81bd36252fc0dbc2d834a1e37de96adb97d13dbe72a896c5d9ea74d8c.exe abdf3bd81bd36252fc0dbc2d834a1e37de96adb97d13dbe72a896c5d9ea74d8c.exe PID 3472 wrote to memory of 1688 3472 abdf3bd81bd36252fc0dbc2d834a1e37de96adb97d13dbe72a896c5d9ea74d8c.exe abdf3bd81bd36252fc0dbc2d834a1e37de96adb97d13dbe72a896c5d9ea74d8c.exe PID 3472 wrote to memory of 1688 3472 abdf3bd81bd36252fc0dbc2d834a1e37de96adb97d13dbe72a896c5d9ea74d8c.exe abdf3bd81bd36252fc0dbc2d834a1e37de96adb97d13dbe72a896c5d9ea74d8c.exe PID 3472 wrote to memory of 1688 3472 abdf3bd81bd36252fc0dbc2d834a1e37de96adb97d13dbe72a896c5d9ea74d8c.exe abdf3bd81bd36252fc0dbc2d834a1e37de96adb97d13dbe72a896c5d9ea74d8c.exe PID 3472 wrote to memory of 1688 3472 abdf3bd81bd36252fc0dbc2d834a1e37de96adb97d13dbe72a896c5d9ea74d8c.exe abdf3bd81bd36252fc0dbc2d834a1e37de96adb97d13dbe72a896c5d9ea74d8c.exe
Processes
-
C:\Users\Admin\AppData\Local\Temp\abdf3bd81bd36252fc0dbc2d834a1e37de96adb97d13dbe72a896c5d9ea74d8c.exe"C:\Users\Admin\AppData\Local\Temp\abdf3bd81bd36252fc0dbc2d834a1e37de96adb97d13dbe72a896c5d9ea74d8c.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\abdf3bd81bd36252fc0dbc2d834a1e37de96adb97d13dbe72a896c5d9ea74d8c.exe"C:\Users\Admin\AppData\Local\Temp\abdf3bd81bd36252fc0dbc2d834a1e37de96adb97d13dbe72a896c5d9ea74d8c.exe" Track="0001001000"2⤵
- Suspicious use of SetWindowsHookEx
Network
MITRE ATT&CK Matrix ATT&CK v6
Replay Monitor
Loading Replay Monitor...
Downloads
-
memory/1688-132-0x0000000000000000-mapping.dmp
-
memory/1688-133-0x0000000000400000-0x0000000000520000-memory.dmpFilesize
1.1MB
-
memory/1688-134-0x0000000000400000-0x0000000000520000-memory.dmpFilesize
1.1MB
-
memory/1688-135-0x0000000000400000-0x0000000000520000-memory.dmpFilesize
1.1MB
-
memory/1688-136-0x0000000000400000-0x0000000000520000-memory.dmpFilesize
1.1MB
-
memory/1688-137-0x0000000000400000-0x0000000000520000-memory.dmpFilesize
1.1MB