Analysis
-
max time kernel
93s -
max time network
96s -
platform
windows10-2004_x64 -
resource
win10v2004-20241007-en -
resource tags
arch:x64arch:x86image:win10v2004-20241007-enlocale:en-usos:windows10-2004-x64system -
submitted
11-11-2024 01:01
Behavioral task
behavioral1
Sample
17feb12c1d7accb3247122aee35d0f6f1ff23b25f25d6ca0ec04d6dd83f6e734N.exe
Resource
win7-20240903-en
Behavioral task
behavioral2
Sample
17feb12c1d7accb3247122aee35d0f6f1ff23b25f25d6ca0ec04d6dd83f6e734N.exe
Resource
win10v2004-20241007-en
General
-
Target
17feb12c1d7accb3247122aee35d0f6f1ff23b25f25d6ca0ec04d6dd83f6e734N.exe
-
Size
2.9MB
-
MD5
8ff70aa964233c81b0a65ffa807f9821
-
SHA1
9074172a199ad08e655486cd713122d965d252f4
-
SHA256
0346782816f3eded04422abb5d2f58d16c92ceb422b5cfdaf00d21508f6c6ca5
-
SHA512
d55620c1e55be3cfa2aa94651cfb549713ed01904f3b04260049d4274f8ee8497d67bd5f2acb34ab580a183e394486477aad3994a83cf88f4586c6bf9af9f01b
-
SSDEEP
24576:eTy7ASmZZcVKfIxTiEVc847flVC6faaQDbGV6eH81k6IbGD2JTu0GoZQDbGV6eHB:eTy7ASmw4gxeOw46fUbNecCCFbNecU
Malware Config
Signatures
-
Drops startup file 1 IoCs
Processes:
cmd.exedescription ioc process File created C:\Users\Admin\AppData\Roaming\Microsoft\Windows\Start Menu\Programs\Startup\x.vbs cmd.exe -
Adds Run key to start application 2 TTPs 1 IoCs
Processes:
17feb12c1d7accb3247122aee35d0f6f1ff23b25f25d6ca0ec04d6dd83f6e734N.exedescription ioc process Set value (str) \REGISTRY\USER\S-1-5-21-3350944739-639801879-157714471-1000\SOFTWARE\Microsoft\Windows\CurrentVersion\Run\Microsoft OneDrive = "C:\\Users\\Admin\\AppData\\Local\\Chrome\\StikyNot.exe" 17feb12c1d7accb3247122aee35d0f6f1ff23b25f25d6ca0ec04d6dd83f6e734N.exe -
Suspicious use of SetThreadContext 3 IoCs
Processes:
17feb12c1d7accb3247122aee35d0f6f1ff23b25f25d6ca0ec04d6dd83f6e734N.exe17feb12c1d7accb3247122aee35d0f6f1ff23b25f25d6ca0ec04d6dd83f6e734N.exedescription pid process target process PID 2160 set thread context of 4904 2160 17feb12c1d7accb3247122aee35d0f6f1ff23b25f25d6ca0ec04d6dd83f6e734N.exe 17feb12c1d7accb3247122aee35d0f6f1ff23b25f25d6ca0ec04d6dd83f6e734N.exe PID 4904 set thread context of 2640 4904 17feb12c1d7accb3247122aee35d0f6f1ff23b25f25d6ca0ec04d6dd83f6e734N.exe 17feb12c1d7accb3247122aee35d0f6f1ff23b25f25d6ca0ec04d6dd83f6e734N.exe PID 4904 set thread context of 3920 4904 17feb12c1d7accb3247122aee35d0f6f1ff23b25f25d6ca0ec04d6dd83f6e734N.exe diskperf.exe -
Enumerates physical storage devices 1 TTPs
Attempts to interact with connected storage/optical drive(s).
-
System Location Discovery: System Language Discovery 1 TTPs 4 IoCs
Attempt gather information about the system language of a victim in order to infer the geographical location of that host.
Processes:
17feb12c1d7accb3247122aee35d0f6f1ff23b25f25d6ca0ec04d6dd83f6e734N.execmd.exe17feb12c1d7accb3247122aee35d0f6f1ff23b25f25d6ca0ec04d6dd83f6e734N.exe17feb12c1d7accb3247122aee35d0f6f1ff23b25f25d6ca0ec04d6dd83f6e734N.exedescription ioc process Key opened \REGISTRY\MACHINE\SYSTEM\ControlSet001\Control\NLS\Language 17feb12c1d7accb3247122aee35d0f6f1ff23b25f25d6ca0ec04d6dd83f6e734N.exe Key opened \REGISTRY\MACHINE\SYSTEM\ControlSet001\Control\NLS\Language cmd.exe Key opened \REGISTRY\MACHINE\SYSTEM\ControlSet001\Control\NLS\Language 17feb12c1d7accb3247122aee35d0f6f1ff23b25f25d6ca0ec04d6dd83f6e734N.exe Key opened \REGISTRY\MACHINE\SYSTEM\ControlSet001\Control\NLS\Language 17feb12c1d7accb3247122aee35d0f6f1ff23b25f25d6ca0ec04d6dd83f6e734N.exe -
Suspicious behavior: EnumeratesProcesses 2 IoCs
Processes:
17feb12c1d7accb3247122aee35d0f6f1ff23b25f25d6ca0ec04d6dd83f6e734N.exepid process 2160 17feb12c1d7accb3247122aee35d0f6f1ff23b25f25d6ca0ec04d6dd83f6e734N.exe 2160 17feb12c1d7accb3247122aee35d0f6f1ff23b25f25d6ca0ec04d6dd83f6e734N.exe -
Suspicious use of SetWindowsHookEx 4 IoCs
Processes:
17feb12c1d7accb3247122aee35d0f6f1ff23b25f25d6ca0ec04d6dd83f6e734N.exe17feb12c1d7accb3247122aee35d0f6f1ff23b25f25d6ca0ec04d6dd83f6e734N.exepid process 2160 17feb12c1d7accb3247122aee35d0f6f1ff23b25f25d6ca0ec04d6dd83f6e734N.exe 2160 17feb12c1d7accb3247122aee35d0f6f1ff23b25f25d6ca0ec04d6dd83f6e734N.exe 2640 17feb12c1d7accb3247122aee35d0f6f1ff23b25f25d6ca0ec04d6dd83f6e734N.exe 2640 17feb12c1d7accb3247122aee35d0f6f1ff23b25f25d6ca0ec04d6dd83f6e734N.exe -
Suspicious use of WriteProcessMemory 45 IoCs
Processes:
17feb12c1d7accb3247122aee35d0f6f1ff23b25f25d6ca0ec04d6dd83f6e734N.exe17feb12c1d7accb3247122aee35d0f6f1ff23b25f25d6ca0ec04d6dd83f6e734N.exedescription pid process target process PID 2160 wrote to memory of 2944 2160 17feb12c1d7accb3247122aee35d0f6f1ff23b25f25d6ca0ec04d6dd83f6e734N.exe cmd.exe PID 2160 wrote to memory of 2944 2160 17feb12c1d7accb3247122aee35d0f6f1ff23b25f25d6ca0ec04d6dd83f6e734N.exe cmd.exe PID 2160 wrote to memory of 2944 2160 17feb12c1d7accb3247122aee35d0f6f1ff23b25f25d6ca0ec04d6dd83f6e734N.exe cmd.exe PID 2160 wrote to memory of 4904 2160 17feb12c1d7accb3247122aee35d0f6f1ff23b25f25d6ca0ec04d6dd83f6e734N.exe 17feb12c1d7accb3247122aee35d0f6f1ff23b25f25d6ca0ec04d6dd83f6e734N.exe PID 2160 wrote to memory of 4904 2160 17feb12c1d7accb3247122aee35d0f6f1ff23b25f25d6ca0ec04d6dd83f6e734N.exe 17feb12c1d7accb3247122aee35d0f6f1ff23b25f25d6ca0ec04d6dd83f6e734N.exe PID 2160 wrote to memory of 4904 2160 17feb12c1d7accb3247122aee35d0f6f1ff23b25f25d6ca0ec04d6dd83f6e734N.exe 17feb12c1d7accb3247122aee35d0f6f1ff23b25f25d6ca0ec04d6dd83f6e734N.exe PID 2160 wrote to memory of 4904 2160 17feb12c1d7accb3247122aee35d0f6f1ff23b25f25d6ca0ec04d6dd83f6e734N.exe 17feb12c1d7accb3247122aee35d0f6f1ff23b25f25d6ca0ec04d6dd83f6e734N.exe PID 2160 wrote to memory of 4904 2160 17feb12c1d7accb3247122aee35d0f6f1ff23b25f25d6ca0ec04d6dd83f6e734N.exe 17feb12c1d7accb3247122aee35d0f6f1ff23b25f25d6ca0ec04d6dd83f6e734N.exe PID 2160 wrote to memory of 4904 2160 17feb12c1d7accb3247122aee35d0f6f1ff23b25f25d6ca0ec04d6dd83f6e734N.exe 17feb12c1d7accb3247122aee35d0f6f1ff23b25f25d6ca0ec04d6dd83f6e734N.exe PID 2160 wrote to memory of 4904 2160 17feb12c1d7accb3247122aee35d0f6f1ff23b25f25d6ca0ec04d6dd83f6e734N.exe 17feb12c1d7accb3247122aee35d0f6f1ff23b25f25d6ca0ec04d6dd83f6e734N.exe PID 2160 wrote to memory of 4904 2160 17feb12c1d7accb3247122aee35d0f6f1ff23b25f25d6ca0ec04d6dd83f6e734N.exe 17feb12c1d7accb3247122aee35d0f6f1ff23b25f25d6ca0ec04d6dd83f6e734N.exe PID 2160 wrote to memory of 4904 2160 17feb12c1d7accb3247122aee35d0f6f1ff23b25f25d6ca0ec04d6dd83f6e734N.exe 17feb12c1d7accb3247122aee35d0f6f1ff23b25f25d6ca0ec04d6dd83f6e734N.exe PID 2160 wrote to memory of 4904 2160 17feb12c1d7accb3247122aee35d0f6f1ff23b25f25d6ca0ec04d6dd83f6e734N.exe 17feb12c1d7accb3247122aee35d0f6f1ff23b25f25d6ca0ec04d6dd83f6e734N.exe PID 2160 wrote to memory of 4904 2160 17feb12c1d7accb3247122aee35d0f6f1ff23b25f25d6ca0ec04d6dd83f6e734N.exe 17feb12c1d7accb3247122aee35d0f6f1ff23b25f25d6ca0ec04d6dd83f6e734N.exe PID 2160 wrote to memory of 4904 2160 17feb12c1d7accb3247122aee35d0f6f1ff23b25f25d6ca0ec04d6dd83f6e734N.exe 17feb12c1d7accb3247122aee35d0f6f1ff23b25f25d6ca0ec04d6dd83f6e734N.exe PID 2160 wrote to memory of 4904 2160 17feb12c1d7accb3247122aee35d0f6f1ff23b25f25d6ca0ec04d6dd83f6e734N.exe 17feb12c1d7accb3247122aee35d0f6f1ff23b25f25d6ca0ec04d6dd83f6e734N.exe PID 2160 wrote to memory of 4904 2160 17feb12c1d7accb3247122aee35d0f6f1ff23b25f25d6ca0ec04d6dd83f6e734N.exe 17feb12c1d7accb3247122aee35d0f6f1ff23b25f25d6ca0ec04d6dd83f6e734N.exe PID 2160 wrote to memory of 4904 2160 17feb12c1d7accb3247122aee35d0f6f1ff23b25f25d6ca0ec04d6dd83f6e734N.exe 17feb12c1d7accb3247122aee35d0f6f1ff23b25f25d6ca0ec04d6dd83f6e734N.exe PID 2160 wrote to memory of 4904 2160 17feb12c1d7accb3247122aee35d0f6f1ff23b25f25d6ca0ec04d6dd83f6e734N.exe 17feb12c1d7accb3247122aee35d0f6f1ff23b25f25d6ca0ec04d6dd83f6e734N.exe PID 2160 wrote to memory of 4904 2160 17feb12c1d7accb3247122aee35d0f6f1ff23b25f25d6ca0ec04d6dd83f6e734N.exe 17feb12c1d7accb3247122aee35d0f6f1ff23b25f25d6ca0ec04d6dd83f6e734N.exe PID 2160 wrote to memory of 4904 2160 17feb12c1d7accb3247122aee35d0f6f1ff23b25f25d6ca0ec04d6dd83f6e734N.exe 17feb12c1d7accb3247122aee35d0f6f1ff23b25f25d6ca0ec04d6dd83f6e734N.exe PID 2160 wrote to memory of 4904 2160 17feb12c1d7accb3247122aee35d0f6f1ff23b25f25d6ca0ec04d6dd83f6e734N.exe 17feb12c1d7accb3247122aee35d0f6f1ff23b25f25d6ca0ec04d6dd83f6e734N.exe PID 2160 wrote to memory of 4904 2160 17feb12c1d7accb3247122aee35d0f6f1ff23b25f25d6ca0ec04d6dd83f6e734N.exe 17feb12c1d7accb3247122aee35d0f6f1ff23b25f25d6ca0ec04d6dd83f6e734N.exe PID 2160 wrote to memory of 4904 2160 17feb12c1d7accb3247122aee35d0f6f1ff23b25f25d6ca0ec04d6dd83f6e734N.exe 17feb12c1d7accb3247122aee35d0f6f1ff23b25f25d6ca0ec04d6dd83f6e734N.exe PID 2160 wrote to memory of 4904 2160 17feb12c1d7accb3247122aee35d0f6f1ff23b25f25d6ca0ec04d6dd83f6e734N.exe 17feb12c1d7accb3247122aee35d0f6f1ff23b25f25d6ca0ec04d6dd83f6e734N.exe PID 2160 wrote to memory of 4904 2160 17feb12c1d7accb3247122aee35d0f6f1ff23b25f25d6ca0ec04d6dd83f6e734N.exe 17feb12c1d7accb3247122aee35d0f6f1ff23b25f25d6ca0ec04d6dd83f6e734N.exe PID 2160 wrote to memory of 4904 2160 17feb12c1d7accb3247122aee35d0f6f1ff23b25f25d6ca0ec04d6dd83f6e734N.exe 17feb12c1d7accb3247122aee35d0f6f1ff23b25f25d6ca0ec04d6dd83f6e734N.exe PID 2160 wrote to memory of 4904 2160 17feb12c1d7accb3247122aee35d0f6f1ff23b25f25d6ca0ec04d6dd83f6e734N.exe 17feb12c1d7accb3247122aee35d0f6f1ff23b25f25d6ca0ec04d6dd83f6e734N.exe PID 2160 wrote to memory of 4904 2160 17feb12c1d7accb3247122aee35d0f6f1ff23b25f25d6ca0ec04d6dd83f6e734N.exe 17feb12c1d7accb3247122aee35d0f6f1ff23b25f25d6ca0ec04d6dd83f6e734N.exe PID 2160 wrote to memory of 4904 2160 17feb12c1d7accb3247122aee35d0f6f1ff23b25f25d6ca0ec04d6dd83f6e734N.exe 17feb12c1d7accb3247122aee35d0f6f1ff23b25f25d6ca0ec04d6dd83f6e734N.exe PID 2160 wrote to memory of 4904 2160 17feb12c1d7accb3247122aee35d0f6f1ff23b25f25d6ca0ec04d6dd83f6e734N.exe 17feb12c1d7accb3247122aee35d0f6f1ff23b25f25d6ca0ec04d6dd83f6e734N.exe PID 2160 wrote to memory of 4904 2160 17feb12c1d7accb3247122aee35d0f6f1ff23b25f25d6ca0ec04d6dd83f6e734N.exe 17feb12c1d7accb3247122aee35d0f6f1ff23b25f25d6ca0ec04d6dd83f6e734N.exe PID 4904 wrote to memory of 2640 4904 17feb12c1d7accb3247122aee35d0f6f1ff23b25f25d6ca0ec04d6dd83f6e734N.exe 17feb12c1d7accb3247122aee35d0f6f1ff23b25f25d6ca0ec04d6dd83f6e734N.exe PID 4904 wrote to memory of 2640 4904 17feb12c1d7accb3247122aee35d0f6f1ff23b25f25d6ca0ec04d6dd83f6e734N.exe 17feb12c1d7accb3247122aee35d0f6f1ff23b25f25d6ca0ec04d6dd83f6e734N.exe PID 4904 wrote to memory of 2640 4904 17feb12c1d7accb3247122aee35d0f6f1ff23b25f25d6ca0ec04d6dd83f6e734N.exe 17feb12c1d7accb3247122aee35d0f6f1ff23b25f25d6ca0ec04d6dd83f6e734N.exe PID 4904 wrote to memory of 2640 4904 17feb12c1d7accb3247122aee35d0f6f1ff23b25f25d6ca0ec04d6dd83f6e734N.exe 17feb12c1d7accb3247122aee35d0f6f1ff23b25f25d6ca0ec04d6dd83f6e734N.exe PID 4904 wrote to memory of 2640 4904 17feb12c1d7accb3247122aee35d0f6f1ff23b25f25d6ca0ec04d6dd83f6e734N.exe 17feb12c1d7accb3247122aee35d0f6f1ff23b25f25d6ca0ec04d6dd83f6e734N.exe PID 4904 wrote to memory of 2640 4904 17feb12c1d7accb3247122aee35d0f6f1ff23b25f25d6ca0ec04d6dd83f6e734N.exe 17feb12c1d7accb3247122aee35d0f6f1ff23b25f25d6ca0ec04d6dd83f6e734N.exe PID 4904 wrote to memory of 2640 4904 17feb12c1d7accb3247122aee35d0f6f1ff23b25f25d6ca0ec04d6dd83f6e734N.exe 17feb12c1d7accb3247122aee35d0f6f1ff23b25f25d6ca0ec04d6dd83f6e734N.exe PID 4904 wrote to memory of 2640 4904 17feb12c1d7accb3247122aee35d0f6f1ff23b25f25d6ca0ec04d6dd83f6e734N.exe 17feb12c1d7accb3247122aee35d0f6f1ff23b25f25d6ca0ec04d6dd83f6e734N.exe PID 4904 wrote to memory of 3920 4904 17feb12c1d7accb3247122aee35d0f6f1ff23b25f25d6ca0ec04d6dd83f6e734N.exe diskperf.exe PID 4904 wrote to memory of 3920 4904 17feb12c1d7accb3247122aee35d0f6f1ff23b25f25d6ca0ec04d6dd83f6e734N.exe diskperf.exe PID 4904 wrote to memory of 3920 4904 17feb12c1d7accb3247122aee35d0f6f1ff23b25f25d6ca0ec04d6dd83f6e734N.exe diskperf.exe PID 4904 wrote to memory of 3920 4904 17feb12c1d7accb3247122aee35d0f6f1ff23b25f25d6ca0ec04d6dd83f6e734N.exe diskperf.exe PID 4904 wrote to memory of 3920 4904 17feb12c1d7accb3247122aee35d0f6f1ff23b25f25d6ca0ec04d6dd83f6e734N.exe diskperf.exe
Processes
-
C:\Users\Admin\AppData\Local\Temp\17feb12c1d7accb3247122aee35d0f6f1ff23b25f25d6ca0ec04d6dd83f6e734N.exe"C:\Users\Admin\AppData\Local\Temp\17feb12c1d7accb3247122aee35d0f6f1ff23b25f25d6ca0ec04d6dd83f6e734N.exe"1⤵
- Suspicious use of SetThreadContext
- System Location Discovery: System Language Discovery
- Suspicious behavior: EnumeratesProcesses
- Suspicious use of SetWindowsHookEx
- Suspicious use of WriteProcessMemory
PID:2160 -
C:\Windows\SysWOW64\cmd.exeC:\Windows\system32\cmd.exe /c echo on error resume next:CreateObject("WScript.Shell").Run "C:\Users\Admin\AppData\Local\Temp\17feb12c1d7accb3247122aee35d0f6f1ff23b25f25d6ca0ec04d6dd83f6e734N.exe",1: >"C:\Users\Admin\AppData\Roaming\Microsoft\Windows\Start Menu\Programs\Startup\x.vbs"2⤵
- Drops startup file
- System Location Discovery: System Language Discovery
PID:2944
-
-
C:\Users\Admin\AppData\Local\Temp\17feb12c1d7accb3247122aee35d0f6f1ff23b25f25d6ca0ec04d6dd83f6e734N.exeC:\Users\Admin\AppData\Local\Temp\17feb12c1d7accb3247122aee35d0f6f1ff23b25f25d6ca0ec04d6dd83f6e734N.exe2⤵
- Adds Run key to start application
- Suspicious use of SetThreadContext
- System Location Discovery: System Language Discovery
- Suspicious use of WriteProcessMemory
PID:4904 -
C:\Users\Admin\AppData\Local\Temp\17feb12c1d7accb3247122aee35d0f6f1ff23b25f25d6ca0ec04d6dd83f6e734N.exeC:\Users\Admin\AppData\Local\Temp\17feb12c1d7accb3247122aee35d0f6f1ff23b25f25d6ca0ec04d6dd83f6e734N.exe3⤵
- System Location Discovery: System Language Discovery
- Suspicious use of SetWindowsHookEx
PID:2640
-
-
C:\Windows\SysWOW64\diskperf.exe"C:\Windows\SysWOW64\diskperf.exe"3⤵PID:3920
-
-