Analysis
-
max time kernel
146s -
max time network
151s -
platform
windows10-2004_x64 -
resource
win10v2004-20220901-en -
resource tags
arch:x64arch:x86image:win10v2004-20220901-enlocale:en-usos:windows10-2004-x64system -
submitted
05/12/2022, 22:00
Behavioral task
behavioral1
Sample
f86d8d41a9d9ed74eedfb175b763e8dbef598052bbf7cba1aef9a596d4fa9405.exe
Resource
win7-20220812-en
windows7-x64
7 signatures
150 seconds
Behavioral task
behavioral2
Sample
f86d8d41a9d9ed74eedfb175b763e8dbef598052bbf7cba1aef9a596d4fa9405.exe
Resource
win10v2004-20220901-en
windows10-2004-x64
7 signatures
150 seconds
General
-
Target
f86d8d41a9d9ed74eedfb175b763e8dbef598052bbf7cba1aef9a596d4fa9405.exe
-
Size
194KB
-
MD5
92286040373b233a6f611973eada0b00
-
SHA1
be3af3dbf8de5495662d47ae1f61060d817612ac
-
SHA256
f86d8d41a9d9ed74eedfb175b763e8dbef598052bbf7cba1aef9a596d4fa9405
-
SHA512
aeee2d9e86199276ebce66e62d67140b173756d6f501c2106cbf7702d8289877bb347ec4200925d4f07a8089cba811a8235f69c3942078db927adb3573f55497
-
SSDEEP
3072:RiWmAlxYYXbeItPPjtq0svSa51sH4fUlknOF1d2sjca4vy:PxYYXbeICYa51ilkODd2sjh4vy
Score
8/10
Malware Config
Signatures
-
Adds policy Run key to start application 2 TTPs 4 IoCs
description ioc Process Key created \REGISTRY\USER\S-1-5-21-929662420-1054238289-2961194603-1000\Software\Microsoft\Windows\CurrentVersion\Policies\Explorer\Run f86d8d41a9d9ed74eedfb175b763e8dbef598052bbf7cba1aef9a596d4fa9405.exe Set value (str) \REGISTRY\USER\S-1-5-21-929662420-1054238289-2961194603-1000\SOFTWARE\Microsoft\Windows\CurrentVersion\Policies\Explorer\Run\Policies = "c:\\Rs\\install\\install\\server.exe" f86d8d41a9d9ed74eedfb175b763e8dbef598052bbf7cba1aef9a596d4fa9405.exe Key created \REGISTRY\MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Policies\Explorer\Run f86d8d41a9d9ed74eedfb175b763e8dbef598052bbf7cba1aef9a596d4fa9405.exe Set value (str) \REGISTRY\MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Policies\Explorer\Run\Policies = "c:\\Rs\\install\\install\\server.exe" f86d8d41a9d9ed74eedfb175b763e8dbef598052bbf7cba1aef9a596d4fa9405.exe -
Modifies Installed Components in the registry 2 TTPs 2 IoCs
description ioc Process Key created \REGISTRY\MACHINE\Software\WOW6432Node\Microsoft\Active Setup\Installed Components\{08B0E5JF-4FCB-11CF-AAA5-00401C6XX500} f86d8d41a9d9ed74eedfb175b763e8dbef598052bbf7cba1aef9a596d4fa9405.exe Set value (str) \REGISTRY\MACHINE\SOFTWARE\WOW6432Node\Microsoft\Active Setup\Installed Components\{08B0E5JF-4FCB-11CF-AAA5-00401C6XX500}\StubPath = "c:\\Rs\\install\\install\\server.exe Restart" f86d8d41a9d9ed74eedfb175b763e8dbef598052bbf7cba1aef9a596d4fa9405.exe -
resource yara_rule behavioral2/memory/5064-133-0x0000000024010000-0x0000000024049000-memory.dmp upx behavioral2/memory/5064-138-0x0000000024050000-0x0000000024089000-memory.dmp upx behavioral2/memory/4324-141-0x0000000024050000-0x0000000024089000-memory.dmp upx behavioral2/memory/4324-142-0x0000000024050000-0x0000000024089000-memory.dmp upx behavioral2/memory/4324-144-0x0000000024050000-0x0000000024089000-memory.dmp upx -
Suspicious behavior: EnumeratesProcesses 2 IoCs
pid Process 5064 f86d8d41a9d9ed74eedfb175b763e8dbef598052bbf7cba1aef9a596d4fa9405.exe 5064 f86d8d41a9d9ed74eedfb175b763e8dbef598052bbf7cba1aef9a596d4fa9405.exe -
Suspicious behavior: GetForegroundWindowSpam 1 IoCs
pid Process 4324 f86d8d41a9d9ed74eedfb175b763e8dbef598052bbf7cba1aef9a596d4fa9405.exe -
Suspicious use of AdjustPrivilegeToken 2 IoCs
description pid Process Token: SeDebugPrivilege 4324 f86d8d41a9d9ed74eedfb175b763e8dbef598052bbf7cba1aef9a596d4fa9405.exe Token: SeDebugPrivilege 4324 f86d8d41a9d9ed74eedfb175b763e8dbef598052bbf7cba1aef9a596d4fa9405.exe -
Suspicious use of WriteProcessMemory 64 IoCs
description pid Process procid_target PID 5064 wrote to memory of 5080 5064 f86d8d41a9d9ed74eedfb175b763e8dbef598052bbf7cba1aef9a596d4fa9405.exe 76 PID 5064 wrote to memory of 5080 5064 f86d8d41a9d9ed74eedfb175b763e8dbef598052bbf7cba1aef9a596d4fa9405.exe 76 PID 5064 wrote to memory of 5080 5064 f86d8d41a9d9ed74eedfb175b763e8dbef598052bbf7cba1aef9a596d4fa9405.exe 76 PID 5064 wrote to memory of 5080 5064 f86d8d41a9d9ed74eedfb175b763e8dbef598052bbf7cba1aef9a596d4fa9405.exe 76 PID 5064 wrote to memory of 5080 5064 f86d8d41a9d9ed74eedfb175b763e8dbef598052bbf7cba1aef9a596d4fa9405.exe 76 PID 5064 wrote to memory of 5080 5064 f86d8d41a9d9ed74eedfb175b763e8dbef598052bbf7cba1aef9a596d4fa9405.exe 76 PID 5064 wrote to memory of 5080 5064 f86d8d41a9d9ed74eedfb175b763e8dbef598052bbf7cba1aef9a596d4fa9405.exe 76 PID 5064 wrote to memory of 5080 5064 f86d8d41a9d9ed74eedfb175b763e8dbef598052bbf7cba1aef9a596d4fa9405.exe 76 PID 5064 wrote to memory of 5080 5064 f86d8d41a9d9ed74eedfb175b763e8dbef598052bbf7cba1aef9a596d4fa9405.exe 76 PID 5064 wrote to memory of 5080 5064 f86d8d41a9d9ed74eedfb175b763e8dbef598052bbf7cba1aef9a596d4fa9405.exe 76 PID 5064 wrote to memory of 5080 5064 f86d8d41a9d9ed74eedfb175b763e8dbef598052bbf7cba1aef9a596d4fa9405.exe 76 PID 5064 wrote to memory of 5080 5064 f86d8d41a9d9ed74eedfb175b763e8dbef598052bbf7cba1aef9a596d4fa9405.exe 76 PID 5064 wrote to memory of 5080 5064 f86d8d41a9d9ed74eedfb175b763e8dbef598052bbf7cba1aef9a596d4fa9405.exe 76 PID 5064 wrote to memory of 5080 5064 f86d8d41a9d9ed74eedfb175b763e8dbef598052bbf7cba1aef9a596d4fa9405.exe 76 PID 5064 wrote to memory of 5080 5064 f86d8d41a9d9ed74eedfb175b763e8dbef598052bbf7cba1aef9a596d4fa9405.exe 76 PID 5064 wrote to memory of 5080 5064 f86d8d41a9d9ed74eedfb175b763e8dbef598052bbf7cba1aef9a596d4fa9405.exe 76 PID 5064 wrote to memory of 5080 5064 f86d8d41a9d9ed74eedfb175b763e8dbef598052bbf7cba1aef9a596d4fa9405.exe 76 PID 5064 wrote to memory of 5080 5064 f86d8d41a9d9ed74eedfb175b763e8dbef598052bbf7cba1aef9a596d4fa9405.exe 76 PID 5064 wrote to memory of 5080 5064 f86d8d41a9d9ed74eedfb175b763e8dbef598052bbf7cba1aef9a596d4fa9405.exe 76 PID 5064 wrote to memory of 5080 5064 f86d8d41a9d9ed74eedfb175b763e8dbef598052bbf7cba1aef9a596d4fa9405.exe 76 PID 5064 wrote to memory of 5080 5064 f86d8d41a9d9ed74eedfb175b763e8dbef598052bbf7cba1aef9a596d4fa9405.exe 76 PID 5064 wrote to memory of 5080 5064 f86d8d41a9d9ed74eedfb175b763e8dbef598052bbf7cba1aef9a596d4fa9405.exe 76 PID 5064 wrote to memory of 5080 5064 f86d8d41a9d9ed74eedfb175b763e8dbef598052bbf7cba1aef9a596d4fa9405.exe 76 PID 5064 wrote to memory of 5080 5064 f86d8d41a9d9ed74eedfb175b763e8dbef598052bbf7cba1aef9a596d4fa9405.exe 76 PID 5064 wrote to memory of 5080 5064 f86d8d41a9d9ed74eedfb175b763e8dbef598052bbf7cba1aef9a596d4fa9405.exe 76 PID 5064 wrote to memory of 5080 5064 f86d8d41a9d9ed74eedfb175b763e8dbef598052bbf7cba1aef9a596d4fa9405.exe 76 PID 5064 wrote to memory of 5080 5064 f86d8d41a9d9ed74eedfb175b763e8dbef598052bbf7cba1aef9a596d4fa9405.exe 76 PID 5064 wrote to memory of 5080 5064 f86d8d41a9d9ed74eedfb175b763e8dbef598052bbf7cba1aef9a596d4fa9405.exe 76 PID 5064 wrote to memory of 5080 5064 f86d8d41a9d9ed74eedfb175b763e8dbef598052bbf7cba1aef9a596d4fa9405.exe 76 PID 5064 wrote to memory of 5080 5064 f86d8d41a9d9ed74eedfb175b763e8dbef598052bbf7cba1aef9a596d4fa9405.exe 76 PID 5064 wrote to memory of 5080 5064 f86d8d41a9d9ed74eedfb175b763e8dbef598052bbf7cba1aef9a596d4fa9405.exe 76 PID 5064 wrote to memory of 5080 5064 f86d8d41a9d9ed74eedfb175b763e8dbef598052bbf7cba1aef9a596d4fa9405.exe 76 PID 5064 wrote to memory of 5080 5064 f86d8d41a9d9ed74eedfb175b763e8dbef598052bbf7cba1aef9a596d4fa9405.exe 76 PID 5064 wrote to memory of 5080 5064 f86d8d41a9d9ed74eedfb175b763e8dbef598052bbf7cba1aef9a596d4fa9405.exe 76 PID 5064 wrote to memory of 5080 5064 f86d8d41a9d9ed74eedfb175b763e8dbef598052bbf7cba1aef9a596d4fa9405.exe 76 PID 5064 wrote to memory of 5080 5064 f86d8d41a9d9ed74eedfb175b763e8dbef598052bbf7cba1aef9a596d4fa9405.exe 76 PID 5064 wrote to memory of 5080 5064 f86d8d41a9d9ed74eedfb175b763e8dbef598052bbf7cba1aef9a596d4fa9405.exe 76 PID 5064 wrote to memory of 5080 5064 f86d8d41a9d9ed74eedfb175b763e8dbef598052bbf7cba1aef9a596d4fa9405.exe 76 PID 5064 wrote to memory of 5080 5064 f86d8d41a9d9ed74eedfb175b763e8dbef598052bbf7cba1aef9a596d4fa9405.exe 76 PID 5064 wrote to memory of 5080 5064 f86d8d41a9d9ed74eedfb175b763e8dbef598052bbf7cba1aef9a596d4fa9405.exe 76 PID 5064 wrote to memory of 5080 5064 f86d8d41a9d9ed74eedfb175b763e8dbef598052bbf7cba1aef9a596d4fa9405.exe 76 PID 5064 wrote to memory of 5080 5064 f86d8d41a9d9ed74eedfb175b763e8dbef598052bbf7cba1aef9a596d4fa9405.exe 76 PID 5064 wrote to memory of 5080 5064 f86d8d41a9d9ed74eedfb175b763e8dbef598052bbf7cba1aef9a596d4fa9405.exe 76 PID 5064 wrote to memory of 5080 5064 f86d8d41a9d9ed74eedfb175b763e8dbef598052bbf7cba1aef9a596d4fa9405.exe 76 PID 5064 wrote to memory of 5080 5064 f86d8d41a9d9ed74eedfb175b763e8dbef598052bbf7cba1aef9a596d4fa9405.exe 76 PID 5064 wrote to memory of 5080 5064 f86d8d41a9d9ed74eedfb175b763e8dbef598052bbf7cba1aef9a596d4fa9405.exe 76 PID 5064 wrote to memory of 5080 5064 f86d8d41a9d9ed74eedfb175b763e8dbef598052bbf7cba1aef9a596d4fa9405.exe 76 PID 5064 wrote to memory of 5080 5064 f86d8d41a9d9ed74eedfb175b763e8dbef598052bbf7cba1aef9a596d4fa9405.exe 76 PID 5064 wrote to memory of 5080 5064 f86d8d41a9d9ed74eedfb175b763e8dbef598052bbf7cba1aef9a596d4fa9405.exe 76 PID 5064 wrote to memory of 5080 5064 f86d8d41a9d9ed74eedfb175b763e8dbef598052bbf7cba1aef9a596d4fa9405.exe 76 PID 5064 wrote to memory of 5080 5064 f86d8d41a9d9ed74eedfb175b763e8dbef598052bbf7cba1aef9a596d4fa9405.exe 76 PID 5064 wrote to memory of 5080 5064 f86d8d41a9d9ed74eedfb175b763e8dbef598052bbf7cba1aef9a596d4fa9405.exe 76 PID 5064 wrote to memory of 5080 5064 f86d8d41a9d9ed74eedfb175b763e8dbef598052bbf7cba1aef9a596d4fa9405.exe 76 PID 5064 wrote to memory of 5080 5064 f86d8d41a9d9ed74eedfb175b763e8dbef598052bbf7cba1aef9a596d4fa9405.exe 76 PID 5064 wrote to memory of 5080 5064 f86d8d41a9d9ed74eedfb175b763e8dbef598052bbf7cba1aef9a596d4fa9405.exe 76 PID 5064 wrote to memory of 5080 5064 f86d8d41a9d9ed74eedfb175b763e8dbef598052bbf7cba1aef9a596d4fa9405.exe 76 PID 5064 wrote to memory of 5080 5064 f86d8d41a9d9ed74eedfb175b763e8dbef598052bbf7cba1aef9a596d4fa9405.exe 76 PID 5064 wrote to memory of 5080 5064 f86d8d41a9d9ed74eedfb175b763e8dbef598052bbf7cba1aef9a596d4fa9405.exe 76 PID 5064 wrote to memory of 5080 5064 f86d8d41a9d9ed74eedfb175b763e8dbef598052bbf7cba1aef9a596d4fa9405.exe 76 PID 5064 wrote to memory of 5080 5064 f86d8d41a9d9ed74eedfb175b763e8dbef598052bbf7cba1aef9a596d4fa9405.exe 76 PID 5064 wrote to memory of 5080 5064 f86d8d41a9d9ed74eedfb175b763e8dbef598052bbf7cba1aef9a596d4fa9405.exe 76 PID 5064 wrote to memory of 5080 5064 f86d8d41a9d9ed74eedfb175b763e8dbef598052bbf7cba1aef9a596d4fa9405.exe 76 PID 5064 wrote to memory of 5080 5064 f86d8d41a9d9ed74eedfb175b763e8dbef598052bbf7cba1aef9a596d4fa9405.exe 76 PID 5064 wrote to memory of 5080 5064 f86d8d41a9d9ed74eedfb175b763e8dbef598052bbf7cba1aef9a596d4fa9405.exe 76
Processes
-
C:\Users\Admin\AppData\Local\Temp\f86d8d41a9d9ed74eedfb175b763e8dbef598052bbf7cba1aef9a596d4fa9405.exe"C:\Users\Admin\AppData\Local\Temp\f86d8d41a9d9ed74eedfb175b763e8dbef598052bbf7cba1aef9a596d4fa9405.exe"1⤵
- Adds policy Run key to start application
- Modifies Installed Components in the registry
- Suspicious behavior: EnumeratesProcesses
- Suspicious use of WriteProcessMemory
PID:5064 -
C:\Program Files\Internet Explorer\iexplore.exe"C:\Program Files\Internet Explorer\iexplore.exe"2⤵PID:5080
-
-
C:\Users\Admin\AppData\Local\Temp\f86d8d41a9d9ed74eedfb175b763e8dbef598052bbf7cba1aef9a596d4fa9405.exe"C:\Users\Admin\AppData\Local\Temp\f86d8d41a9d9ed74eedfb175b763e8dbef598052bbf7cba1aef9a596d4fa9405.exe"2⤵
- Suspicious behavior: GetForegroundWindowSpam
- Suspicious use of AdjustPrivilegeToken
PID:4324
-
Network
MITRE ATT&CK Enterprise v6
Replay Monitor
Loading Replay Monitor...
Downloads
-
Filesize
133KB
MD5230925ad84a55e250be9c3a66283428e
SHA14c5e7b7be574e47f01f767d82238d0e2945a22f3
SHA25668c6c9a1429f90558843642562faf6ecb0a169b64cdf26ff0544dc14aedf6c30
SHA512b5de0d51253d99e51122d1f26da6a4c9cd01a852e1af9b19c009a4282baabd7d7f103edda4e293e2068fb4efdb4db9ac877aae6f272f0cb5856e6f44b5c953b0