Analysis
-
max time kernel
94s -
max time network
95s -
platform
windows10-2004_x64 -
resource
win10v2004-20241007-en -
resource tags
arch:x64arch:x86image:win10v2004-20241007-enlocale:en-usos:windows10-2004-x64system -
submitted
10-11-2024 22:08
Behavioral task
behavioral1
Sample
96a8236dcc4bd2a392a82075f38327843610b5d86d2ef1095afcf8b461e58c39N.exe
Resource
win7-20240903-en
Behavioral task
behavioral2
Sample
96a8236dcc4bd2a392a82075f38327843610b5d86d2ef1095afcf8b461e58c39N.exe
Resource
win10v2004-20241007-en
General
-
Target
96a8236dcc4bd2a392a82075f38327843610b5d86d2ef1095afcf8b461e58c39N.exe
-
Size
2.9MB
-
MD5
ecc387942636a759bf75666c1affcbe9
-
SHA1
539668bf21a251da9fe843983ca3b69b224cd0ee
-
SHA256
6e1bf6e75eddea4d6b476fc1ebee4a27001e96ea431acc9673929dd6974f20a7
-
SHA512
92783e1ee9e6386f3c3f5fb99357d629baaeb9245c292caef58b8cc3de74c57c554aa4ac43fc48de5ed9691c9632514302447aba8ead7b619b0efdb6b37aaa87
-
SSDEEP
24576:7v97AXmZZcVKfIxTiEVc847flVC6faaQDbGV6eH81k6IbGD2JTu0GoZQDbGV6eH+:7v97AXmw4gxeOw46fUbNecCCFbNecB
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:
96a8236dcc4bd2a392a82075f38327843610b5d86d2ef1095afcf8b461e58c39N.exedescription ioc process Set value (str) \REGISTRY\USER\S-1-5-21-2045521122-590294423-3465680274-1000\SOFTWARE\Microsoft\Windows\CurrentVersion\Run\Microsoft OneDrive = "C:\\Users\\Admin\\AppData\\Local\\Chrome\\StikyNot.exe" 96a8236dcc4bd2a392a82075f38327843610b5d86d2ef1095afcf8b461e58c39N.exe -
Suspicious use of SetThreadContext 2 IoCs
Processes:
96a8236dcc4bd2a392a82075f38327843610b5d86d2ef1095afcf8b461e58c39N.exe96a8236dcc4bd2a392a82075f38327843610b5d86d2ef1095afcf8b461e58c39N.exedescription pid process target process PID 332 set thread context of 4052 332 96a8236dcc4bd2a392a82075f38327843610b5d86d2ef1095afcf8b461e58c39N.exe 96a8236dcc4bd2a392a82075f38327843610b5d86d2ef1095afcf8b461e58c39N.exe PID 4052 set thread context of 4976 4052 96a8236dcc4bd2a392a82075f38327843610b5d86d2ef1095afcf8b461e58c39N.exe 96a8236dcc4bd2a392a82075f38327843610b5d86d2ef1095afcf8b461e58c39N.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:
cmd.exe96a8236dcc4bd2a392a82075f38327843610b5d86d2ef1095afcf8b461e58c39N.exe96a8236dcc4bd2a392a82075f38327843610b5d86d2ef1095afcf8b461e58c39N.exe96a8236dcc4bd2a392a82075f38327843610b5d86d2ef1095afcf8b461e58c39N.exedescription ioc process Key opened \REGISTRY\MACHINE\SYSTEM\ControlSet001\Control\NLS\Language cmd.exe Key opened \REGISTRY\MACHINE\SYSTEM\ControlSet001\Control\NLS\Language 96a8236dcc4bd2a392a82075f38327843610b5d86d2ef1095afcf8b461e58c39N.exe Key opened \REGISTRY\MACHINE\SYSTEM\ControlSet001\Control\NLS\Language 96a8236dcc4bd2a392a82075f38327843610b5d86d2ef1095afcf8b461e58c39N.exe Key opened \REGISTRY\MACHINE\SYSTEM\ControlSet001\Control\NLS\Language 96a8236dcc4bd2a392a82075f38327843610b5d86d2ef1095afcf8b461e58c39N.exe -
Suspicious behavior: EnumeratesProcesses 2 IoCs
Processes:
96a8236dcc4bd2a392a82075f38327843610b5d86d2ef1095afcf8b461e58c39N.exepid process 332 96a8236dcc4bd2a392a82075f38327843610b5d86d2ef1095afcf8b461e58c39N.exe 332 96a8236dcc4bd2a392a82075f38327843610b5d86d2ef1095afcf8b461e58c39N.exe -
Suspicious use of SetWindowsHookEx 4 IoCs
Processes:
96a8236dcc4bd2a392a82075f38327843610b5d86d2ef1095afcf8b461e58c39N.exe96a8236dcc4bd2a392a82075f38327843610b5d86d2ef1095afcf8b461e58c39N.exepid process 332 96a8236dcc4bd2a392a82075f38327843610b5d86d2ef1095afcf8b461e58c39N.exe 332 96a8236dcc4bd2a392a82075f38327843610b5d86d2ef1095afcf8b461e58c39N.exe 4976 96a8236dcc4bd2a392a82075f38327843610b5d86d2ef1095afcf8b461e58c39N.exe 4976 96a8236dcc4bd2a392a82075f38327843610b5d86d2ef1095afcf8b461e58c39N.exe -
Suspicious use of WriteProcessMemory 43 IoCs
Processes:
96a8236dcc4bd2a392a82075f38327843610b5d86d2ef1095afcf8b461e58c39N.exe96a8236dcc4bd2a392a82075f38327843610b5d86d2ef1095afcf8b461e58c39N.exedescription pid process target process PID 332 wrote to memory of 4900 332 96a8236dcc4bd2a392a82075f38327843610b5d86d2ef1095afcf8b461e58c39N.exe cmd.exe PID 332 wrote to memory of 4900 332 96a8236dcc4bd2a392a82075f38327843610b5d86d2ef1095afcf8b461e58c39N.exe cmd.exe PID 332 wrote to memory of 4900 332 96a8236dcc4bd2a392a82075f38327843610b5d86d2ef1095afcf8b461e58c39N.exe cmd.exe PID 332 wrote to memory of 4052 332 96a8236dcc4bd2a392a82075f38327843610b5d86d2ef1095afcf8b461e58c39N.exe 96a8236dcc4bd2a392a82075f38327843610b5d86d2ef1095afcf8b461e58c39N.exe PID 332 wrote to memory of 4052 332 96a8236dcc4bd2a392a82075f38327843610b5d86d2ef1095afcf8b461e58c39N.exe 96a8236dcc4bd2a392a82075f38327843610b5d86d2ef1095afcf8b461e58c39N.exe PID 332 wrote to memory of 4052 332 96a8236dcc4bd2a392a82075f38327843610b5d86d2ef1095afcf8b461e58c39N.exe 96a8236dcc4bd2a392a82075f38327843610b5d86d2ef1095afcf8b461e58c39N.exe PID 332 wrote to memory of 4052 332 96a8236dcc4bd2a392a82075f38327843610b5d86d2ef1095afcf8b461e58c39N.exe 96a8236dcc4bd2a392a82075f38327843610b5d86d2ef1095afcf8b461e58c39N.exe PID 332 wrote to memory of 4052 332 96a8236dcc4bd2a392a82075f38327843610b5d86d2ef1095afcf8b461e58c39N.exe 96a8236dcc4bd2a392a82075f38327843610b5d86d2ef1095afcf8b461e58c39N.exe PID 332 wrote to memory of 4052 332 96a8236dcc4bd2a392a82075f38327843610b5d86d2ef1095afcf8b461e58c39N.exe 96a8236dcc4bd2a392a82075f38327843610b5d86d2ef1095afcf8b461e58c39N.exe PID 332 wrote to memory of 4052 332 96a8236dcc4bd2a392a82075f38327843610b5d86d2ef1095afcf8b461e58c39N.exe 96a8236dcc4bd2a392a82075f38327843610b5d86d2ef1095afcf8b461e58c39N.exe PID 332 wrote to memory of 4052 332 96a8236dcc4bd2a392a82075f38327843610b5d86d2ef1095afcf8b461e58c39N.exe 96a8236dcc4bd2a392a82075f38327843610b5d86d2ef1095afcf8b461e58c39N.exe PID 332 wrote to memory of 4052 332 96a8236dcc4bd2a392a82075f38327843610b5d86d2ef1095afcf8b461e58c39N.exe 96a8236dcc4bd2a392a82075f38327843610b5d86d2ef1095afcf8b461e58c39N.exe PID 332 wrote to memory of 4052 332 96a8236dcc4bd2a392a82075f38327843610b5d86d2ef1095afcf8b461e58c39N.exe 96a8236dcc4bd2a392a82075f38327843610b5d86d2ef1095afcf8b461e58c39N.exe PID 332 wrote to memory of 4052 332 96a8236dcc4bd2a392a82075f38327843610b5d86d2ef1095afcf8b461e58c39N.exe 96a8236dcc4bd2a392a82075f38327843610b5d86d2ef1095afcf8b461e58c39N.exe PID 332 wrote to memory of 4052 332 96a8236dcc4bd2a392a82075f38327843610b5d86d2ef1095afcf8b461e58c39N.exe 96a8236dcc4bd2a392a82075f38327843610b5d86d2ef1095afcf8b461e58c39N.exe PID 332 wrote to memory of 4052 332 96a8236dcc4bd2a392a82075f38327843610b5d86d2ef1095afcf8b461e58c39N.exe 96a8236dcc4bd2a392a82075f38327843610b5d86d2ef1095afcf8b461e58c39N.exe PID 332 wrote to memory of 4052 332 96a8236dcc4bd2a392a82075f38327843610b5d86d2ef1095afcf8b461e58c39N.exe 96a8236dcc4bd2a392a82075f38327843610b5d86d2ef1095afcf8b461e58c39N.exe PID 332 wrote to memory of 4052 332 96a8236dcc4bd2a392a82075f38327843610b5d86d2ef1095afcf8b461e58c39N.exe 96a8236dcc4bd2a392a82075f38327843610b5d86d2ef1095afcf8b461e58c39N.exe PID 332 wrote to memory of 4052 332 96a8236dcc4bd2a392a82075f38327843610b5d86d2ef1095afcf8b461e58c39N.exe 96a8236dcc4bd2a392a82075f38327843610b5d86d2ef1095afcf8b461e58c39N.exe PID 332 wrote to memory of 4052 332 96a8236dcc4bd2a392a82075f38327843610b5d86d2ef1095afcf8b461e58c39N.exe 96a8236dcc4bd2a392a82075f38327843610b5d86d2ef1095afcf8b461e58c39N.exe PID 332 wrote to memory of 4052 332 96a8236dcc4bd2a392a82075f38327843610b5d86d2ef1095afcf8b461e58c39N.exe 96a8236dcc4bd2a392a82075f38327843610b5d86d2ef1095afcf8b461e58c39N.exe PID 332 wrote to memory of 4052 332 96a8236dcc4bd2a392a82075f38327843610b5d86d2ef1095afcf8b461e58c39N.exe 96a8236dcc4bd2a392a82075f38327843610b5d86d2ef1095afcf8b461e58c39N.exe PID 332 wrote to memory of 4052 332 96a8236dcc4bd2a392a82075f38327843610b5d86d2ef1095afcf8b461e58c39N.exe 96a8236dcc4bd2a392a82075f38327843610b5d86d2ef1095afcf8b461e58c39N.exe PID 332 wrote to memory of 4052 332 96a8236dcc4bd2a392a82075f38327843610b5d86d2ef1095afcf8b461e58c39N.exe 96a8236dcc4bd2a392a82075f38327843610b5d86d2ef1095afcf8b461e58c39N.exe PID 332 wrote to memory of 4052 332 96a8236dcc4bd2a392a82075f38327843610b5d86d2ef1095afcf8b461e58c39N.exe 96a8236dcc4bd2a392a82075f38327843610b5d86d2ef1095afcf8b461e58c39N.exe PID 332 wrote to memory of 4052 332 96a8236dcc4bd2a392a82075f38327843610b5d86d2ef1095afcf8b461e58c39N.exe 96a8236dcc4bd2a392a82075f38327843610b5d86d2ef1095afcf8b461e58c39N.exe PID 332 wrote to memory of 4052 332 96a8236dcc4bd2a392a82075f38327843610b5d86d2ef1095afcf8b461e58c39N.exe 96a8236dcc4bd2a392a82075f38327843610b5d86d2ef1095afcf8b461e58c39N.exe PID 332 wrote to memory of 4052 332 96a8236dcc4bd2a392a82075f38327843610b5d86d2ef1095afcf8b461e58c39N.exe 96a8236dcc4bd2a392a82075f38327843610b5d86d2ef1095afcf8b461e58c39N.exe PID 332 wrote to memory of 4052 332 96a8236dcc4bd2a392a82075f38327843610b5d86d2ef1095afcf8b461e58c39N.exe 96a8236dcc4bd2a392a82075f38327843610b5d86d2ef1095afcf8b461e58c39N.exe PID 332 wrote to memory of 4052 332 96a8236dcc4bd2a392a82075f38327843610b5d86d2ef1095afcf8b461e58c39N.exe 96a8236dcc4bd2a392a82075f38327843610b5d86d2ef1095afcf8b461e58c39N.exe PID 332 wrote to memory of 4052 332 96a8236dcc4bd2a392a82075f38327843610b5d86d2ef1095afcf8b461e58c39N.exe 96a8236dcc4bd2a392a82075f38327843610b5d86d2ef1095afcf8b461e58c39N.exe PID 332 wrote to memory of 4052 332 96a8236dcc4bd2a392a82075f38327843610b5d86d2ef1095afcf8b461e58c39N.exe 96a8236dcc4bd2a392a82075f38327843610b5d86d2ef1095afcf8b461e58c39N.exe PID 4052 wrote to memory of 4976 4052 96a8236dcc4bd2a392a82075f38327843610b5d86d2ef1095afcf8b461e58c39N.exe 96a8236dcc4bd2a392a82075f38327843610b5d86d2ef1095afcf8b461e58c39N.exe PID 4052 wrote to memory of 4976 4052 96a8236dcc4bd2a392a82075f38327843610b5d86d2ef1095afcf8b461e58c39N.exe 96a8236dcc4bd2a392a82075f38327843610b5d86d2ef1095afcf8b461e58c39N.exe PID 4052 wrote to memory of 4976 4052 96a8236dcc4bd2a392a82075f38327843610b5d86d2ef1095afcf8b461e58c39N.exe 96a8236dcc4bd2a392a82075f38327843610b5d86d2ef1095afcf8b461e58c39N.exe PID 4052 wrote to memory of 4976 4052 96a8236dcc4bd2a392a82075f38327843610b5d86d2ef1095afcf8b461e58c39N.exe 96a8236dcc4bd2a392a82075f38327843610b5d86d2ef1095afcf8b461e58c39N.exe PID 4052 wrote to memory of 4976 4052 96a8236dcc4bd2a392a82075f38327843610b5d86d2ef1095afcf8b461e58c39N.exe 96a8236dcc4bd2a392a82075f38327843610b5d86d2ef1095afcf8b461e58c39N.exe PID 4052 wrote to memory of 4976 4052 96a8236dcc4bd2a392a82075f38327843610b5d86d2ef1095afcf8b461e58c39N.exe 96a8236dcc4bd2a392a82075f38327843610b5d86d2ef1095afcf8b461e58c39N.exe PID 4052 wrote to memory of 4976 4052 96a8236dcc4bd2a392a82075f38327843610b5d86d2ef1095afcf8b461e58c39N.exe 96a8236dcc4bd2a392a82075f38327843610b5d86d2ef1095afcf8b461e58c39N.exe PID 4052 wrote to memory of 4976 4052 96a8236dcc4bd2a392a82075f38327843610b5d86d2ef1095afcf8b461e58c39N.exe 96a8236dcc4bd2a392a82075f38327843610b5d86d2ef1095afcf8b461e58c39N.exe PID 4052 wrote to memory of 3252 4052 96a8236dcc4bd2a392a82075f38327843610b5d86d2ef1095afcf8b461e58c39N.exe diskperf.exe PID 4052 wrote to memory of 3252 4052 96a8236dcc4bd2a392a82075f38327843610b5d86d2ef1095afcf8b461e58c39N.exe diskperf.exe PID 4052 wrote to memory of 3252 4052 96a8236dcc4bd2a392a82075f38327843610b5d86d2ef1095afcf8b461e58c39N.exe diskperf.exe
Processes
-
C:\Users\Admin\AppData\Local\Temp\96a8236dcc4bd2a392a82075f38327843610b5d86d2ef1095afcf8b461e58c39N.exe"C:\Users\Admin\AppData\Local\Temp\96a8236dcc4bd2a392a82075f38327843610b5d86d2ef1095afcf8b461e58c39N.exe"1⤵
- Suspicious use of SetThreadContext
- System Location Discovery: System Language Discovery
- Suspicious behavior: EnumeratesProcesses
- Suspicious use of SetWindowsHookEx
- Suspicious use of WriteProcessMemory
PID:332 -
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\96a8236dcc4bd2a392a82075f38327843610b5d86d2ef1095afcf8b461e58c39N.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:4900
-
-
C:\Users\Admin\AppData\Local\Temp\96a8236dcc4bd2a392a82075f38327843610b5d86d2ef1095afcf8b461e58c39N.exeC:\Users\Admin\AppData\Local\Temp\96a8236dcc4bd2a392a82075f38327843610b5d86d2ef1095afcf8b461e58c39N.exe2⤵
- Adds Run key to start application
- Suspicious use of SetThreadContext
- System Location Discovery: System Language Discovery
- Suspicious use of WriteProcessMemory
PID:4052 -
C:\Users\Admin\AppData\Local\Temp\96a8236dcc4bd2a392a82075f38327843610b5d86d2ef1095afcf8b461e58c39N.exeC:\Users\Admin\AppData\Local\Temp\96a8236dcc4bd2a392a82075f38327843610b5d86d2ef1095afcf8b461e58c39N.exe3⤵
- System Location Discovery: System Language Discovery
- Suspicious use of SetWindowsHookEx
PID:4976
-
-
C:\Windows\SysWOW64\diskperf.exe"C:\Windows\SysWOW64\diskperf.exe"3⤵PID:3252
-
-