Analysis
-
max time kernel
0s -
max time network
147s -
platform
windows7_x64 -
resource
win7-20231215-en -
resource tags
arch:x64arch:x86image:win7-20231215-enlocale:en-usos:windows7-x64system -
submitted
05/01/2024, 04:20
Static task
static1
Behavioral task
behavioral1
Sample
53b029acaf56b1b9184157408958a7e995bf41c98d60879e8f889e479f4f24be.exe
Resource
win7-20231215-en
Behavioral task
behavioral2
Sample
53b029acaf56b1b9184157408958a7e995bf41c98d60879e8f889e479f4f24be.exe
Resource
win10v2004-20231222-en
General
-
Target
53b029acaf56b1b9184157408958a7e995bf41c98d60879e8f889e479f4f24be.exe
-
Size
201KB
-
MD5
e98ba95efa3e03567ec95964bdec5cae
-
SHA1
dc8f23eacfd365a2e76ec11847617696d3b1f46e
-
SHA256
53b029acaf56b1b9184157408958a7e995bf41c98d60879e8f889e479f4f24be
-
SHA512
11ec9a630086aaffb064accff6622d354a26dea29e6418c7ee61628aa08c1babfca32fb1e959e21aefb7cd5216871bc60d0f792c28f769e5d4a3acf7c6d19b0d
-
SSDEEP
3072:fP5gvNVLIfHQja1RfmLQADwSKkhU+tLgT5lODbiC8r1PkT:X2vnSwjaOcADw9cUeCOf
Malware Config
Signatures
-
Runs ping.exe 1 TTPs 1 IoCs
pid Process 2684 PING.EXE -
Suspicious use of SetWindowsHookEx 1 IoCs
pid Process 2108 53b029acaf56b1b9184157408958a7e995bf41c98d60879e8f889e479f4f24be.exe -
Suspicious use of WriteProcessMemory 8 IoCs
description pid Process procid_target PID 2108 wrote to memory of 3064 2108 53b029acaf56b1b9184157408958a7e995bf41c98d60879e8f889e479f4f24be.exe 21 PID 2108 wrote to memory of 3064 2108 53b029acaf56b1b9184157408958a7e995bf41c98d60879e8f889e479f4f24be.exe 21 PID 2108 wrote to memory of 3064 2108 53b029acaf56b1b9184157408958a7e995bf41c98d60879e8f889e479f4f24be.exe 21 PID 2108 wrote to memory of 3064 2108 53b029acaf56b1b9184157408958a7e995bf41c98d60879e8f889e479f4f24be.exe 21 PID 3064 wrote to memory of 2684 3064 cmd.exe 19 PID 3064 wrote to memory of 2684 3064 cmd.exe 19 PID 3064 wrote to memory of 2684 3064 cmd.exe 19 PID 3064 wrote to memory of 2684 3064 cmd.exe 19
Processes
-
C:\Users\Admin\AppData\Local\Temp\53b029acaf56b1b9184157408958a7e995bf41c98d60879e8f889e479f4f24be.exe"C:\Users\Admin\AppData\Local\Temp\53b029acaf56b1b9184157408958a7e995bf41c98d60879e8f889e479f4f24be.exe"1⤵
- Suspicious use of SetWindowsHookEx
- Suspicious use of WriteProcessMemory
PID:2108 -
C:\Windows\SysWOW64\cmd.execmd.exe /c ping 127.0.0.1 -n 2&C:\Users\Admin\AppData\Local\Temp\\ululkmiy.exe "C:\Users\Admin\AppData\Local\Temp\53b029acaf56b1b9184157408958a7e995bf41c98d60879e8f889e479f4f24be.exe"2⤵
- Suspicious use of WriteProcessMemory
PID:3064 -
C:\Users\Admin\AppData\Local\Temp\ululkmiy.exeC:\Users\Admin\AppData\Local\Temp\\ululkmiy.exe "C:\Users\Admin\AppData\Local\Temp\53b029acaf56b1b9184157408958a7e995bf41c98d60879e8f889e479f4f24be.exe"3⤵PID:2788
-
-
-
C:\Windows\SysWOW64\PING.EXEping 127.0.0.1 -n 21⤵
- Runs ping.exe
PID:2684
-
\??\c:\Program Files\wysxm\fxm.exe"c:\Program Files\wysxm\fxm.exe" "c:\Program Files\wysxm\fxmuh.dll",Compliance C:\Users\Admin\AppData\Local\Temp\ululkmiy.exe1⤵PID:2736