Analysis
-
max time kernel
153s -
max time network
177s -
platform
windows10-2004_x64 -
resource
win10v2004-20221111-en -
resource tags
arch:x64arch:x86image:win10v2004-20221111-enlocale:en-usos:windows10-2004-x64system -
submitted
06/12/2022, 10:50
Static task
static1
Behavioral task
behavioral1
Sample
9a113fb097c1cee87961a2ecc9d83b583d5bb7c568fd6b4356f4dad9c0540c89.exe
Resource
win7-20220812-en
Behavioral task
behavioral2
Sample
9a113fb097c1cee87961a2ecc9d83b583d5bb7c568fd6b4356f4dad9c0540c89.exe
Resource
win10v2004-20221111-en
General
-
Target
9a113fb097c1cee87961a2ecc9d83b583d5bb7c568fd6b4356f4dad9c0540c89.exe
-
Size
228KB
-
MD5
75d0ae83d06d5f04b2552f0110842edb
-
SHA1
8a6f838a6d0976b92bd9d8e3493393e6866a9b2b
-
SHA256
9a113fb097c1cee87961a2ecc9d83b583d5bb7c568fd6b4356f4dad9c0540c89
-
SHA512
bc5346965422fac5d685ae17beb3b1798396460f874b0548fac896d5bf51a89e028974738351e64ef074a725128b28f13420daef08e8b7d9bb76fe437d7a7a4c
-
SSDEEP
6144:Ei7xr4iYl2989s9xnP+wIJQIPNJjOB9QuLLJ8ve9uV:EWxrPcs9xnWwICIP+QuLLJqecV
Malware Config
Signatures
-
resource yara_rule behavioral2/memory/368-138-0x0000000000400000-0x0000000000427000-memory.dmp upx behavioral2/memory/368-140-0x0000000000400000-0x0000000000427000-memory.dmp upx behavioral2/memory/368-142-0x0000000000400000-0x0000000000427000-memory.dmp upx behavioral2/memory/368-148-0x0000000000400000-0x0000000000427000-memory.dmp upx -
Suspicious use of SetThreadContext 2 IoCs
description pid Process procid_target PID 4796 set thread context of 368 4796 9a113fb097c1cee87961a2ecc9d83b583d5bb7c568fd6b4356f4dad9c0540c89.exe 83 PID 368 set thread context of 1888 368 9a113fb097c1cee87961a2ecc9d83b583d5bb7c568fd6b4356f4dad9c0540c89.exe 84 -
Suspicious behavior: EnumeratesProcesses 4 IoCs
pid Process 1888 9a113fb097c1cee87961a2ecc9d83b583d5bb7c568fd6b4356f4dad9c0540c89.exe 1888 9a113fb097c1cee87961a2ecc9d83b583d5bb7c568fd6b4356f4dad9c0540c89.exe 1888 9a113fb097c1cee87961a2ecc9d83b583d5bb7c568fd6b4356f4dad9c0540c89.exe 1888 9a113fb097c1cee87961a2ecc9d83b583d5bb7c568fd6b4356f4dad9c0540c89.exe -
Suspicious use of SetWindowsHookEx 2 IoCs
pid Process 4796 9a113fb097c1cee87961a2ecc9d83b583d5bb7c568fd6b4356f4dad9c0540c89.exe 368 9a113fb097c1cee87961a2ecc9d83b583d5bb7c568fd6b4356f4dad9c0540c89.exe -
Suspicious use of WriteProcessMemory 19 IoCs
description pid Process procid_target PID 4796 wrote to memory of 368 4796 9a113fb097c1cee87961a2ecc9d83b583d5bb7c568fd6b4356f4dad9c0540c89.exe 83 PID 4796 wrote to memory of 368 4796 9a113fb097c1cee87961a2ecc9d83b583d5bb7c568fd6b4356f4dad9c0540c89.exe 83 PID 4796 wrote to memory of 368 4796 9a113fb097c1cee87961a2ecc9d83b583d5bb7c568fd6b4356f4dad9c0540c89.exe 83 PID 4796 wrote to memory of 368 4796 9a113fb097c1cee87961a2ecc9d83b583d5bb7c568fd6b4356f4dad9c0540c89.exe 83 PID 4796 wrote to memory of 368 4796 9a113fb097c1cee87961a2ecc9d83b583d5bb7c568fd6b4356f4dad9c0540c89.exe 83 PID 4796 wrote to memory of 368 4796 9a113fb097c1cee87961a2ecc9d83b583d5bb7c568fd6b4356f4dad9c0540c89.exe 83 PID 4796 wrote to memory of 368 4796 9a113fb097c1cee87961a2ecc9d83b583d5bb7c568fd6b4356f4dad9c0540c89.exe 83 PID 4796 wrote to memory of 368 4796 9a113fb097c1cee87961a2ecc9d83b583d5bb7c568fd6b4356f4dad9c0540c89.exe 83 PID 368 wrote to memory of 1888 368 9a113fb097c1cee87961a2ecc9d83b583d5bb7c568fd6b4356f4dad9c0540c89.exe 84 PID 368 wrote to memory of 1888 368 9a113fb097c1cee87961a2ecc9d83b583d5bb7c568fd6b4356f4dad9c0540c89.exe 84 PID 368 wrote to memory of 1888 368 9a113fb097c1cee87961a2ecc9d83b583d5bb7c568fd6b4356f4dad9c0540c89.exe 84 PID 368 wrote to memory of 1888 368 9a113fb097c1cee87961a2ecc9d83b583d5bb7c568fd6b4356f4dad9c0540c89.exe 84 PID 368 wrote to memory of 1888 368 9a113fb097c1cee87961a2ecc9d83b583d5bb7c568fd6b4356f4dad9c0540c89.exe 84 PID 368 wrote to memory of 1888 368 9a113fb097c1cee87961a2ecc9d83b583d5bb7c568fd6b4356f4dad9c0540c89.exe 84 PID 368 wrote to memory of 1888 368 9a113fb097c1cee87961a2ecc9d83b583d5bb7c568fd6b4356f4dad9c0540c89.exe 84 PID 1888 wrote to memory of 2184 1888 9a113fb097c1cee87961a2ecc9d83b583d5bb7c568fd6b4356f4dad9c0540c89.exe 44 PID 1888 wrote to memory of 2184 1888 9a113fb097c1cee87961a2ecc9d83b583d5bb7c568fd6b4356f4dad9c0540c89.exe 44 PID 1888 wrote to memory of 2184 1888 9a113fb097c1cee87961a2ecc9d83b583d5bb7c568fd6b4356f4dad9c0540c89.exe 44 PID 1888 wrote to memory of 2184 1888 9a113fb097c1cee87961a2ecc9d83b583d5bb7c568fd6b4356f4dad9c0540c89.exe 44
Processes
-
C:\Windows\Explorer.EXEC:\Windows\Explorer.EXE1⤵PID:2184
-
C:\Users\Admin\AppData\Local\Temp\9a113fb097c1cee87961a2ecc9d83b583d5bb7c568fd6b4356f4dad9c0540c89.exe"C:\Users\Admin\AppData\Local\Temp\9a113fb097c1cee87961a2ecc9d83b583d5bb7c568fd6b4356f4dad9c0540c89.exe"2⤵
- Suspicious use of SetThreadContext
- Suspicious use of SetWindowsHookEx
- Suspicious use of WriteProcessMemory
PID:4796 -
C:\Users\Admin\AppData\Local\Temp\9a113fb097c1cee87961a2ecc9d83b583d5bb7c568fd6b4356f4dad9c0540c89.exeC:\Users\Admin\AppData\Local\Temp\9a113fb097c1cee87961a2ecc9d83b583d5bb7c568fd6b4356f4dad9c0540c89.exe3⤵
- Suspicious use of SetThreadContext
- Suspicious use of SetWindowsHookEx
- Suspicious use of WriteProcessMemory
PID:368 -
C:\Users\Admin\AppData\Local\Temp\9a113fb097c1cee87961a2ecc9d83b583d5bb7c568fd6b4356f4dad9c0540c89.exeC:\Users\Admin\AppData\Local\Temp\9a113fb097c1cee87961a2ecc9d83b583d5bb7c568fd6b4356f4dad9c0540c89.exe4⤵
- Suspicious behavior: EnumeratesProcesses
- Suspicious use of WriteProcessMemory
PID:1888
-
-
-