Analysis
-
max time kernel
135s -
max time network
106s -
platform
windows10-2004_x64 -
resource
win10v2004-20240426-en -
resource tags
arch:x64arch:x86image:win10v2004-20240426-enlocale:en-usos:windows10-2004-x64system -
submitted
26-05-2024 11:00
Static task
static1
1 signatures
Behavioral task
behavioral1
Sample
f04cb1b8a8beb6a51b0beb2867d18dc6df2352afb67a3c85233a7383c1ce3617.exe
Resource
win7-20240508-en
windows7-x64
2 signatures
150 seconds
General
-
Target
f04cb1b8a8beb6a51b0beb2867d18dc6df2352afb67a3c85233a7383c1ce3617.exe
-
Size
2.9MB
-
MD5
8eb3c7bc1ad38ae064eda594deed070b
-
SHA1
58d2d8baa9a14ece4ae12b6cd3260e79c7003059
-
SHA256
f04cb1b8a8beb6a51b0beb2867d18dc6df2352afb67a3c85233a7383c1ce3617
-
SHA512
4c86c4e290b678faecf906719c183fe190ce88e7242ae25af35887c12da9e4184010a94854cf12e49342074d56097dc117439f9711600f110222c264fa730648
-
SSDEEP
49152:U4D5fBZcSZW/ym3NyBWvYPywzniB/U+0DqKwoszSwKWFQpFR7IUyq3QqumQhG/75:U+W/D3gBlmB/URKos9z2pFF/puLc71
Malware Config
Extracted
Family
risepro
C2
118.194.235.187:50500
Signatures
-
Suspicious use of SetThreadContext 1 IoCs
Processes:
f04cb1b8a8beb6a51b0beb2867d18dc6df2352afb67a3c85233a7383c1ce3617.exedescription pid process target process PID 4408 set thread context of 1260 4408 f04cb1b8a8beb6a51b0beb2867d18dc6df2352afb67a3c85233a7383c1ce3617.exe RegAsm.exe -
Program crash 1 IoCs
Processes:
WerFault.exepid pid_target process target process 1748 4408 WerFault.exe f04cb1b8a8beb6a51b0beb2867d18dc6df2352afb67a3c85233a7383c1ce3617.exe -
Suspicious use of WriteProcessMemory 21 IoCs
Processes:
f04cb1b8a8beb6a51b0beb2867d18dc6df2352afb67a3c85233a7383c1ce3617.exedescription pid process target process PID 4408 wrote to memory of 3536 4408 f04cb1b8a8beb6a51b0beb2867d18dc6df2352afb67a3c85233a7383c1ce3617.exe RegAsm.exe PID 4408 wrote to memory of 3536 4408 f04cb1b8a8beb6a51b0beb2867d18dc6df2352afb67a3c85233a7383c1ce3617.exe RegAsm.exe PID 4408 wrote to memory of 3536 4408 f04cb1b8a8beb6a51b0beb2867d18dc6df2352afb67a3c85233a7383c1ce3617.exe RegAsm.exe PID 4408 wrote to memory of 4644 4408 f04cb1b8a8beb6a51b0beb2867d18dc6df2352afb67a3c85233a7383c1ce3617.exe RegAsm.exe PID 4408 wrote to memory of 4644 4408 f04cb1b8a8beb6a51b0beb2867d18dc6df2352afb67a3c85233a7383c1ce3617.exe RegAsm.exe PID 4408 wrote to memory of 4644 4408 f04cb1b8a8beb6a51b0beb2867d18dc6df2352afb67a3c85233a7383c1ce3617.exe RegAsm.exe PID 4408 wrote to memory of 3992 4408 f04cb1b8a8beb6a51b0beb2867d18dc6df2352afb67a3c85233a7383c1ce3617.exe RegAsm.exe PID 4408 wrote to memory of 3992 4408 f04cb1b8a8beb6a51b0beb2867d18dc6df2352afb67a3c85233a7383c1ce3617.exe RegAsm.exe PID 4408 wrote to memory of 3992 4408 f04cb1b8a8beb6a51b0beb2867d18dc6df2352afb67a3c85233a7383c1ce3617.exe RegAsm.exe PID 4408 wrote to memory of 1260 4408 f04cb1b8a8beb6a51b0beb2867d18dc6df2352afb67a3c85233a7383c1ce3617.exe RegAsm.exe PID 4408 wrote to memory of 1260 4408 f04cb1b8a8beb6a51b0beb2867d18dc6df2352afb67a3c85233a7383c1ce3617.exe RegAsm.exe PID 4408 wrote to memory of 1260 4408 f04cb1b8a8beb6a51b0beb2867d18dc6df2352afb67a3c85233a7383c1ce3617.exe RegAsm.exe PID 4408 wrote to memory of 1260 4408 f04cb1b8a8beb6a51b0beb2867d18dc6df2352afb67a3c85233a7383c1ce3617.exe RegAsm.exe PID 4408 wrote to memory of 1260 4408 f04cb1b8a8beb6a51b0beb2867d18dc6df2352afb67a3c85233a7383c1ce3617.exe RegAsm.exe PID 4408 wrote to memory of 1260 4408 f04cb1b8a8beb6a51b0beb2867d18dc6df2352afb67a3c85233a7383c1ce3617.exe RegAsm.exe PID 4408 wrote to memory of 1260 4408 f04cb1b8a8beb6a51b0beb2867d18dc6df2352afb67a3c85233a7383c1ce3617.exe RegAsm.exe PID 4408 wrote to memory of 1260 4408 f04cb1b8a8beb6a51b0beb2867d18dc6df2352afb67a3c85233a7383c1ce3617.exe RegAsm.exe PID 4408 wrote to memory of 1260 4408 f04cb1b8a8beb6a51b0beb2867d18dc6df2352afb67a3c85233a7383c1ce3617.exe RegAsm.exe PID 4408 wrote to memory of 1260 4408 f04cb1b8a8beb6a51b0beb2867d18dc6df2352afb67a3c85233a7383c1ce3617.exe RegAsm.exe PID 4408 wrote to memory of 1260 4408 f04cb1b8a8beb6a51b0beb2867d18dc6df2352afb67a3c85233a7383c1ce3617.exe RegAsm.exe PID 4408 wrote to memory of 1260 4408 f04cb1b8a8beb6a51b0beb2867d18dc6df2352afb67a3c85233a7383c1ce3617.exe RegAsm.exe
Processes
-
C:\Users\Admin\AppData\Local\Temp\f04cb1b8a8beb6a51b0beb2867d18dc6df2352afb67a3c85233a7383c1ce3617.exe"C:\Users\Admin\AppData\Local\Temp\f04cb1b8a8beb6a51b0beb2867d18dc6df2352afb67a3c85233a7383c1ce3617.exe"1⤵
- Suspicious use of SetThreadContext
- Suspicious use of WriteProcessMemory
PID:4408 -
C:\Windows\Microsoft.NET\Framework\v4.0.30319\RegAsm.exe"C:\Windows\Microsoft.NET\Framework\v4.0.30319\RegAsm.exe"2⤵PID:3536
-
-
C:\Windows\Microsoft.NET\Framework\v4.0.30319\RegAsm.exe"C:\Windows\Microsoft.NET\Framework\v4.0.30319\RegAsm.exe"2⤵PID:4644
-
-
C:\Windows\Microsoft.NET\Framework\v4.0.30319\RegAsm.exe"C:\Windows\Microsoft.NET\Framework\v4.0.30319\RegAsm.exe"2⤵PID:3992
-
-
C:\Windows\Microsoft.NET\Framework\v4.0.30319\RegAsm.exe"C:\Windows\Microsoft.NET\Framework\v4.0.30319\RegAsm.exe"2⤵PID:1260
-
-
C:\Windows\SysWOW64\WerFault.exeC:\Windows\SysWOW64\WerFault.exe -u -p 4408 -s 3002⤵
- Program crash
PID:1748
-
-
C:\Windows\SysWOW64\WerFault.exeC:\Windows\SysWOW64\WerFault.exe -pss -s 424 -p 4408 -ip 44081⤵PID:1416