General
- Target SecuriteInfo.com.Win32.MalwareX-gen.28212.1387.exe
- Size 1.2MB
- Sample230111-2et9ssae2y
- SHA256 6b8c08bdfd37a2535412abaab2caff3235b903a2f57d618a35806b98cba075cf
- MD5 b18b9ba39054c5f15c251cae648c0caf
- SHA1 244bf62a39485e06b8b7328bd08b4f5d9c29b311
- SHA512 99459e24b0a532faf43cf8202d3aeae8e557bb257511f2f1a728ab190f0a671be7680d4a1127750e7ba7a1a35c22e6763d2706b9aea3c5a87978294122640506
- SSDEEP 24576:aPiGxOQo+USleWhUPZ3UH3vkXYDxs3JrYTSKIKTn6AL5x:fGskHhUyH3s
- MD5 SHA1 SHA512 SSDEEP
Score
10/10
Static task
static1
Behavioral task
behavioral1
Sample
SecuriteInfo.com.Win32.MalwareX-gen.28212.1387.exe
Resource
win7-20221111-en
8 signatures
150 seconds
Behavioral task
behavioral2
Sample
SecuriteInfo.com.Win32.MalwareX-gen.28212.1387.exe
Resource
win10v2004-20220812-en
9 signatures
150 seconds
Malware Config
Extracted
Family
-
remcos
Botnet
-
RemoteHost
C2
-
10.9.0.26:10929
-
45.139.105.174:10929
-
127.0.0.1:10929
Attributes
-
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
Rmc-I0OT6D
-
screenshot_crypt
false
-
screenshot_flag
false
-
screenshot_folder
Screenshots
-
screenshot_path
%AppData%
-
screenshot_time
10
-
startup_value
Remcos
-
take_screenshot_option
false
-
take_screenshot_time
5
Targets
-
- Target SecuriteInfo.com.Win32.MalwareX-gen.28212.1387.exe
- Size 1.2MB
- SHA256 6b8c08bdfd37a2535412abaab2caff3235b903a2f57d618a35806b98cba075cf
- MD5 b18b9ba39054c5f15c251cae648c0caf
- SHA1 244bf62a39485e06b8b7328bd08b4f5d9c29b311
- SHA512 99459e24b0a532faf43cf8202d3aeae8e557bb257511f2f1a728ab190f0a671be7680d4a1127750e7ba7a1a35c22e6763d2706b9aea3c5a87978294122640506
- SSDEEP 24576:aPiGxOQo+USleWhUPZ3UH3vkXYDxs3JrYTSKIKTn6AL5x:fGskHhUyH3s
- MD5 SHA1 SHA512 SSDEEP
Score10/10-
Checks computer location settings
Looks up country code configured in the registry, likely geofence.
-
Suspicious use of SetThreadContext