Analysis
-
max time kernel
131s -
max time network
136s -
platform
windows7_x64 -
resource
win7-20221111-en -
resource tags
arch:x64arch:x86image:win7-20221111-enlocale:en-usos:windows7-x64system -
submitted
12-12-2022 22:05
Static task
static1
Behavioral task
behavioral1
Sample
399a0e77326dc484fa92fd5f95f2dbd89866dfd4e7e80661634a9a83f0652403.exe
Resource
win7-20221111-en
Behavioral task
behavioral2
Sample
399a0e77326dc484fa92fd5f95f2dbd89866dfd4e7e80661634a9a83f0652403.exe
Resource
win10v2004-20221111-en
General
-
Target
399a0e77326dc484fa92fd5f95f2dbd89866dfd4e7e80661634a9a83f0652403.exe
-
Size
14.7MB
-
MD5
2cbd5d9d43c5c49f0580975e9e620808
-
SHA1
17e209b6d6c66882ed78a40d7e0d211760b489a0
-
SHA256
399a0e77326dc484fa92fd5f95f2dbd89866dfd4e7e80661634a9a83f0652403
-
SHA512
26e06d3d3b4f8d1198f483e2485ee107782c7f5b70ddb4d48dd84c9ef81029af316ad3a184c90921c6f1188f92d88b9fd6a152eaba5648a03bfbdea589202812
-
SSDEEP
196608:X0hLU8m9T9crlNBd8Sbrlzg0IzM7djVK2:khA595q38SbBs0IzM3
Malware Config
Extracted
asyncrat
0.5.7B
System Guard Runtime
85.105.88.221:2531
System Guard Runtime
-
delay
3
-
install
false
-
install_file
System Guard Runtime
-
install_folder
%AppData%
Signatures
-
Async RAT payload 7 IoCs
Processes:
resource yara_rule behavioral1/memory/268-62-0x0000000000400000-0x0000000000412000-memory.dmp asyncrat behavioral1/memory/268-63-0x0000000000400000-0x0000000000412000-memory.dmp asyncrat behavioral1/memory/268-64-0x000000000040D0EE-mapping.dmp asyncrat behavioral1/memory/268-61-0x0000000000400000-0x0000000000412000-memory.dmp asyncrat behavioral1/memory/268-66-0x0000000000400000-0x0000000000412000-memory.dmp asyncrat behavioral1/memory/268-68-0x0000000000400000-0x0000000000412000-memory.dmp asyncrat behavioral1/memory/1532-80-0x000000000040D0EE-mapping.dmp asyncrat -
Executes dropped EXE 1 IoCs
Processes:
399a0e77326dc484fa92fd5f95f2dbd89866dfd4e7e80661634a9a83f0652403.exepid process 1040 399a0e77326dc484fa92fd5f95f2dbd89866dfd4e7e80661634a9a83f0652403.exe -
Suspicious use of SetThreadContext 2 IoCs
Processes:
399a0e77326dc484fa92fd5f95f2dbd89866dfd4e7e80661634a9a83f0652403.exe399a0e77326dc484fa92fd5f95f2dbd89866dfd4e7e80661634a9a83f0652403.exedescription pid process target process PID 1752 set thread context of 268 1752 399a0e77326dc484fa92fd5f95f2dbd89866dfd4e7e80661634a9a83f0652403.exe RegAsm.exe PID 1040 set thread context of 1532 1040 399a0e77326dc484fa92fd5f95f2dbd89866dfd4e7e80661634a9a83f0652403.exe RegAsm.exe -
Suspicious use of AdjustPrivilegeToken 2 IoCs
Processes:
399a0e77326dc484fa92fd5f95f2dbd89866dfd4e7e80661634a9a83f0652403.exe399a0e77326dc484fa92fd5f95f2dbd89866dfd4e7e80661634a9a83f0652403.exedescription pid process Token: SeDebugPrivilege 1752 399a0e77326dc484fa92fd5f95f2dbd89866dfd4e7e80661634a9a83f0652403.exe Token: SeDebugPrivilege 1040 399a0e77326dc484fa92fd5f95f2dbd89866dfd4e7e80661634a9a83f0652403.exe -
Suspicious use of WriteProcessMemory 28 IoCs
Processes:
399a0e77326dc484fa92fd5f95f2dbd89866dfd4e7e80661634a9a83f0652403.exetaskeng.exe399a0e77326dc484fa92fd5f95f2dbd89866dfd4e7e80661634a9a83f0652403.exedescription pid process target process PID 1752 wrote to memory of 268 1752 399a0e77326dc484fa92fd5f95f2dbd89866dfd4e7e80661634a9a83f0652403.exe RegAsm.exe PID 1752 wrote to memory of 268 1752 399a0e77326dc484fa92fd5f95f2dbd89866dfd4e7e80661634a9a83f0652403.exe RegAsm.exe PID 1752 wrote to memory of 268 1752 399a0e77326dc484fa92fd5f95f2dbd89866dfd4e7e80661634a9a83f0652403.exe RegAsm.exe PID 1752 wrote to memory of 268 1752 399a0e77326dc484fa92fd5f95f2dbd89866dfd4e7e80661634a9a83f0652403.exe RegAsm.exe PID 1752 wrote to memory of 268 1752 399a0e77326dc484fa92fd5f95f2dbd89866dfd4e7e80661634a9a83f0652403.exe RegAsm.exe PID 1752 wrote to memory of 268 1752 399a0e77326dc484fa92fd5f95f2dbd89866dfd4e7e80661634a9a83f0652403.exe RegAsm.exe PID 1752 wrote to memory of 268 1752 399a0e77326dc484fa92fd5f95f2dbd89866dfd4e7e80661634a9a83f0652403.exe RegAsm.exe PID 1752 wrote to memory of 268 1752 399a0e77326dc484fa92fd5f95f2dbd89866dfd4e7e80661634a9a83f0652403.exe RegAsm.exe PID 1752 wrote to memory of 268 1752 399a0e77326dc484fa92fd5f95f2dbd89866dfd4e7e80661634a9a83f0652403.exe RegAsm.exe PID 1752 wrote to memory of 268 1752 399a0e77326dc484fa92fd5f95f2dbd89866dfd4e7e80661634a9a83f0652403.exe RegAsm.exe PID 1752 wrote to memory of 268 1752 399a0e77326dc484fa92fd5f95f2dbd89866dfd4e7e80661634a9a83f0652403.exe RegAsm.exe PID 1752 wrote to memory of 268 1752 399a0e77326dc484fa92fd5f95f2dbd89866dfd4e7e80661634a9a83f0652403.exe RegAsm.exe PID 1956 wrote to memory of 1040 1956 taskeng.exe 399a0e77326dc484fa92fd5f95f2dbd89866dfd4e7e80661634a9a83f0652403.exe PID 1956 wrote to memory of 1040 1956 taskeng.exe 399a0e77326dc484fa92fd5f95f2dbd89866dfd4e7e80661634a9a83f0652403.exe PID 1956 wrote to memory of 1040 1956 taskeng.exe 399a0e77326dc484fa92fd5f95f2dbd89866dfd4e7e80661634a9a83f0652403.exe PID 1956 wrote to memory of 1040 1956 taskeng.exe 399a0e77326dc484fa92fd5f95f2dbd89866dfd4e7e80661634a9a83f0652403.exe PID 1040 wrote to memory of 1532 1040 399a0e77326dc484fa92fd5f95f2dbd89866dfd4e7e80661634a9a83f0652403.exe RegAsm.exe PID 1040 wrote to memory of 1532 1040 399a0e77326dc484fa92fd5f95f2dbd89866dfd4e7e80661634a9a83f0652403.exe RegAsm.exe PID 1040 wrote to memory of 1532 1040 399a0e77326dc484fa92fd5f95f2dbd89866dfd4e7e80661634a9a83f0652403.exe RegAsm.exe PID 1040 wrote to memory of 1532 1040 399a0e77326dc484fa92fd5f95f2dbd89866dfd4e7e80661634a9a83f0652403.exe RegAsm.exe PID 1040 wrote to memory of 1532 1040 399a0e77326dc484fa92fd5f95f2dbd89866dfd4e7e80661634a9a83f0652403.exe RegAsm.exe PID 1040 wrote to memory of 1532 1040 399a0e77326dc484fa92fd5f95f2dbd89866dfd4e7e80661634a9a83f0652403.exe RegAsm.exe PID 1040 wrote to memory of 1532 1040 399a0e77326dc484fa92fd5f95f2dbd89866dfd4e7e80661634a9a83f0652403.exe RegAsm.exe PID 1040 wrote to memory of 1532 1040 399a0e77326dc484fa92fd5f95f2dbd89866dfd4e7e80661634a9a83f0652403.exe RegAsm.exe PID 1040 wrote to memory of 1532 1040 399a0e77326dc484fa92fd5f95f2dbd89866dfd4e7e80661634a9a83f0652403.exe RegAsm.exe PID 1040 wrote to memory of 1532 1040 399a0e77326dc484fa92fd5f95f2dbd89866dfd4e7e80661634a9a83f0652403.exe RegAsm.exe PID 1040 wrote to memory of 1532 1040 399a0e77326dc484fa92fd5f95f2dbd89866dfd4e7e80661634a9a83f0652403.exe RegAsm.exe PID 1040 wrote to memory of 1532 1040 399a0e77326dc484fa92fd5f95f2dbd89866dfd4e7e80661634a9a83f0652403.exe RegAsm.exe
Processes
-
C:\Users\Admin\AppData\Local\Temp\399a0e77326dc484fa92fd5f95f2dbd89866dfd4e7e80661634a9a83f0652403.exe"C:\Users\Admin\AppData\Local\Temp\399a0e77326dc484fa92fd5f95f2dbd89866dfd4e7e80661634a9a83f0652403.exe"1⤵
- Suspicious use of SetThreadContext
- Suspicious use of AdjustPrivilegeToken
- Suspicious use of WriteProcessMemory
-
C:\Windows\Microsoft.NET\Framework\v4.0.30319\RegAsm.exe"C:\Windows\Microsoft.NET\Framework\v4.0.30319\RegAsm.exe"2⤵
-
C:\Windows\system32\taskeng.exetaskeng.exe {AA402CD5-97AD-446C-A010-8032BB2784B3} S-1-5-21-3385717845-2518323428-350143044-1000:SABDUHNY\Admin:Interactive:[1]1⤵
- Suspicious use of WriteProcessMemory
-
C:\Users\Admin\AppData\Local\Temp\399a0e77326dc484fa92fd5f95f2dbd89866dfd4e7e80661634a9a83f0652403.exeC:\Users\Admin\AppData\Local\Temp\399a0e77326dc484fa92fd5f95f2dbd89866dfd4e7e80661634a9a83f0652403.exe2⤵
- Executes dropped EXE
- Suspicious use of SetThreadContext
- Suspicious use of AdjustPrivilegeToken
- Suspicious use of WriteProcessMemory
-
C:\Windows\Microsoft.NET\Framework\v4.0.30319\RegAsm.exe"C:\Windows\Microsoft.NET\Framework\v4.0.30319\RegAsm.exe"3⤵
Network
MITRE ATT&CK Matrix
Replay Monitor
Loading Replay Monitor...
Downloads
-
C:\Users\Admin\AppData\Local\Temp\399a0e77326dc484fa92fd5f95f2dbd89866dfd4e7e80661634a9a83f0652403.exeFilesize
14.7MB
MD52cbd5d9d43c5c49f0580975e9e620808
SHA117e209b6d6c66882ed78a40d7e0d211760b489a0
SHA256399a0e77326dc484fa92fd5f95f2dbd89866dfd4e7e80661634a9a83f0652403
SHA51226e06d3d3b4f8d1198f483e2485ee107782c7f5b70ddb4d48dd84c9ef81029af316ad3a184c90921c6f1188f92d88b9fd6a152eaba5648a03bfbdea589202812
-
memory/268-59-0x0000000000400000-0x0000000000412000-memory.dmpFilesize
72KB
-
memory/268-58-0x0000000000400000-0x0000000000412000-memory.dmpFilesize
72KB
-
memory/268-68-0x0000000000400000-0x0000000000412000-memory.dmpFilesize
72KB
-
memory/268-62-0x0000000000400000-0x0000000000412000-memory.dmpFilesize
72KB
-
memory/268-63-0x0000000000400000-0x0000000000412000-memory.dmpFilesize
72KB
-
memory/268-64-0x000000000040D0EE-mapping.dmp
-
memory/268-66-0x0000000000400000-0x0000000000412000-memory.dmpFilesize
72KB
-
memory/268-61-0x0000000000400000-0x0000000000412000-memory.dmpFilesize
72KB
-
memory/1040-70-0x0000000000000000-mapping.dmp
-
memory/1040-72-0x0000000000380000-0x0000000001230000-memory.dmpFilesize
14.7MB
-
memory/1532-80-0x000000000040D0EE-mapping.dmp
-
memory/1752-54-0x0000000000330000-0x00000000011E0000-memory.dmpFilesize
14.7MB
-
memory/1752-56-0x0000000075C41000-0x0000000075C43000-memory.dmpFilesize
8KB
-
memory/1752-57-0x0000000005820000-0x00000000058BC000-memory.dmpFilesize
624KB
-
memory/1752-55-0x0000000007D90000-0x0000000007F56000-memory.dmpFilesize
1.8MB