Analysis
-
max time kernel
175s -
max time network
194s -
platform
windows10-2004_x64 -
resource
win10v2004-20221111-en -
resource tags
arch:x64arch:x86image:win10v2004-20221111-enlocale:en-usos:windows10-2004-x64system -
submitted
04/12/2022, 08:10
Static task
static1
Behavioral task
behavioral1
Sample
f38873237c1e2d963c7ba8444d52501722f92fa31486cb6b71bcf9a670961095.exe
Resource
win7-20221111-en
Behavioral task
behavioral2
Sample
f38873237c1e2d963c7ba8444d52501722f92fa31486cb6b71bcf9a670961095.exe
Resource
win10v2004-20221111-en
General
-
Target
f38873237c1e2d963c7ba8444d52501722f92fa31486cb6b71bcf9a670961095.exe
-
Size
276KB
-
MD5
125c4dbadc820e2e0178349702a7e2cf
-
SHA1
946841c3ae3dfff69b32192230361de6c6eb0a12
-
SHA256
f38873237c1e2d963c7ba8444d52501722f92fa31486cb6b71bcf9a670961095
-
SHA512
d1953eb6cc276303f056d15488b06ccef73da632d3619802538c9f650bdf3f43fbe6f1c531ee92a8a68944673fe1701e75f336891f2e121228c49cdf0a77efa9
-
SSDEEP
6144:bqY9SC2DqBRhVh8njm9VCwH+ep7Ld7GsAtIOPEBejLhe8:WYMusnjmLjbisgkqLt
Malware Config
Signatures
-
Suspicious use of SetThreadContext 1 IoCs
description pid Process procid_target PID 4088 set thread context of 1836 4088 f38873237c1e2d963c7ba8444d52501722f92fa31486cb6b71bcf9a670961095.exe 81 -
Suspicious behavior: EnumeratesProcesses 4 IoCs
pid Process 1836 f38873237c1e2d963c7ba8444d52501722f92fa31486cb6b71bcf9a670961095.exe 1836 f38873237c1e2d963c7ba8444d52501722f92fa31486cb6b71bcf9a670961095.exe 1836 f38873237c1e2d963c7ba8444d52501722f92fa31486cb6b71bcf9a670961095.exe 1836 f38873237c1e2d963c7ba8444d52501722f92fa31486cb6b71bcf9a670961095.exe -
Suspicious use of SetWindowsHookEx 1 IoCs
pid Process 4088 f38873237c1e2d963c7ba8444d52501722f92fa31486cb6b71bcf9a670961095.exe -
Suspicious use of WriteProcessMemory 13 IoCs
description pid Process procid_target PID 4088 wrote to memory of 1836 4088 f38873237c1e2d963c7ba8444d52501722f92fa31486cb6b71bcf9a670961095.exe 81 PID 4088 wrote to memory of 1836 4088 f38873237c1e2d963c7ba8444d52501722f92fa31486cb6b71bcf9a670961095.exe 81 PID 4088 wrote to memory of 1836 4088 f38873237c1e2d963c7ba8444d52501722f92fa31486cb6b71bcf9a670961095.exe 81 PID 4088 wrote to memory of 1836 4088 f38873237c1e2d963c7ba8444d52501722f92fa31486cb6b71bcf9a670961095.exe 81 PID 4088 wrote to memory of 1836 4088 f38873237c1e2d963c7ba8444d52501722f92fa31486cb6b71bcf9a670961095.exe 81 PID 4088 wrote to memory of 1836 4088 f38873237c1e2d963c7ba8444d52501722f92fa31486cb6b71bcf9a670961095.exe 81 PID 4088 wrote to memory of 1836 4088 f38873237c1e2d963c7ba8444d52501722f92fa31486cb6b71bcf9a670961095.exe 81 PID 1836 wrote to memory of 2708 1836 f38873237c1e2d963c7ba8444d52501722f92fa31486cb6b71bcf9a670961095.exe 54 PID 1836 wrote to memory of 2708 1836 f38873237c1e2d963c7ba8444d52501722f92fa31486cb6b71bcf9a670961095.exe 54 PID 1836 wrote to memory of 2708 1836 f38873237c1e2d963c7ba8444d52501722f92fa31486cb6b71bcf9a670961095.exe 54 PID 1836 wrote to memory of 2708 1836 f38873237c1e2d963c7ba8444d52501722f92fa31486cb6b71bcf9a670961095.exe 54 PID 1836 wrote to memory of 2708 1836 f38873237c1e2d963c7ba8444d52501722f92fa31486cb6b71bcf9a670961095.exe 54 PID 1836 wrote to memory of 2708 1836 f38873237c1e2d963c7ba8444d52501722f92fa31486cb6b71bcf9a670961095.exe 54
Processes
-
C:\Windows\Explorer.EXEC:\Windows\Explorer.EXE1⤵PID:2708
-
C:\Users\Admin\AppData\Local\Temp\f38873237c1e2d963c7ba8444d52501722f92fa31486cb6b71bcf9a670961095.exe"C:\Users\Admin\AppData\Local\Temp\f38873237c1e2d963c7ba8444d52501722f92fa31486cb6b71bcf9a670961095.exe"2⤵
- Suspicious use of SetThreadContext
- Suspicious use of SetWindowsHookEx
- Suspicious use of WriteProcessMemory
PID:4088 -
C:\Users\Admin\AppData\Local\Temp\f38873237c1e2d963c7ba8444d52501722f92fa31486cb6b71bcf9a670961095.exeC:\Users\Admin\AppData\Local\Temp\f38873237c1e2d963c7ba8444d52501722f92fa31486cb6b71bcf9a670961095.exe3⤵
- Suspicious behavior: EnumeratesProcesses
- Suspicious use of WriteProcessMemory
PID:1836
-
-