Analysis
-
max time kernel
155s -
max time network
184s -
platform
windows10-2004_x64 -
resource
win10v2004-20221111-en -
resource tags
arch:x64arch:x86image:win10v2004-20221111-enlocale:en-usos:windows10-2004-x64system -
submitted
05/12/2022, 21:22
Static task
static1
Behavioral task
behavioral1
Sample
de30ce4e4ba0dc7bcdd4931ff34fd4dfe45c571761b8be67ddcfedd6bea49e59.exe
Resource
win7-20221111-en
Behavioral task
behavioral2
Sample
de30ce4e4ba0dc7bcdd4931ff34fd4dfe45c571761b8be67ddcfedd6bea49e59.exe
Resource
win10v2004-20221111-en
General
-
Target
de30ce4e4ba0dc7bcdd4931ff34fd4dfe45c571761b8be67ddcfedd6bea49e59.exe
-
Size
160KB
-
MD5
f8795a8b2597f8f3ccdeba9cc5240e74
-
SHA1
54a08dc3a1e901e37148e301274cd1d70ab1932b
-
SHA256
de30ce4e4ba0dc7bcdd4931ff34fd4dfe45c571761b8be67ddcfedd6bea49e59
-
SHA512
df19c45adf504c468be923f874d3fc94306e08b9d790702692abca2bc340dc5b5a70c9a6bb9d15de3ad5e872972f2ca52a632ceaaa2c603c944d55f7f33b4c7c
-
SSDEEP
1536:LWOeyIbBCNqAh5P+g0s5CXf9HpHpMbKgyAptwM9VyTwEUg4rBgWNz:G1BCV5P+g0s5CXBq5frEU/V
Malware Config
Signatures
-
Suspicious use of SetThreadContext 2 IoCs
description pid Process procid_target PID 4268 set thread context of 1932 4268 de30ce4e4ba0dc7bcdd4931ff34fd4dfe45c571761b8be67ddcfedd6bea49e59.exe 83 PID 1932 set thread context of 4356 1932 de30ce4e4ba0dc7bcdd4931ff34fd4dfe45c571761b8be67ddcfedd6bea49e59.exe 84 -
Suspicious use of SetWindowsHookEx 2 IoCs
pid Process 4268 de30ce4e4ba0dc7bcdd4931ff34fd4dfe45c571761b8be67ddcfedd6bea49e59.exe 1932 de30ce4e4ba0dc7bcdd4931ff34fd4dfe45c571761b8be67ddcfedd6bea49e59.exe -
Suspicious use of WriteProcessMemory 15 IoCs
description pid Process procid_target PID 4268 wrote to memory of 1932 4268 de30ce4e4ba0dc7bcdd4931ff34fd4dfe45c571761b8be67ddcfedd6bea49e59.exe 83 PID 4268 wrote to memory of 1932 4268 de30ce4e4ba0dc7bcdd4931ff34fd4dfe45c571761b8be67ddcfedd6bea49e59.exe 83 PID 4268 wrote to memory of 1932 4268 de30ce4e4ba0dc7bcdd4931ff34fd4dfe45c571761b8be67ddcfedd6bea49e59.exe 83 PID 4268 wrote to memory of 1932 4268 de30ce4e4ba0dc7bcdd4931ff34fd4dfe45c571761b8be67ddcfedd6bea49e59.exe 83 PID 4268 wrote to memory of 1932 4268 de30ce4e4ba0dc7bcdd4931ff34fd4dfe45c571761b8be67ddcfedd6bea49e59.exe 83 PID 4268 wrote to memory of 1932 4268 de30ce4e4ba0dc7bcdd4931ff34fd4dfe45c571761b8be67ddcfedd6bea49e59.exe 83 PID 4268 wrote to memory of 1932 4268 de30ce4e4ba0dc7bcdd4931ff34fd4dfe45c571761b8be67ddcfedd6bea49e59.exe 83 PID 4268 wrote to memory of 1932 4268 de30ce4e4ba0dc7bcdd4931ff34fd4dfe45c571761b8be67ddcfedd6bea49e59.exe 83 PID 1932 wrote to memory of 4356 1932 de30ce4e4ba0dc7bcdd4931ff34fd4dfe45c571761b8be67ddcfedd6bea49e59.exe 84 PID 1932 wrote to memory of 4356 1932 de30ce4e4ba0dc7bcdd4931ff34fd4dfe45c571761b8be67ddcfedd6bea49e59.exe 84 PID 1932 wrote to memory of 4356 1932 de30ce4e4ba0dc7bcdd4931ff34fd4dfe45c571761b8be67ddcfedd6bea49e59.exe 84 PID 1932 wrote to memory of 4356 1932 de30ce4e4ba0dc7bcdd4931ff34fd4dfe45c571761b8be67ddcfedd6bea49e59.exe 84 PID 1932 wrote to memory of 4356 1932 de30ce4e4ba0dc7bcdd4931ff34fd4dfe45c571761b8be67ddcfedd6bea49e59.exe 84 PID 1932 wrote to memory of 4356 1932 de30ce4e4ba0dc7bcdd4931ff34fd4dfe45c571761b8be67ddcfedd6bea49e59.exe 84 PID 1932 wrote to memory of 4356 1932 de30ce4e4ba0dc7bcdd4931ff34fd4dfe45c571761b8be67ddcfedd6bea49e59.exe 84
Processes
-
C:\Users\Admin\AppData\Local\Temp\de30ce4e4ba0dc7bcdd4931ff34fd4dfe45c571761b8be67ddcfedd6bea49e59.exe"C:\Users\Admin\AppData\Local\Temp\de30ce4e4ba0dc7bcdd4931ff34fd4dfe45c571761b8be67ddcfedd6bea49e59.exe"1⤵
- Suspicious use of SetThreadContext
- Suspicious use of SetWindowsHookEx
- Suspicious use of WriteProcessMemory
PID:4268 -
C:\Users\Admin\AppData\Local\Temp\de30ce4e4ba0dc7bcdd4931ff34fd4dfe45c571761b8be67ddcfedd6bea49e59.exe
- Suspicious use of SetThreadContext
- Suspicious use of SetWindowsHookEx
- Suspicious use of WriteProcessMemory
PID:1932 -
C:\Users\Admin\AppData\Local\Temp\de30ce4e4ba0dc7bcdd4931ff34fd4dfe45c571761b8be67ddcfedd6bea49e59.exeC:\Users\Admin\AppData\Local\Temp\de30ce4e4ba0dc7bcdd4931ff34fd4dfe45c571761b8be67ddcfedd6bea49e59.exe3⤵PID:4356
-
-