Analysis
-
max time kernel
150s -
max time network
46s -
platform
windows7_x64 -
resource
win7-20220718-en -
resource tags
arch:x64arch:x86image:win7-20220718-enlocale:en-usos:windows7-x64system -
submitted
24-07-2022 15:28
Static task
static1
Behavioral task
behavioral1
Sample
3b85020323e7b11ba66d785eaf5fa7e3cf3e21791f6b97e6abef4f579266fa3d.exe
Resource
win7-20220718-en
Behavioral task
behavioral2
Sample
3b85020323e7b11ba66d785eaf5fa7e3cf3e21791f6b97e6abef4f579266fa3d.exe
Resource
win10v2004-20220721-en
General
-
Target
3b85020323e7b11ba66d785eaf5fa7e3cf3e21791f6b97e6abef4f579266fa3d.exe
-
Size
943KB
-
MD5
c3d7fac817472717e5ea1f86ac1ff617
-
SHA1
5a79365fdae5a436e6aea22ff1155734a8ae92f7
-
SHA256
3b85020323e7b11ba66d785eaf5fa7e3cf3e21791f6b97e6abef4f579266fa3d
-
SHA512
8d0a0a393b5916c21fcaf84b3751d459682877c3150034a732e91583a327f6039b2dd121e38672016a3dff99629976bc70ea7b2d3f5ecbf566e6e9901a97e656
Malware Config
Extracted
revengerat
Guest
ournewcompany2.hopto.org:333
RV_MUTEX
Signatures
-
RevengeRAT
Remote-access trojan with a wide range of capabilities.
-
RevengeRat Executable 10 IoCs
Processes:
resource yara_rule behavioral1/memory/1760-61-0x0000000000400000-0x0000000000408000-memory.dmp revengerat behavioral1/memory/1760-63-0x0000000000405DCE-mapping.dmp revengerat behavioral1/memory/1760-62-0x0000000000400000-0x0000000000408000-memory.dmp revengerat behavioral1/memory/1760-66-0x0000000000400000-0x0000000000408000-memory.dmp revengerat behavioral1/memory/1760-70-0x0000000000400000-0x0000000000408000-memory.dmp revengerat behavioral1/memory/1980-73-0x0000000000405DCE-mapping.dmp revengerat behavioral1/memory/1148-83-0x0000000000405DCE-mapping.dmp revengerat behavioral1/memory/1712-96-0x0000000000405DCE-mapping.dmp revengerat behavioral1/memory/816-106-0x0000000000405DCE-mapping.dmp revengerat behavioral1/memory/844-114-0x0000000000405DCE-mapping.dmp revengerat -
Drops startup file 2 IoCs
Processes:
WScript.exedescription ioc process File created C:\Users\Admin\AppData\Roaming\Microsoft\Windows\Start Menu\Programs\Startup\1.exe WScript.exe File opened for modification C:\Users\Admin\AppData\Roaming\Microsoft\Windows\Start Menu\Programs\Startup\1.exe WScript.exe -
Suspicious use of SetThreadContext 6 IoCs
Processes:
3b85020323e7b11ba66d785eaf5fa7e3cf3e21791f6b97e6abef4f579266fa3d.exedescription pid process target process PID 768 set thread context of 1760 768 3b85020323e7b11ba66d785eaf5fa7e3cf3e21791f6b97e6abef4f579266fa3d.exe RegAsm.exe PID 768 set thread context of 1980 768 3b85020323e7b11ba66d785eaf5fa7e3cf3e21791f6b97e6abef4f579266fa3d.exe RegAsm.exe PID 768 set thread context of 1148 768 3b85020323e7b11ba66d785eaf5fa7e3cf3e21791f6b97e6abef4f579266fa3d.exe RegAsm.exe PID 768 set thread context of 1712 768 3b85020323e7b11ba66d785eaf5fa7e3cf3e21791f6b97e6abef4f579266fa3d.exe RegAsm.exe PID 768 set thread context of 816 768 3b85020323e7b11ba66d785eaf5fa7e3cf3e21791f6b97e6abef4f579266fa3d.exe RegAsm.exe PID 768 set thread context of 844 768 3b85020323e7b11ba66d785eaf5fa7e3cf3e21791f6b97e6abef4f579266fa3d.exe RegAsm.exe -
Enumerates physical storage devices 1 TTPs
Attempts to interact with connected storage/optical drive(s). Likely ransomware behaviour.
-
Suspicious use of AdjustPrivilegeToken 5 IoCs
Processes:
RegAsm.exeRegAsm.exeRegAsm.exeRegAsm.exeRegAsm.exedescription pid process Token: SeDebugPrivilege 1980 RegAsm.exe Token: SeDebugPrivilege 1760 RegAsm.exe Token: SeDebugPrivilege 1712 RegAsm.exe Token: SeDebugPrivilege 844 RegAsm.exe Token: SeDebugPrivilege 816 RegAsm.exe -
Suspicious use of WriteProcessMemory 64 IoCs
Processes:
3b85020323e7b11ba66d785eaf5fa7e3cf3e21791f6b97e6abef4f579266fa3d.exedescription pid process target process PID 768 wrote to memory of 1660 768 3b85020323e7b11ba66d785eaf5fa7e3cf3e21791f6b97e6abef4f579266fa3d.exe WScript.exe PID 768 wrote to memory of 1660 768 3b85020323e7b11ba66d785eaf5fa7e3cf3e21791f6b97e6abef4f579266fa3d.exe WScript.exe PID 768 wrote to memory of 1660 768 3b85020323e7b11ba66d785eaf5fa7e3cf3e21791f6b97e6abef4f579266fa3d.exe WScript.exe PID 768 wrote to memory of 1660 768 3b85020323e7b11ba66d785eaf5fa7e3cf3e21791f6b97e6abef4f579266fa3d.exe WScript.exe PID 768 wrote to memory of 1760 768 3b85020323e7b11ba66d785eaf5fa7e3cf3e21791f6b97e6abef4f579266fa3d.exe RegAsm.exe PID 768 wrote to memory of 1760 768 3b85020323e7b11ba66d785eaf5fa7e3cf3e21791f6b97e6abef4f579266fa3d.exe RegAsm.exe PID 768 wrote to memory of 1760 768 3b85020323e7b11ba66d785eaf5fa7e3cf3e21791f6b97e6abef4f579266fa3d.exe RegAsm.exe PID 768 wrote to memory of 1760 768 3b85020323e7b11ba66d785eaf5fa7e3cf3e21791f6b97e6abef4f579266fa3d.exe RegAsm.exe PID 768 wrote to memory of 1760 768 3b85020323e7b11ba66d785eaf5fa7e3cf3e21791f6b97e6abef4f579266fa3d.exe RegAsm.exe PID 768 wrote to memory of 1760 768 3b85020323e7b11ba66d785eaf5fa7e3cf3e21791f6b97e6abef4f579266fa3d.exe RegAsm.exe PID 768 wrote to memory of 1760 768 3b85020323e7b11ba66d785eaf5fa7e3cf3e21791f6b97e6abef4f579266fa3d.exe RegAsm.exe PID 768 wrote to memory of 1760 768 3b85020323e7b11ba66d785eaf5fa7e3cf3e21791f6b97e6abef4f579266fa3d.exe RegAsm.exe PID 768 wrote to memory of 1760 768 3b85020323e7b11ba66d785eaf5fa7e3cf3e21791f6b97e6abef4f579266fa3d.exe RegAsm.exe PID 768 wrote to memory of 1760 768 3b85020323e7b11ba66d785eaf5fa7e3cf3e21791f6b97e6abef4f579266fa3d.exe RegAsm.exe PID 768 wrote to memory of 1760 768 3b85020323e7b11ba66d785eaf5fa7e3cf3e21791f6b97e6abef4f579266fa3d.exe RegAsm.exe PID 768 wrote to memory of 1980 768 3b85020323e7b11ba66d785eaf5fa7e3cf3e21791f6b97e6abef4f579266fa3d.exe RegAsm.exe PID 768 wrote to memory of 1980 768 3b85020323e7b11ba66d785eaf5fa7e3cf3e21791f6b97e6abef4f579266fa3d.exe RegAsm.exe PID 768 wrote to memory of 1980 768 3b85020323e7b11ba66d785eaf5fa7e3cf3e21791f6b97e6abef4f579266fa3d.exe RegAsm.exe PID 768 wrote to memory of 1980 768 3b85020323e7b11ba66d785eaf5fa7e3cf3e21791f6b97e6abef4f579266fa3d.exe RegAsm.exe PID 768 wrote to memory of 1980 768 3b85020323e7b11ba66d785eaf5fa7e3cf3e21791f6b97e6abef4f579266fa3d.exe RegAsm.exe PID 768 wrote to memory of 1980 768 3b85020323e7b11ba66d785eaf5fa7e3cf3e21791f6b97e6abef4f579266fa3d.exe RegAsm.exe PID 768 wrote to memory of 1980 768 3b85020323e7b11ba66d785eaf5fa7e3cf3e21791f6b97e6abef4f579266fa3d.exe RegAsm.exe PID 768 wrote to memory of 1980 768 3b85020323e7b11ba66d785eaf5fa7e3cf3e21791f6b97e6abef4f579266fa3d.exe RegAsm.exe PID 768 wrote to memory of 1980 768 3b85020323e7b11ba66d785eaf5fa7e3cf3e21791f6b97e6abef4f579266fa3d.exe RegAsm.exe PID 768 wrote to memory of 1980 768 3b85020323e7b11ba66d785eaf5fa7e3cf3e21791f6b97e6abef4f579266fa3d.exe RegAsm.exe PID 768 wrote to memory of 1980 768 3b85020323e7b11ba66d785eaf5fa7e3cf3e21791f6b97e6abef4f579266fa3d.exe RegAsm.exe PID 768 wrote to memory of 1148 768 3b85020323e7b11ba66d785eaf5fa7e3cf3e21791f6b97e6abef4f579266fa3d.exe RegAsm.exe PID 768 wrote to memory of 1148 768 3b85020323e7b11ba66d785eaf5fa7e3cf3e21791f6b97e6abef4f579266fa3d.exe RegAsm.exe PID 768 wrote to memory of 1148 768 3b85020323e7b11ba66d785eaf5fa7e3cf3e21791f6b97e6abef4f579266fa3d.exe RegAsm.exe PID 768 wrote to memory of 1148 768 3b85020323e7b11ba66d785eaf5fa7e3cf3e21791f6b97e6abef4f579266fa3d.exe RegAsm.exe PID 768 wrote to memory of 1148 768 3b85020323e7b11ba66d785eaf5fa7e3cf3e21791f6b97e6abef4f579266fa3d.exe RegAsm.exe PID 768 wrote to memory of 1148 768 3b85020323e7b11ba66d785eaf5fa7e3cf3e21791f6b97e6abef4f579266fa3d.exe RegAsm.exe PID 768 wrote to memory of 1148 768 3b85020323e7b11ba66d785eaf5fa7e3cf3e21791f6b97e6abef4f579266fa3d.exe RegAsm.exe PID 768 wrote to memory of 1148 768 3b85020323e7b11ba66d785eaf5fa7e3cf3e21791f6b97e6abef4f579266fa3d.exe RegAsm.exe PID 768 wrote to memory of 1148 768 3b85020323e7b11ba66d785eaf5fa7e3cf3e21791f6b97e6abef4f579266fa3d.exe RegAsm.exe PID 768 wrote to memory of 1148 768 3b85020323e7b11ba66d785eaf5fa7e3cf3e21791f6b97e6abef4f579266fa3d.exe RegAsm.exe PID 768 wrote to memory of 1148 768 3b85020323e7b11ba66d785eaf5fa7e3cf3e21791f6b97e6abef4f579266fa3d.exe RegAsm.exe PID 768 wrote to memory of 1712 768 3b85020323e7b11ba66d785eaf5fa7e3cf3e21791f6b97e6abef4f579266fa3d.exe RegAsm.exe PID 768 wrote to memory of 1712 768 3b85020323e7b11ba66d785eaf5fa7e3cf3e21791f6b97e6abef4f579266fa3d.exe RegAsm.exe PID 768 wrote to memory of 1712 768 3b85020323e7b11ba66d785eaf5fa7e3cf3e21791f6b97e6abef4f579266fa3d.exe RegAsm.exe PID 768 wrote to memory of 1712 768 3b85020323e7b11ba66d785eaf5fa7e3cf3e21791f6b97e6abef4f579266fa3d.exe RegAsm.exe PID 768 wrote to memory of 1712 768 3b85020323e7b11ba66d785eaf5fa7e3cf3e21791f6b97e6abef4f579266fa3d.exe RegAsm.exe PID 768 wrote to memory of 1712 768 3b85020323e7b11ba66d785eaf5fa7e3cf3e21791f6b97e6abef4f579266fa3d.exe RegAsm.exe PID 768 wrote to memory of 1712 768 3b85020323e7b11ba66d785eaf5fa7e3cf3e21791f6b97e6abef4f579266fa3d.exe RegAsm.exe PID 768 wrote to memory of 1712 768 3b85020323e7b11ba66d785eaf5fa7e3cf3e21791f6b97e6abef4f579266fa3d.exe RegAsm.exe PID 768 wrote to memory of 1712 768 3b85020323e7b11ba66d785eaf5fa7e3cf3e21791f6b97e6abef4f579266fa3d.exe RegAsm.exe PID 768 wrote to memory of 1712 768 3b85020323e7b11ba66d785eaf5fa7e3cf3e21791f6b97e6abef4f579266fa3d.exe RegAsm.exe PID 768 wrote to memory of 1712 768 3b85020323e7b11ba66d785eaf5fa7e3cf3e21791f6b97e6abef4f579266fa3d.exe RegAsm.exe PID 768 wrote to memory of 816 768 3b85020323e7b11ba66d785eaf5fa7e3cf3e21791f6b97e6abef4f579266fa3d.exe RegAsm.exe PID 768 wrote to memory of 816 768 3b85020323e7b11ba66d785eaf5fa7e3cf3e21791f6b97e6abef4f579266fa3d.exe RegAsm.exe PID 768 wrote to memory of 816 768 3b85020323e7b11ba66d785eaf5fa7e3cf3e21791f6b97e6abef4f579266fa3d.exe RegAsm.exe PID 768 wrote to memory of 816 768 3b85020323e7b11ba66d785eaf5fa7e3cf3e21791f6b97e6abef4f579266fa3d.exe RegAsm.exe PID 768 wrote to memory of 816 768 3b85020323e7b11ba66d785eaf5fa7e3cf3e21791f6b97e6abef4f579266fa3d.exe RegAsm.exe PID 768 wrote to memory of 816 768 3b85020323e7b11ba66d785eaf5fa7e3cf3e21791f6b97e6abef4f579266fa3d.exe RegAsm.exe PID 768 wrote to memory of 816 768 3b85020323e7b11ba66d785eaf5fa7e3cf3e21791f6b97e6abef4f579266fa3d.exe RegAsm.exe PID 768 wrote to memory of 816 768 3b85020323e7b11ba66d785eaf5fa7e3cf3e21791f6b97e6abef4f579266fa3d.exe RegAsm.exe PID 768 wrote to memory of 816 768 3b85020323e7b11ba66d785eaf5fa7e3cf3e21791f6b97e6abef4f579266fa3d.exe RegAsm.exe PID 768 wrote to memory of 816 768 3b85020323e7b11ba66d785eaf5fa7e3cf3e21791f6b97e6abef4f579266fa3d.exe RegAsm.exe PID 768 wrote to memory of 816 768 3b85020323e7b11ba66d785eaf5fa7e3cf3e21791f6b97e6abef4f579266fa3d.exe RegAsm.exe PID 768 wrote to memory of 844 768 3b85020323e7b11ba66d785eaf5fa7e3cf3e21791f6b97e6abef4f579266fa3d.exe RegAsm.exe PID 768 wrote to memory of 844 768 3b85020323e7b11ba66d785eaf5fa7e3cf3e21791f6b97e6abef4f579266fa3d.exe RegAsm.exe PID 768 wrote to memory of 844 768 3b85020323e7b11ba66d785eaf5fa7e3cf3e21791f6b97e6abef4f579266fa3d.exe RegAsm.exe PID 768 wrote to memory of 844 768 3b85020323e7b11ba66d785eaf5fa7e3cf3e21791f6b97e6abef4f579266fa3d.exe RegAsm.exe PID 768 wrote to memory of 844 768 3b85020323e7b11ba66d785eaf5fa7e3cf3e21791f6b97e6abef4f579266fa3d.exe RegAsm.exe
Processes
-
C:\Users\Admin\AppData\Local\Temp\3b85020323e7b11ba66d785eaf5fa7e3cf3e21791f6b97e6abef4f579266fa3d.exe"C:\Users\Admin\AppData\Local\Temp\3b85020323e7b11ba66d785eaf5fa7e3cf3e21791f6b97e6abef4f579266fa3d.exe"1⤵
- Suspicious use of SetThreadContext
- Suspicious use of WriteProcessMemory
-
C:\Windows\SysWOW64\WScript.exe"C:\Windows\System32\WScript.exe" "C:\Users\Admin\AppData\Roaming\1.vbs"2⤵
- Drops startup file
-
C:\Windows\Microsoft.NET\Framework\v2.0.50727\RegAsm.exe"C:\Windows\Microsoft.NET\Framework\v2.0.50727\RegAsm.exe"2⤵
- Suspicious use of AdjustPrivilegeToken
-
C:\Windows\Microsoft.NET\Framework\v2.0.50727\RegAsm.exe"C:\Windows\Microsoft.NET\Framework\v2.0.50727\RegAsm.exe"2⤵
- Suspicious use of AdjustPrivilegeToken
-
C:\Windows\Microsoft.NET\Framework\v2.0.50727\RegAsm.exe"C:\Windows\Microsoft.NET\Framework\v2.0.50727\RegAsm.exe"2⤵
-
C:\Windows\Microsoft.NET\Framework\v2.0.50727\RegAsm.exe"C:\Windows\Microsoft.NET\Framework\v2.0.50727\RegAsm.exe"2⤵
- Suspicious use of AdjustPrivilegeToken
-
C:\Windows\Microsoft.NET\Framework\v2.0.50727\RegAsm.exe"C:\Windows\Microsoft.NET\Framework\v2.0.50727\RegAsm.exe"2⤵
- Suspicious use of AdjustPrivilegeToken
-
C:\Windows\Microsoft.NET\Framework\v2.0.50727\RegAsm.exe"C:\Windows\Microsoft.NET\Framework\v2.0.50727\RegAsm.exe"2⤵
- Suspicious use of AdjustPrivilegeToken
Network
MITRE ATT&CK Matrix ATT&CK v6
Replay Monitor
Loading Replay Monitor...
Downloads
-
C:\Users\Admin\AppData\Roaming\1.vbsFilesize
355B
MD5f46b01af063ab26583cbc102f0d7faa9
SHA1dc86052d4e60f31b9bd569f392b039f1da3a5ab8
SHA256a734c682eeff369adac414474ab1d8427a6505b246dcd55982a35ac7bf9d6f5f
SHA5122e8ae969dfc975b601513bda8e57988f919ade03e61f14637872cd42a303602b44c699cdfe1320909eaf7aef544820af1a91525e614aa78c1f624679c1fc294f
-
memory/768-54-0x0000000076AE1000-0x0000000076AE3000-memory.dmpFilesize
8KB
-
memory/816-130-0x0000000074700000-0x0000000074CAB000-memory.dmpFilesize
5.7MB
-
memory/816-106-0x0000000000405DCE-mapping.dmp
-
memory/844-129-0x0000000074700000-0x0000000074CAB000-memory.dmpFilesize
5.7MB
-
memory/844-114-0x0000000000405DCE-mapping.dmp
-
memory/1148-123-0x0000000074700000-0x0000000074CAB000-memory.dmpFilesize
5.7MB
-
memory/1148-83-0x0000000000405DCE-mapping.dmp
-
memory/1660-55-0x0000000000000000-mapping.dmp
-
memory/1712-96-0x0000000000405DCE-mapping.dmp
-
memory/1712-128-0x0000000074700000-0x0000000074CAB000-memory.dmpFilesize
5.7MB
-
memory/1712-127-0x0000000074700000-0x0000000074CAB000-memory.dmpFilesize
5.7MB
-
memory/1760-61-0x0000000000400000-0x0000000000408000-memory.dmpFilesize
32KB
-
memory/1760-70-0x0000000000400000-0x0000000000408000-memory.dmpFilesize
32KB
-
memory/1760-66-0x0000000000400000-0x0000000000408000-memory.dmpFilesize
32KB
-
memory/1760-126-0x0000000074700000-0x0000000074CAB000-memory.dmpFilesize
5.7MB
-
memory/1760-62-0x0000000000400000-0x0000000000408000-memory.dmpFilesize
32KB
-
memory/1760-63-0x0000000000405DCE-mapping.dmp
-
memory/1760-58-0x0000000000400000-0x0000000000408000-memory.dmpFilesize
32KB
-
memory/1760-59-0x0000000000400000-0x0000000000408000-memory.dmpFilesize
32KB
-
memory/1760-131-0x0000000074700000-0x0000000074CAB000-memory.dmpFilesize
5.7MB
-
memory/1980-73-0x0000000000405DCE-mapping.dmp
-
memory/1980-121-0x0000000074700000-0x0000000074CAB000-memory.dmpFilesize
5.7MB