Analysis
-
max time kernel
94s -
max time network
143s -
platform
windows7_x64 -
resource
win7-20221111-en -
resource tags
arch:x64arch:x86image:win7-20221111-enlocale:en-usos:windows7-x64system -
submitted
23-11-2022 18:48
Static task
static1
Behavioral task
behavioral1
Sample
2d3925f7b82404b53719f5d5fbbd686ebf1a973a5cfd3663eb71df8816dcf546.exe
Resource
win7-20221111-en
Behavioral task
behavioral2
Sample
2d3925f7b82404b53719f5d5fbbd686ebf1a973a5cfd3663eb71df8816dcf546.exe
Resource
win10v2004-20220812-en
General
-
Target
2d3925f7b82404b53719f5d5fbbd686ebf1a973a5cfd3663eb71df8816dcf546.exe
-
Size
36KB
-
MD5
44822cc990142caeeb2e9b3464cb5a50
-
SHA1
202c943cd7a95e71612bfd89762273af7d5da694
-
SHA256
2d3925f7b82404b53719f5d5fbbd686ebf1a973a5cfd3663eb71df8816dcf546
-
SHA512
32056572b6605f52063815dbe2d6e7d462cf25734fdcff3a9ff624182c1f13ffb71fc166d4c720565c55d107c153511bbb4513bce8b275e3776272de426e1cae
-
SSDEEP
768:ljNT+6F3G8YasqAaqBKEyoMs6Sug3HdplvnpFxf+SsI:ljNS6ZGKsuqBKE3iSH3HZ
Malware Config
Signatures
-
Maps connected drives based on registry 3 TTPs 2 IoCs
Disk information is often read in order to detect sandboxing environments.
Processes:
2d3925f7b82404b53719f5d5fbbd686ebf1a973a5cfd3663eb71df8816dcf546.exedescription ioc process Key opened \REGISTRY\MACHINE\SYSTEM\ControlSet001\Services\Disk\Enum 2d3925f7b82404b53719f5d5fbbd686ebf1a973a5cfd3663eb71df8816dcf546.exe Key value queried \REGISTRY\MACHINE\SYSTEM\ControlSet001\services\Disk\Enum\0 2d3925f7b82404b53719f5d5fbbd686ebf1a973a5cfd3663eb71df8816dcf546.exe -
Suspicious use of SetThreadContext 1 IoCs
Processes:
2d3925f7b82404b53719f5d5fbbd686ebf1a973a5cfd3663eb71df8816dcf546.exedescription pid process target process PID 1952 set thread context of 1912 1952 2d3925f7b82404b53719f5d5fbbd686ebf1a973a5cfd3663eb71df8816dcf546.exe 2d3925f7b82404b53719f5d5fbbd686ebf1a973a5cfd3663eb71df8816dcf546.exe -
Suspicious use of SetWindowsHookEx 3 IoCs
Processes:
2d3925f7b82404b53719f5d5fbbd686ebf1a973a5cfd3663eb71df8816dcf546.exe2d3925f7b82404b53719f5d5fbbd686ebf1a973a5cfd3663eb71df8816dcf546.exepid process 1952 2d3925f7b82404b53719f5d5fbbd686ebf1a973a5cfd3663eb71df8816dcf546.exe 1912 2d3925f7b82404b53719f5d5fbbd686ebf1a973a5cfd3663eb71df8816dcf546.exe 1912 2d3925f7b82404b53719f5d5fbbd686ebf1a973a5cfd3663eb71df8816dcf546.exe -
Suspicious use of WriteProcessMemory 10 IoCs
Processes:
2d3925f7b82404b53719f5d5fbbd686ebf1a973a5cfd3663eb71df8816dcf546.exedescription pid process target process PID 1952 wrote to memory of 1912 1952 2d3925f7b82404b53719f5d5fbbd686ebf1a973a5cfd3663eb71df8816dcf546.exe 2d3925f7b82404b53719f5d5fbbd686ebf1a973a5cfd3663eb71df8816dcf546.exe PID 1952 wrote to memory of 1912 1952 2d3925f7b82404b53719f5d5fbbd686ebf1a973a5cfd3663eb71df8816dcf546.exe 2d3925f7b82404b53719f5d5fbbd686ebf1a973a5cfd3663eb71df8816dcf546.exe PID 1952 wrote to memory of 1912 1952 2d3925f7b82404b53719f5d5fbbd686ebf1a973a5cfd3663eb71df8816dcf546.exe 2d3925f7b82404b53719f5d5fbbd686ebf1a973a5cfd3663eb71df8816dcf546.exe PID 1952 wrote to memory of 1912 1952 2d3925f7b82404b53719f5d5fbbd686ebf1a973a5cfd3663eb71df8816dcf546.exe 2d3925f7b82404b53719f5d5fbbd686ebf1a973a5cfd3663eb71df8816dcf546.exe PID 1952 wrote to memory of 1912 1952 2d3925f7b82404b53719f5d5fbbd686ebf1a973a5cfd3663eb71df8816dcf546.exe 2d3925f7b82404b53719f5d5fbbd686ebf1a973a5cfd3663eb71df8816dcf546.exe PID 1952 wrote to memory of 1912 1952 2d3925f7b82404b53719f5d5fbbd686ebf1a973a5cfd3663eb71df8816dcf546.exe 2d3925f7b82404b53719f5d5fbbd686ebf1a973a5cfd3663eb71df8816dcf546.exe PID 1952 wrote to memory of 1912 1952 2d3925f7b82404b53719f5d5fbbd686ebf1a973a5cfd3663eb71df8816dcf546.exe 2d3925f7b82404b53719f5d5fbbd686ebf1a973a5cfd3663eb71df8816dcf546.exe PID 1952 wrote to memory of 1912 1952 2d3925f7b82404b53719f5d5fbbd686ebf1a973a5cfd3663eb71df8816dcf546.exe 2d3925f7b82404b53719f5d5fbbd686ebf1a973a5cfd3663eb71df8816dcf546.exe PID 1952 wrote to memory of 1912 1952 2d3925f7b82404b53719f5d5fbbd686ebf1a973a5cfd3663eb71df8816dcf546.exe 2d3925f7b82404b53719f5d5fbbd686ebf1a973a5cfd3663eb71df8816dcf546.exe PID 1952 wrote to memory of 1912 1952 2d3925f7b82404b53719f5d5fbbd686ebf1a973a5cfd3663eb71df8816dcf546.exe 2d3925f7b82404b53719f5d5fbbd686ebf1a973a5cfd3663eb71df8816dcf546.exe
Processes
-
C:\Users\Admin\AppData\Local\Temp\2d3925f7b82404b53719f5d5fbbd686ebf1a973a5cfd3663eb71df8816dcf546.exe"C:\Users\Admin\AppData\Local\Temp\2d3925f7b82404b53719f5d5fbbd686ebf1a973a5cfd3663eb71df8816dcf546.exe"1⤵
- Suspicious use of SetThreadContext
- Suspicious use of SetWindowsHookEx
- Suspicious use of WriteProcessMemory
PID:1952 -
C:\Users\Admin\AppData\Local\Temp\2d3925f7b82404b53719f5d5fbbd686ebf1a973a5cfd3663eb71df8816dcf546.exea|2⤵
- Maps connected drives based on registry
- Suspicious use of SetWindowsHookEx
PID:1912