Analysis
-
max time kernel
128s -
max time network
138s -
platform
windows10_x64 -
resource
win10v20201028 -
submitted
12-11-2020 14:15
Static task
static1
Behavioral task
behavioral1
Sample
e5223d2f96963acd0f798655baadb74bb1260b1342e2839bceadc0daba6c5f78.exe
Resource
win7v20201028
Behavioral task
behavioral2
Sample
e5223d2f96963acd0f798655baadb74bb1260b1342e2839bceadc0daba6c5f78.exe
Resource
win10v20201028
General
-
Target
e5223d2f96963acd0f798655baadb74bb1260b1342e2839bceadc0daba6c5f78.exe
-
Size
1.1MB
-
MD5
3f6c9f05bf208a082ffbc1786347abd7
-
SHA1
472dcc8685cd8ec76f47ba91f87f2bbb8852721e
-
SHA256
e5223d2f96963acd0f798655baadb74bb1260b1342e2839bceadc0daba6c5f78
-
SHA512
f81f639267e54d82821e5dbcd60f666a2b524f81135fac77f76922148109b14ae8b0623ba06ea7c4a978187f9e3fe0a9652ee61f42e44976d5db96bb7975480f
Malware Config
Extracted
revengerat
Guest
178.17.174.71:3310
RV_MUTEX-HxdYuaWVCGnhp
Signatures
-
RevengeRAT
Remote-access trojan with a wide range of capabilities.
-
RevengeRat Executable 2 IoCs
Processes:
resource yara_rule behavioral2/memory/4032-0-0x0000000000400000-0x0000000000408000-memory.dmp revengerat behavioral2/memory/4032-1-0x0000000000405E3E-mapping.dmp revengerat -
Drops startup file 1 IoCs
Processes:
e5223d2f96963acd0f798655baadb74bb1260b1342e2839bceadc0daba6c5f78.exedescription ioc process File created C:\Users\Admin\AppData\Roaming\Microsoft\Windows\Start Menu\Programs\Startup\msdtc.url e5223d2f96963acd0f798655baadb74bb1260b1342e2839bceadc0daba6c5f78.exe -
Suspicious use of SetThreadContext 1 IoCs
Processes:
e5223d2f96963acd0f798655baadb74bb1260b1342e2839bceadc0daba6c5f78.exedescription pid process target process PID 944 set thread context of 4032 944 e5223d2f96963acd0f798655baadb74bb1260b1342e2839bceadc0daba6c5f78.exe RegAsm.exe -
Drops file in Windows directory 1 IoCs
Processes:
RegAsm.exedescription ioc process File opened for modification C:\Windows\Microsoft.NET\Framework\v2.0.50727\RegAsm.exe RegAsm.exe -
Suspicious use of AdjustPrivilegeToken 1 IoCs
Processes:
RegAsm.exedescription pid process Token: SeDebugPrivilege 4032 RegAsm.exe -
Suspicious use of FindShellTrayWindow 3 IoCs
Processes:
e5223d2f96963acd0f798655baadb74bb1260b1342e2839bceadc0daba6c5f78.exepid process 944 e5223d2f96963acd0f798655baadb74bb1260b1342e2839bceadc0daba6c5f78.exe 944 e5223d2f96963acd0f798655baadb74bb1260b1342e2839bceadc0daba6c5f78.exe 944 e5223d2f96963acd0f798655baadb74bb1260b1342e2839bceadc0daba6c5f78.exe -
Suspicious use of SendNotifyMessage 3 IoCs
Processes:
e5223d2f96963acd0f798655baadb74bb1260b1342e2839bceadc0daba6c5f78.exepid process 944 e5223d2f96963acd0f798655baadb74bb1260b1342e2839bceadc0daba6c5f78.exe 944 e5223d2f96963acd0f798655baadb74bb1260b1342e2839bceadc0daba6c5f78.exe 944 e5223d2f96963acd0f798655baadb74bb1260b1342e2839bceadc0daba6c5f78.exe -
Suspicious use of WriteProcessMemory 5 IoCs
Processes:
e5223d2f96963acd0f798655baadb74bb1260b1342e2839bceadc0daba6c5f78.exedescription pid process target process PID 944 wrote to memory of 4032 944 e5223d2f96963acd0f798655baadb74bb1260b1342e2839bceadc0daba6c5f78.exe RegAsm.exe PID 944 wrote to memory of 4032 944 e5223d2f96963acd0f798655baadb74bb1260b1342e2839bceadc0daba6c5f78.exe RegAsm.exe PID 944 wrote to memory of 4032 944 e5223d2f96963acd0f798655baadb74bb1260b1342e2839bceadc0daba6c5f78.exe RegAsm.exe PID 944 wrote to memory of 4032 944 e5223d2f96963acd0f798655baadb74bb1260b1342e2839bceadc0daba6c5f78.exe RegAsm.exe PID 944 wrote to memory of 4032 944 e5223d2f96963acd0f798655baadb74bb1260b1342e2839bceadc0daba6c5f78.exe RegAsm.exe
Processes
-
C:\Users\Admin\AppData\Local\Temp\e5223d2f96963acd0f798655baadb74bb1260b1342e2839bceadc0daba6c5f78.exe"C:\Users\Admin\AppData\Local\Temp\e5223d2f96963acd0f798655baadb74bb1260b1342e2839bceadc0daba6c5f78.exe"1⤵
- Drops startup file
- Suspicious use of SetThreadContext
- Suspicious use of FindShellTrayWindow
- Suspicious use of SendNotifyMessage
- Suspicious use of WriteProcessMemory
-
C:\Windows\Microsoft.NET\Framework\v2.0.50727\RegAsm.exe"C:\Windows\Microsoft.NET\Framework\v2.0.50727\RegAsm.exe"2⤵
- Drops file in Windows directory
- Suspicious use of AdjustPrivilegeToken