Analysis
-
max time kernel
149s -
max time network
151s -
platform
windows10-2004_x64 -
resource
win10v2004-20240709-en -
resource tags
arch:x64arch:x86image:win10v2004-20240709-enlocale:en-usos:windows10-2004-x64system -
submitted
24-07-2024 01:02
Static task
static1
Behavioral task
behavioral1
Sample
043f6e5b65055436ee950f3ebd72ed16589a34742deea3ad82e946bba1b94728.exe
Resource
win7-20240708-en
General
-
Target
043f6e5b65055436ee950f3ebd72ed16589a34742deea3ad82e946bba1b94728.exe
-
Size
2.7MB
-
MD5
df3a32a59e276774a045fd80fa2b53db
-
SHA1
ce4bb00e51f685b3ec7eb8100047c82db1f8be72
-
SHA256
043f6e5b65055436ee950f3ebd72ed16589a34742deea3ad82e946bba1b94728
-
SHA512
7811cace2b99777f1980c7021fca67f9500d5a140aa73ff02fa19327db134710cc97e6d8b7ad1b58592dd23ed2a548fe5cf520227654c05ff2f0c23336b8fb0d
-
SSDEEP
24576:JoawHU1iLq121i1IqzUlfC1QZ6KEJeEZ+ZZY:JoaMU1iLqM1ij4SQ5ECZY
Malware Config
Extracted
remcos
ZIP
vegetachcnc.com:2556
-
audio_folder
MicRecords
-
audio_record_time
5
-
connect_delay
0
-
connect_interval
1
-
copy_file
remcos.exe
-
copy_folder
Remcos
-
delete_file
false
-
hide_file
false
-
hide_keylog_file
false
-
install_flag
false
-
keylog_crypt
false
-
keylog_file
logs.dat
-
keylog_flag
false
-
keylog_folder
remcos
-
mouse_option
false
-
mutex
chrome-76G0MC
-
screenshot_crypt
false
-
screenshot_flag
false
-
screenshot_folder
Screenshots
-
screenshot_path
%AppData%
-
screenshot_time
10
-
take_screenshot_option
false
-
take_screenshot_time
5
Signatures
-
Suspicious use of SetThreadContext 1 IoCs
description pid Process procid_target PID 1520 set thread context of 3740 1520 043f6e5b65055436ee950f3ebd72ed16589a34742deea3ad82e946bba1b94728.exe 89 -
Program crash 1 IoCs
pid pid_target Process procid_target 3776 3740 WerFault.exe 89 -
Suspicious use of AdjustPrivilegeToken 1 IoCs
description pid Process Token: SeDebugPrivilege 1520 043f6e5b65055436ee950f3ebd72ed16589a34742deea3ad82e946bba1b94728.exe -
Suspicious use of WriteProcessMemory 25 IoCs
description pid Process procid_target PID 1520 wrote to memory of 2580 1520 043f6e5b65055436ee950f3ebd72ed16589a34742deea3ad82e946bba1b94728.exe 85 PID 1520 wrote to memory of 2580 1520 043f6e5b65055436ee950f3ebd72ed16589a34742deea3ad82e946bba1b94728.exe 85 PID 1520 wrote to memory of 2580 1520 043f6e5b65055436ee950f3ebd72ed16589a34742deea3ad82e946bba1b94728.exe 85 PID 1520 wrote to memory of 2580 1520 043f6e5b65055436ee950f3ebd72ed16589a34742deea3ad82e946bba1b94728.exe 85 PID 1520 wrote to memory of 2580 1520 043f6e5b65055436ee950f3ebd72ed16589a34742deea3ad82e946bba1b94728.exe 85 PID 1520 wrote to memory of 2580 1520 043f6e5b65055436ee950f3ebd72ed16589a34742deea3ad82e946bba1b94728.exe 85 PID 1520 wrote to memory of 2580 1520 043f6e5b65055436ee950f3ebd72ed16589a34742deea3ad82e946bba1b94728.exe 85 PID 1520 wrote to memory of 2580 1520 043f6e5b65055436ee950f3ebd72ed16589a34742deea3ad82e946bba1b94728.exe 85 PID 1520 wrote to memory of 2580 1520 043f6e5b65055436ee950f3ebd72ed16589a34742deea3ad82e946bba1b94728.exe 85 PID 1520 wrote to memory of 2580 1520 043f6e5b65055436ee950f3ebd72ed16589a34742deea3ad82e946bba1b94728.exe 85 PID 1520 wrote to memory of 3740 1520 043f6e5b65055436ee950f3ebd72ed16589a34742deea3ad82e946bba1b94728.exe 89 PID 1520 wrote to memory of 3740 1520 043f6e5b65055436ee950f3ebd72ed16589a34742deea3ad82e946bba1b94728.exe 89 PID 1520 wrote to memory of 3740 1520 043f6e5b65055436ee950f3ebd72ed16589a34742deea3ad82e946bba1b94728.exe 89 PID 1520 wrote to memory of 3740 1520 043f6e5b65055436ee950f3ebd72ed16589a34742deea3ad82e946bba1b94728.exe 89 PID 1520 wrote to memory of 3740 1520 043f6e5b65055436ee950f3ebd72ed16589a34742deea3ad82e946bba1b94728.exe 89 PID 1520 wrote to memory of 3740 1520 043f6e5b65055436ee950f3ebd72ed16589a34742deea3ad82e946bba1b94728.exe 89 PID 1520 wrote to memory of 3740 1520 043f6e5b65055436ee950f3ebd72ed16589a34742deea3ad82e946bba1b94728.exe 89 PID 1520 wrote to memory of 3740 1520 043f6e5b65055436ee950f3ebd72ed16589a34742deea3ad82e946bba1b94728.exe 89 PID 1520 wrote to memory of 3740 1520 043f6e5b65055436ee950f3ebd72ed16589a34742deea3ad82e946bba1b94728.exe 89 PID 1520 wrote to memory of 3740 1520 043f6e5b65055436ee950f3ebd72ed16589a34742deea3ad82e946bba1b94728.exe 89 PID 1520 wrote to memory of 3740 1520 043f6e5b65055436ee950f3ebd72ed16589a34742deea3ad82e946bba1b94728.exe 89 PID 1520 wrote to memory of 3740 1520 043f6e5b65055436ee950f3ebd72ed16589a34742deea3ad82e946bba1b94728.exe 89 PID 1520 wrote to memory of 4876 1520 043f6e5b65055436ee950f3ebd72ed16589a34742deea3ad82e946bba1b94728.exe 90 PID 1520 wrote to memory of 4876 1520 043f6e5b65055436ee950f3ebd72ed16589a34742deea3ad82e946bba1b94728.exe 90 PID 1520 wrote to memory of 4876 1520 043f6e5b65055436ee950f3ebd72ed16589a34742deea3ad82e946bba1b94728.exe 90
Processes
-
C:\Users\Admin\AppData\Local\Temp\043f6e5b65055436ee950f3ebd72ed16589a34742deea3ad82e946bba1b94728.exe"C:\Users\Admin\AppData\Local\Temp\043f6e5b65055436ee950f3ebd72ed16589a34742deea3ad82e946bba1b94728.exe"1⤵
- Suspicious use of SetThreadContext
- Suspicious use of AdjustPrivilegeToken
- Suspicious use of WriteProcessMemory
PID:1520 -
C:\Windows\System32\svchost.exe"C:\Windows\System32\svchost.exe"2⤵PID:2580
-
-
C:\Windows\Microsoft.NET\Framework\v4.0.30319\ilasm.exe"C:\Windows\Microsoft.NET\Framework\v4.0.30319\ilasm.exe"2⤵PID:3740
-
C:\Windows\SysWOW64\WerFault.exeC:\Windows\SysWOW64\WerFault.exe -u -p 3740 -s 203⤵
- Program crash
PID:3776
-
-
-
C:\Windows\Microsoft.NET\Framework\v4.0.30319\ilasm.exe"C:\Windows\Microsoft.NET\Framework\v4.0.30319\ilasm.exe"2⤵PID:4876
-
-
C:\Windows\SysWOW64\WerFault.exeC:\Windows\SysWOW64\WerFault.exe -pss -s 416 -p 3740 -ip 37401⤵PID:1408