Analysis
-
max time kernel
94s -
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 17:54
Behavioral task
behavioral1
Sample
4d2f2a733eb1ab8bdefcfa015b663a5893850dd472c786ffde21846730805e5d.exe
Resource
win7-20240903-en
Behavioral task
behavioral2
Sample
4d2f2a733eb1ab8bdefcfa015b663a5893850dd472c786ffde21846730805e5d.exe
Resource
win10v2004-20241007-en
General
-
Target
4d2f2a733eb1ab8bdefcfa015b663a5893850dd472c786ffde21846730805e5d.exe
-
Size
2.9MB
-
MD5
79afeb809e234451874d12df009b4043
-
SHA1
a8a26a4bfc395e570e295b7c21ec5888464b9ac3
-
SHA256
4d2f2a733eb1ab8bdefcfa015b663a5893850dd472c786ffde21846730805e5d
-
SHA512
f57eb987e045849ad16ae060ed368cd4274b8f26b13a7921a6b4c057658f40b98d6d3bba77fa887dfa3d468ecd56a712d7576d0906acef11a1431e5b80dd882a
-
SSDEEP
24576:ATU7AAmZZcVKfIxTiEVc847flVC6faaQDbGV6eH81k6IbGD2JTu0GoZQDbGV6eHi:ATU7AAmw4gxeOw46fUbNecCCFbNecF
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:
4d2f2a733eb1ab8bdefcfa015b663a5893850dd472c786ffde21846730805e5d.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" 4d2f2a733eb1ab8bdefcfa015b663a5893850dd472c786ffde21846730805e5d.exe -
Suspicious use of SetThreadContext 2 IoCs
Processes:
4d2f2a733eb1ab8bdefcfa015b663a5893850dd472c786ffde21846730805e5d.exe4d2f2a733eb1ab8bdefcfa015b663a5893850dd472c786ffde21846730805e5d.exedescription pid process target process PID 3292 set thread context of 2920 3292 4d2f2a733eb1ab8bdefcfa015b663a5893850dd472c786ffde21846730805e5d.exe 4d2f2a733eb1ab8bdefcfa015b663a5893850dd472c786ffde21846730805e5d.exe PID 2920 set thread context of 4236 2920 4d2f2a733eb1ab8bdefcfa015b663a5893850dd472c786ffde21846730805e5d.exe 4d2f2a733eb1ab8bdefcfa015b663a5893850dd472c786ffde21846730805e5d.exe -
Processes:
resource yara_rule behavioral2/memory/3292-0-0x0000000000400000-0x0000000000446000-memory.dmp upx behavioral2/memory/3292-11-0x0000000000400000-0x0000000000446000-memory.dmp upx -
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:
4d2f2a733eb1ab8bdefcfa015b663a5893850dd472c786ffde21846730805e5d.execmd.exe4d2f2a733eb1ab8bdefcfa015b663a5893850dd472c786ffde21846730805e5d.exe4d2f2a733eb1ab8bdefcfa015b663a5893850dd472c786ffde21846730805e5d.exedescription ioc process Key opened \REGISTRY\MACHINE\SYSTEM\ControlSet001\Control\NLS\Language 4d2f2a733eb1ab8bdefcfa015b663a5893850dd472c786ffde21846730805e5d.exe Key opened \REGISTRY\MACHINE\SYSTEM\ControlSet001\Control\NLS\Language cmd.exe Key opened \REGISTRY\MACHINE\SYSTEM\ControlSet001\Control\NLS\Language 4d2f2a733eb1ab8bdefcfa015b663a5893850dd472c786ffde21846730805e5d.exe Key opened \REGISTRY\MACHINE\SYSTEM\ControlSet001\Control\NLS\Language 4d2f2a733eb1ab8bdefcfa015b663a5893850dd472c786ffde21846730805e5d.exe -
Suspicious behavior: EnumeratesProcesses 2 IoCs
Processes:
4d2f2a733eb1ab8bdefcfa015b663a5893850dd472c786ffde21846730805e5d.exepid process 3292 4d2f2a733eb1ab8bdefcfa015b663a5893850dd472c786ffde21846730805e5d.exe 3292 4d2f2a733eb1ab8bdefcfa015b663a5893850dd472c786ffde21846730805e5d.exe -
Suspicious use of SetWindowsHookEx 4 IoCs
Processes:
4d2f2a733eb1ab8bdefcfa015b663a5893850dd472c786ffde21846730805e5d.exe4d2f2a733eb1ab8bdefcfa015b663a5893850dd472c786ffde21846730805e5d.exepid process 3292 4d2f2a733eb1ab8bdefcfa015b663a5893850dd472c786ffde21846730805e5d.exe 3292 4d2f2a733eb1ab8bdefcfa015b663a5893850dd472c786ffde21846730805e5d.exe 4236 4d2f2a733eb1ab8bdefcfa015b663a5893850dd472c786ffde21846730805e5d.exe 4236 4d2f2a733eb1ab8bdefcfa015b663a5893850dd472c786ffde21846730805e5d.exe -
Suspicious use of WriteProcessMemory 43 IoCs
Processes:
4d2f2a733eb1ab8bdefcfa015b663a5893850dd472c786ffde21846730805e5d.exe4d2f2a733eb1ab8bdefcfa015b663a5893850dd472c786ffde21846730805e5d.exedescription pid process target process PID 3292 wrote to memory of 1296 3292 4d2f2a733eb1ab8bdefcfa015b663a5893850dd472c786ffde21846730805e5d.exe cmd.exe PID 3292 wrote to memory of 1296 3292 4d2f2a733eb1ab8bdefcfa015b663a5893850dd472c786ffde21846730805e5d.exe cmd.exe PID 3292 wrote to memory of 1296 3292 4d2f2a733eb1ab8bdefcfa015b663a5893850dd472c786ffde21846730805e5d.exe cmd.exe PID 3292 wrote to memory of 2920 3292 4d2f2a733eb1ab8bdefcfa015b663a5893850dd472c786ffde21846730805e5d.exe 4d2f2a733eb1ab8bdefcfa015b663a5893850dd472c786ffde21846730805e5d.exe PID 3292 wrote to memory of 2920 3292 4d2f2a733eb1ab8bdefcfa015b663a5893850dd472c786ffde21846730805e5d.exe 4d2f2a733eb1ab8bdefcfa015b663a5893850dd472c786ffde21846730805e5d.exe PID 3292 wrote to memory of 2920 3292 4d2f2a733eb1ab8bdefcfa015b663a5893850dd472c786ffde21846730805e5d.exe 4d2f2a733eb1ab8bdefcfa015b663a5893850dd472c786ffde21846730805e5d.exe PID 3292 wrote to memory of 2920 3292 4d2f2a733eb1ab8bdefcfa015b663a5893850dd472c786ffde21846730805e5d.exe 4d2f2a733eb1ab8bdefcfa015b663a5893850dd472c786ffde21846730805e5d.exe PID 3292 wrote to memory of 2920 3292 4d2f2a733eb1ab8bdefcfa015b663a5893850dd472c786ffde21846730805e5d.exe 4d2f2a733eb1ab8bdefcfa015b663a5893850dd472c786ffde21846730805e5d.exe PID 3292 wrote to memory of 2920 3292 4d2f2a733eb1ab8bdefcfa015b663a5893850dd472c786ffde21846730805e5d.exe 4d2f2a733eb1ab8bdefcfa015b663a5893850dd472c786ffde21846730805e5d.exe PID 3292 wrote to memory of 2920 3292 4d2f2a733eb1ab8bdefcfa015b663a5893850dd472c786ffde21846730805e5d.exe 4d2f2a733eb1ab8bdefcfa015b663a5893850dd472c786ffde21846730805e5d.exe PID 3292 wrote to memory of 2920 3292 4d2f2a733eb1ab8bdefcfa015b663a5893850dd472c786ffde21846730805e5d.exe 4d2f2a733eb1ab8bdefcfa015b663a5893850dd472c786ffde21846730805e5d.exe PID 3292 wrote to memory of 2920 3292 4d2f2a733eb1ab8bdefcfa015b663a5893850dd472c786ffde21846730805e5d.exe 4d2f2a733eb1ab8bdefcfa015b663a5893850dd472c786ffde21846730805e5d.exe PID 3292 wrote to memory of 2920 3292 4d2f2a733eb1ab8bdefcfa015b663a5893850dd472c786ffde21846730805e5d.exe 4d2f2a733eb1ab8bdefcfa015b663a5893850dd472c786ffde21846730805e5d.exe PID 3292 wrote to memory of 2920 3292 4d2f2a733eb1ab8bdefcfa015b663a5893850dd472c786ffde21846730805e5d.exe 4d2f2a733eb1ab8bdefcfa015b663a5893850dd472c786ffde21846730805e5d.exe PID 3292 wrote to memory of 2920 3292 4d2f2a733eb1ab8bdefcfa015b663a5893850dd472c786ffde21846730805e5d.exe 4d2f2a733eb1ab8bdefcfa015b663a5893850dd472c786ffde21846730805e5d.exe PID 3292 wrote to memory of 2920 3292 4d2f2a733eb1ab8bdefcfa015b663a5893850dd472c786ffde21846730805e5d.exe 4d2f2a733eb1ab8bdefcfa015b663a5893850dd472c786ffde21846730805e5d.exe PID 3292 wrote to memory of 2920 3292 4d2f2a733eb1ab8bdefcfa015b663a5893850dd472c786ffde21846730805e5d.exe 4d2f2a733eb1ab8bdefcfa015b663a5893850dd472c786ffde21846730805e5d.exe PID 3292 wrote to memory of 2920 3292 4d2f2a733eb1ab8bdefcfa015b663a5893850dd472c786ffde21846730805e5d.exe 4d2f2a733eb1ab8bdefcfa015b663a5893850dd472c786ffde21846730805e5d.exe PID 3292 wrote to memory of 2920 3292 4d2f2a733eb1ab8bdefcfa015b663a5893850dd472c786ffde21846730805e5d.exe 4d2f2a733eb1ab8bdefcfa015b663a5893850dd472c786ffde21846730805e5d.exe PID 3292 wrote to memory of 2920 3292 4d2f2a733eb1ab8bdefcfa015b663a5893850dd472c786ffde21846730805e5d.exe 4d2f2a733eb1ab8bdefcfa015b663a5893850dd472c786ffde21846730805e5d.exe PID 3292 wrote to memory of 2920 3292 4d2f2a733eb1ab8bdefcfa015b663a5893850dd472c786ffde21846730805e5d.exe 4d2f2a733eb1ab8bdefcfa015b663a5893850dd472c786ffde21846730805e5d.exe PID 3292 wrote to memory of 2920 3292 4d2f2a733eb1ab8bdefcfa015b663a5893850dd472c786ffde21846730805e5d.exe 4d2f2a733eb1ab8bdefcfa015b663a5893850dd472c786ffde21846730805e5d.exe PID 3292 wrote to memory of 2920 3292 4d2f2a733eb1ab8bdefcfa015b663a5893850dd472c786ffde21846730805e5d.exe 4d2f2a733eb1ab8bdefcfa015b663a5893850dd472c786ffde21846730805e5d.exe PID 3292 wrote to memory of 2920 3292 4d2f2a733eb1ab8bdefcfa015b663a5893850dd472c786ffde21846730805e5d.exe 4d2f2a733eb1ab8bdefcfa015b663a5893850dd472c786ffde21846730805e5d.exe PID 3292 wrote to memory of 2920 3292 4d2f2a733eb1ab8bdefcfa015b663a5893850dd472c786ffde21846730805e5d.exe 4d2f2a733eb1ab8bdefcfa015b663a5893850dd472c786ffde21846730805e5d.exe PID 3292 wrote to memory of 2920 3292 4d2f2a733eb1ab8bdefcfa015b663a5893850dd472c786ffde21846730805e5d.exe 4d2f2a733eb1ab8bdefcfa015b663a5893850dd472c786ffde21846730805e5d.exe PID 3292 wrote to memory of 2920 3292 4d2f2a733eb1ab8bdefcfa015b663a5893850dd472c786ffde21846730805e5d.exe 4d2f2a733eb1ab8bdefcfa015b663a5893850dd472c786ffde21846730805e5d.exe PID 3292 wrote to memory of 2920 3292 4d2f2a733eb1ab8bdefcfa015b663a5893850dd472c786ffde21846730805e5d.exe 4d2f2a733eb1ab8bdefcfa015b663a5893850dd472c786ffde21846730805e5d.exe PID 3292 wrote to memory of 2920 3292 4d2f2a733eb1ab8bdefcfa015b663a5893850dd472c786ffde21846730805e5d.exe 4d2f2a733eb1ab8bdefcfa015b663a5893850dd472c786ffde21846730805e5d.exe PID 3292 wrote to memory of 2920 3292 4d2f2a733eb1ab8bdefcfa015b663a5893850dd472c786ffde21846730805e5d.exe 4d2f2a733eb1ab8bdefcfa015b663a5893850dd472c786ffde21846730805e5d.exe PID 3292 wrote to memory of 2920 3292 4d2f2a733eb1ab8bdefcfa015b663a5893850dd472c786ffde21846730805e5d.exe 4d2f2a733eb1ab8bdefcfa015b663a5893850dd472c786ffde21846730805e5d.exe PID 3292 wrote to memory of 2920 3292 4d2f2a733eb1ab8bdefcfa015b663a5893850dd472c786ffde21846730805e5d.exe 4d2f2a733eb1ab8bdefcfa015b663a5893850dd472c786ffde21846730805e5d.exe PID 2920 wrote to memory of 4236 2920 4d2f2a733eb1ab8bdefcfa015b663a5893850dd472c786ffde21846730805e5d.exe 4d2f2a733eb1ab8bdefcfa015b663a5893850dd472c786ffde21846730805e5d.exe PID 2920 wrote to memory of 4236 2920 4d2f2a733eb1ab8bdefcfa015b663a5893850dd472c786ffde21846730805e5d.exe 4d2f2a733eb1ab8bdefcfa015b663a5893850dd472c786ffde21846730805e5d.exe PID 2920 wrote to memory of 4236 2920 4d2f2a733eb1ab8bdefcfa015b663a5893850dd472c786ffde21846730805e5d.exe 4d2f2a733eb1ab8bdefcfa015b663a5893850dd472c786ffde21846730805e5d.exe PID 2920 wrote to memory of 4236 2920 4d2f2a733eb1ab8bdefcfa015b663a5893850dd472c786ffde21846730805e5d.exe 4d2f2a733eb1ab8bdefcfa015b663a5893850dd472c786ffde21846730805e5d.exe PID 2920 wrote to memory of 4236 2920 4d2f2a733eb1ab8bdefcfa015b663a5893850dd472c786ffde21846730805e5d.exe 4d2f2a733eb1ab8bdefcfa015b663a5893850dd472c786ffde21846730805e5d.exe PID 2920 wrote to memory of 4236 2920 4d2f2a733eb1ab8bdefcfa015b663a5893850dd472c786ffde21846730805e5d.exe 4d2f2a733eb1ab8bdefcfa015b663a5893850dd472c786ffde21846730805e5d.exe PID 2920 wrote to memory of 4236 2920 4d2f2a733eb1ab8bdefcfa015b663a5893850dd472c786ffde21846730805e5d.exe 4d2f2a733eb1ab8bdefcfa015b663a5893850dd472c786ffde21846730805e5d.exe PID 2920 wrote to memory of 4236 2920 4d2f2a733eb1ab8bdefcfa015b663a5893850dd472c786ffde21846730805e5d.exe 4d2f2a733eb1ab8bdefcfa015b663a5893850dd472c786ffde21846730805e5d.exe PID 2920 wrote to memory of 2528 2920 4d2f2a733eb1ab8bdefcfa015b663a5893850dd472c786ffde21846730805e5d.exe diskperf.exe PID 2920 wrote to memory of 2528 2920 4d2f2a733eb1ab8bdefcfa015b663a5893850dd472c786ffde21846730805e5d.exe diskperf.exe PID 2920 wrote to memory of 2528 2920 4d2f2a733eb1ab8bdefcfa015b663a5893850dd472c786ffde21846730805e5d.exe diskperf.exe
Processes
-
C:\Users\Admin\AppData\Local\Temp\4d2f2a733eb1ab8bdefcfa015b663a5893850dd472c786ffde21846730805e5d.exe"C:\Users\Admin\AppData\Local\Temp\4d2f2a733eb1ab8bdefcfa015b663a5893850dd472c786ffde21846730805e5d.exe"1⤵
- Suspicious use of SetThreadContext
- System Location Discovery: System Language Discovery
- Suspicious behavior: EnumeratesProcesses
- Suspicious use of SetWindowsHookEx
- Suspicious use of WriteProcessMemory
PID:3292 -
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\4d2f2a733eb1ab8bdefcfa015b663a5893850dd472c786ffde21846730805e5d.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:1296
-
-
C:\Users\Admin\AppData\Local\Temp\4d2f2a733eb1ab8bdefcfa015b663a5893850dd472c786ffde21846730805e5d.exeC:\Users\Admin\AppData\Local\Temp\4d2f2a733eb1ab8bdefcfa015b663a5893850dd472c786ffde21846730805e5d.exe2⤵
- Adds Run key to start application
- Suspicious use of SetThreadContext
- System Location Discovery: System Language Discovery
- Suspicious use of WriteProcessMemory
PID:2920 -
C:\Users\Admin\AppData\Local\Temp\4d2f2a733eb1ab8bdefcfa015b663a5893850dd472c786ffde21846730805e5d.exeC:\Users\Admin\AppData\Local\Temp\4d2f2a733eb1ab8bdefcfa015b663a5893850dd472c786ffde21846730805e5d.exe3⤵
- System Location Discovery: System Language Discovery
- Suspicious use of SetWindowsHookEx
PID:4236
-
-
C:\Windows\SysWOW64\diskperf.exe"C:\Windows\SysWOW64\diskperf.exe"3⤵PID:2528
-
-