Analysis
-
max time kernel
90s -
max time network
154s -
platform
windows10-2004_x64 -
resource
win10v2004-20230220-en -
resource tags
arch:x64arch:x86image:win10v2004-20230220-enlocale:en-usos:windows10-2004-x64system -
submitted
26-03-2023 15:32
Behavioral task
behavioral1
Sample
3af6bf3832ef4fca74ee05e5d824bdf56bda49558221d2444acc423e12c226af.exe
Resource
win7-20230220-en
Behavioral task
behavioral2
Sample
3af6bf3832ef4fca74ee05e5d824bdf56bda49558221d2444acc423e12c226af.exe
Resource
win10v2004-20230220-en
General
-
Target
3af6bf3832ef4fca74ee05e5d824bdf56bda49558221d2444acc423e12c226af.exe
-
Size
16.8MB
-
MD5
0ee4fb241171bccc49b242101ad50901
-
SHA1
a8b3e341d88a56ca73ce15aa3ddcebddfac29c09
-
SHA256
3af6bf3832ef4fca74ee05e5d824bdf56bda49558221d2444acc423e12c226af
-
SHA512
10a54e85f38d976801ad9fa123c4dd8c044b54ec35f87b6463540eaf2e1a12976f85fd6c2e5c25b9b536982c20e1c9d2e21854db9e6a87a2ccce158efde8c305
-
SSDEEP
196608:mU7d9xZSt4U7d9xZStSU7d9xZSt4U7d9xZStmalLXx:n7d9xZo7d9xZS7d9xZo7d9xZ9alLX
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 -
Processes:
resource yara_rule behavioral2/memory/4764-134-0x0000000000400000-0x0000000000449000-memory.dmp upx -
Adds Run key to start application 2 TTPs 1 IoCs
Processes:
3af6bf3832ef4fca74ee05e5d824bdf56bda49558221d2444acc423e12c226af.exedescription ioc process Set value (str) \REGISTRY\USER\S-1-5-21-1529757233-3489015626-3409890339-1000\SOFTWARE\Microsoft\Windows\CurrentVersion\Run\Microsoft OneDrive = "C:\\Users\\Admin\\AppData\\Local\\Chrome\\StikyNot.exe" 3af6bf3832ef4fca74ee05e5d824bdf56bda49558221d2444acc423e12c226af.exe -
Suspicious use of SetThreadContext 2 IoCs
Processes:
3af6bf3832ef4fca74ee05e5d824bdf56bda49558221d2444acc423e12c226af.exe3af6bf3832ef4fca74ee05e5d824bdf56bda49558221d2444acc423e12c226af.exedescription pid process target process PID 4764 set thread context of 4424 4764 3af6bf3832ef4fca74ee05e5d824bdf56bda49558221d2444acc423e12c226af.exe 3af6bf3832ef4fca74ee05e5d824bdf56bda49558221d2444acc423e12c226af.exe PID 4424 set thread context of 4608 4424 3af6bf3832ef4fca74ee05e5d824bdf56bda49558221d2444acc423e12c226af.exe 3af6bf3832ef4fca74ee05e5d824bdf56bda49558221d2444acc423e12c226af.exe -
Enumerates physical storage devices 1 TTPs
Attempts to interact with connected storage/optical drive(s). Likely ransomware behaviour.
-
Suspicious behavior: EnumeratesProcesses 2 IoCs
Processes:
3af6bf3832ef4fca74ee05e5d824bdf56bda49558221d2444acc423e12c226af.exepid process 4764 3af6bf3832ef4fca74ee05e5d824bdf56bda49558221d2444acc423e12c226af.exe 4764 3af6bf3832ef4fca74ee05e5d824bdf56bda49558221d2444acc423e12c226af.exe -
Suspicious use of SetWindowsHookEx 4 IoCs
Processes:
3af6bf3832ef4fca74ee05e5d824bdf56bda49558221d2444acc423e12c226af.exe3af6bf3832ef4fca74ee05e5d824bdf56bda49558221d2444acc423e12c226af.exepid process 4764 3af6bf3832ef4fca74ee05e5d824bdf56bda49558221d2444acc423e12c226af.exe 4764 3af6bf3832ef4fca74ee05e5d824bdf56bda49558221d2444acc423e12c226af.exe 4608 3af6bf3832ef4fca74ee05e5d824bdf56bda49558221d2444acc423e12c226af.exe 4608 3af6bf3832ef4fca74ee05e5d824bdf56bda49558221d2444acc423e12c226af.exe -
Suspicious use of WriteProcessMemory 43 IoCs
Processes:
3af6bf3832ef4fca74ee05e5d824bdf56bda49558221d2444acc423e12c226af.exe3af6bf3832ef4fca74ee05e5d824bdf56bda49558221d2444acc423e12c226af.exedescription pid process target process PID 4764 wrote to memory of 4420 4764 3af6bf3832ef4fca74ee05e5d824bdf56bda49558221d2444acc423e12c226af.exe cmd.exe PID 4764 wrote to memory of 4420 4764 3af6bf3832ef4fca74ee05e5d824bdf56bda49558221d2444acc423e12c226af.exe cmd.exe PID 4764 wrote to memory of 4420 4764 3af6bf3832ef4fca74ee05e5d824bdf56bda49558221d2444acc423e12c226af.exe cmd.exe PID 4764 wrote to memory of 4424 4764 3af6bf3832ef4fca74ee05e5d824bdf56bda49558221d2444acc423e12c226af.exe 3af6bf3832ef4fca74ee05e5d824bdf56bda49558221d2444acc423e12c226af.exe PID 4764 wrote to memory of 4424 4764 3af6bf3832ef4fca74ee05e5d824bdf56bda49558221d2444acc423e12c226af.exe 3af6bf3832ef4fca74ee05e5d824bdf56bda49558221d2444acc423e12c226af.exe PID 4764 wrote to memory of 4424 4764 3af6bf3832ef4fca74ee05e5d824bdf56bda49558221d2444acc423e12c226af.exe 3af6bf3832ef4fca74ee05e5d824bdf56bda49558221d2444acc423e12c226af.exe PID 4764 wrote to memory of 4424 4764 3af6bf3832ef4fca74ee05e5d824bdf56bda49558221d2444acc423e12c226af.exe 3af6bf3832ef4fca74ee05e5d824bdf56bda49558221d2444acc423e12c226af.exe PID 4764 wrote to memory of 4424 4764 3af6bf3832ef4fca74ee05e5d824bdf56bda49558221d2444acc423e12c226af.exe 3af6bf3832ef4fca74ee05e5d824bdf56bda49558221d2444acc423e12c226af.exe PID 4764 wrote to memory of 4424 4764 3af6bf3832ef4fca74ee05e5d824bdf56bda49558221d2444acc423e12c226af.exe 3af6bf3832ef4fca74ee05e5d824bdf56bda49558221d2444acc423e12c226af.exe PID 4764 wrote to memory of 4424 4764 3af6bf3832ef4fca74ee05e5d824bdf56bda49558221d2444acc423e12c226af.exe 3af6bf3832ef4fca74ee05e5d824bdf56bda49558221d2444acc423e12c226af.exe PID 4764 wrote to memory of 4424 4764 3af6bf3832ef4fca74ee05e5d824bdf56bda49558221d2444acc423e12c226af.exe 3af6bf3832ef4fca74ee05e5d824bdf56bda49558221d2444acc423e12c226af.exe PID 4764 wrote to memory of 4424 4764 3af6bf3832ef4fca74ee05e5d824bdf56bda49558221d2444acc423e12c226af.exe 3af6bf3832ef4fca74ee05e5d824bdf56bda49558221d2444acc423e12c226af.exe PID 4764 wrote to memory of 4424 4764 3af6bf3832ef4fca74ee05e5d824bdf56bda49558221d2444acc423e12c226af.exe 3af6bf3832ef4fca74ee05e5d824bdf56bda49558221d2444acc423e12c226af.exe PID 4764 wrote to memory of 4424 4764 3af6bf3832ef4fca74ee05e5d824bdf56bda49558221d2444acc423e12c226af.exe 3af6bf3832ef4fca74ee05e5d824bdf56bda49558221d2444acc423e12c226af.exe PID 4764 wrote to memory of 4424 4764 3af6bf3832ef4fca74ee05e5d824bdf56bda49558221d2444acc423e12c226af.exe 3af6bf3832ef4fca74ee05e5d824bdf56bda49558221d2444acc423e12c226af.exe PID 4764 wrote to memory of 4424 4764 3af6bf3832ef4fca74ee05e5d824bdf56bda49558221d2444acc423e12c226af.exe 3af6bf3832ef4fca74ee05e5d824bdf56bda49558221d2444acc423e12c226af.exe PID 4764 wrote to memory of 4424 4764 3af6bf3832ef4fca74ee05e5d824bdf56bda49558221d2444acc423e12c226af.exe 3af6bf3832ef4fca74ee05e5d824bdf56bda49558221d2444acc423e12c226af.exe PID 4764 wrote to memory of 4424 4764 3af6bf3832ef4fca74ee05e5d824bdf56bda49558221d2444acc423e12c226af.exe 3af6bf3832ef4fca74ee05e5d824bdf56bda49558221d2444acc423e12c226af.exe PID 4764 wrote to memory of 4424 4764 3af6bf3832ef4fca74ee05e5d824bdf56bda49558221d2444acc423e12c226af.exe 3af6bf3832ef4fca74ee05e5d824bdf56bda49558221d2444acc423e12c226af.exe PID 4764 wrote to memory of 4424 4764 3af6bf3832ef4fca74ee05e5d824bdf56bda49558221d2444acc423e12c226af.exe 3af6bf3832ef4fca74ee05e5d824bdf56bda49558221d2444acc423e12c226af.exe PID 4764 wrote to memory of 4424 4764 3af6bf3832ef4fca74ee05e5d824bdf56bda49558221d2444acc423e12c226af.exe 3af6bf3832ef4fca74ee05e5d824bdf56bda49558221d2444acc423e12c226af.exe PID 4764 wrote to memory of 4424 4764 3af6bf3832ef4fca74ee05e5d824bdf56bda49558221d2444acc423e12c226af.exe 3af6bf3832ef4fca74ee05e5d824bdf56bda49558221d2444acc423e12c226af.exe PID 4764 wrote to memory of 4424 4764 3af6bf3832ef4fca74ee05e5d824bdf56bda49558221d2444acc423e12c226af.exe 3af6bf3832ef4fca74ee05e5d824bdf56bda49558221d2444acc423e12c226af.exe PID 4764 wrote to memory of 4424 4764 3af6bf3832ef4fca74ee05e5d824bdf56bda49558221d2444acc423e12c226af.exe 3af6bf3832ef4fca74ee05e5d824bdf56bda49558221d2444acc423e12c226af.exe PID 4764 wrote to memory of 4424 4764 3af6bf3832ef4fca74ee05e5d824bdf56bda49558221d2444acc423e12c226af.exe 3af6bf3832ef4fca74ee05e5d824bdf56bda49558221d2444acc423e12c226af.exe PID 4764 wrote to memory of 4424 4764 3af6bf3832ef4fca74ee05e5d824bdf56bda49558221d2444acc423e12c226af.exe 3af6bf3832ef4fca74ee05e5d824bdf56bda49558221d2444acc423e12c226af.exe PID 4764 wrote to memory of 4424 4764 3af6bf3832ef4fca74ee05e5d824bdf56bda49558221d2444acc423e12c226af.exe 3af6bf3832ef4fca74ee05e5d824bdf56bda49558221d2444acc423e12c226af.exe PID 4764 wrote to memory of 4424 4764 3af6bf3832ef4fca74ee05e5d824bdf56bda49558221d2444acc423e12c226af.exe 3af6bf3832ef4fca74ee05e5d824bdf56bda49558221d2444acc423e12c226af.exe PID 4764 wrote to memory of 4424 4764 3af6bf3832ef4fca74ee05e5d824bdf56bda49558221d2444acc423e12c226af.exe 3af6bf3832ef4fca74ee05e5d824bdf56bda49558221d2444acc423e12c226af.exe PID 4764 wrote to memory of 4424 4764 3af6bf3832ef4fca74ee05e5d824bdf56bda49558221d2444acc423e12c226af.exe 3af6bf3832ef4fca74ee05e5d824bdf56bda49558221d2444acc423e12c226af.exe PID 4764 wrote to memory of 4424 4764 3af6bf3832ef4fca74ee05e5d824bdf56bda49558221d2444acc423e12c226af.exe 3af6bf3832ef4fca74ee05e5d824bdf56bda49558221d2444acc423e12c226af.exe PID 4764 wrote to memory of 4424 4764 3af6bf3832ef4fca74ee05e5d824bdf56bda49558221d2444acc423e12c226af.exe 3af6bf3832ef4fca74ee05e5d824bdf56bda49558221d2444acc423e12c226af.exe PID 4424 wrote to memory of 4608 4424 3af6bf3832ef4fca74ee05e5d824bdf56bda49558221d2444acc423e12c226af.exe 3af6bf3832ef4fca74ee05e5d824bdf56bda49558221d2444acc423e12c226af.exe PID 4424 wrote to memory of 4608 4424 3af6bf3832ef4fca74ee05e5d824bdf56bda49558221d2444acc423e12c226af.exe 3af6bf3832ef4fca74ee05e5d824bdf56bda49558221d2444acc423e12c226af.exe PID 4424 wrote to memory of 4608 4424 3af6bf3832ef4fca74ee05e5d824bdf56bda49558221d2444acc423e12c226af.exe 3af6bf3832ef4fca74ee05e5d824bdf56bda49558221d2444acc423e12c226af.exe PID 4424 wrote to memory of 4608 4424 3af6bf3832ef4fca74ee05e5d824bdf56bda49558221d2444acc423e12c226af.exe 3af6bf3832ef4fca74ee05e5d824bdf56bda49558221d2444acc423e12c226af.exe PID 4424 wrote to memory of 4608 4424 3af6bf3832ef4fca74ee05e5d824bdf56bda49558221d2444acc423e12c226af.exe 3af6bf3832ef4fca74ee05e5d824bdf56bda49558221d2444acc423e12c226af.exe PID 4424 wrote to memory of 4608 4424 3af6bf3832ef4fca74ee05e5d824bdf56bda49558221d2444acc423e12c226af.exe 3af6bf3832ef4fca74ee05e5d824bdf56bda49558221d2444acc423e12c226af.exe PID 4424 wrote to memory of 4608 4424 3af6bf3832ef4fca74ee05e5d824bdf56bda49558221d2444acc423e12c226af.exe 3af6bf3832ef4fca74ee05e5d824bdf56bda49558221d2444acc423e12c226af.exe PID 4424 wrote to memory of 4608 4424 3af6bf3832ef4fca74ee05e5d824bdf56bda49558221d2444acc423e12c226af.exe 3af6bf3832ef4fca74ee05e5d824bdf56bda49558221d2444acc423e12c226af.exe PID 4424 wrote to memory of 4804 4424 3af6bf3832ef4fca74ee05e5d824bdf56bda49558221d2444acc423e12c226af.exe diskperf.exe PID 4424 wrote to memory of 4804 4424 3af6bf3832ef4fca74ee05e5d824bdf56bda49558221d2444acc423e12c226af.exe diskperf.exe PID 4424 wrote to memory of 4804 4424 3af6bf3832ef4fca74ee05e5d824bdf56bda49558221d2444acc423e12c226af.exe diskperf.exe
Processes
-
C:\Users\Admin\AppData\Local\Temp\3af6bf3832ef4fca74ee05e5d824bdf56bda49558221d2444acc423e12c226af.exe"C:\Users\Admin\AppData\Local\Temp\3af6bf3832ef4fca74ee05e5d824bdf56bda49558221d2444acc423e12c226af.exe"1⤵
- Suspicious use of SetThreadContext
- Suspicious behavior: EnumeratesProcesses
- Suspicious use of SetWindowsHookEx
- Suspicious use of WriteProcessMemory
-
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\3af6bf3832ef4fca74ee05e5d824bdf56bda49558221d2444acc423e12c226af.exe",1: >"C:\Users\Admin\AppData\Roaming\Microsoft\Windows\Start Menu\Programs\Startup\x.vbs"2⤵
- Drops startup file
-
C:\Users\Admin\AppData\Local\Temp\3af6bf3832ef4fca74ee05e5d824bdf56bda49558221d2444acc423e12c226af.exeC:\Users\Admin\AppData\Local\Temp\3af6bf3832ef4fca74ee05e5d824bdf56bda49558221d2444acc423e12c226af.exe2⤵
- Adds Run key to start application
- Suspicious use of SetThreadContext
- Suspicious use of WriteProcessMemory
-
C:\Users\Admin\AppData\Local\Temp\3af6bf3832ef4fca74ee05e5d824bdf56bda49558221d2444acc423e12c226af.exeC:\Users\Admin\AppData\Local\Temp\3af6bf3832ef4fca74ee05e5d824bdf56bda49558221d2444acc423e12c226af.exe3⤵
- Suspicious use of SetWindowsHookEx
-
C:\Windows\SysWOW64\diskperf.exe"C:\Windows\SysWOW64\diskperf.exe"3⤵
Network
MITRE ATT&CK Matrix ATT&CK v6
Replay Monitor
Loading Replay Monitor...
Downloads
-
memory/4424-142-0x0000000000400000-0x0000000001400000-memory.dmpFilesize
16.0MB
-
memory/4424-136-0x0000000000400000-0x0000000000628000-memory.dmpFilesize
2.2MB
-
memory/4424-143-0x0000000000400000-0x0000000000628000-memory.dmpFilesize
2.2MB
-
memory/4424-144-0x0000000007180000-0x0000000007181000-memory.dmpFilesize
4KB
-
memory/4424-138-0x0000000000400000-0x0000000000628000-memory.dmpFilesize
2.2MB
-
memory/4424-139-0x0000000000400000-0x0000000001400000-memory.dmpFilesize
16.0MB
-
memory/4424-141-0x0000000000400000-0x0000000000628000-memory.dmpFilesize
2.2MB
-
memory/4424-140-0x0000000000400000-0x0000000001400000-memory.dmpFilesize
16.0MB
-
memory/4424-156-0x0000000000400000-0x0000000000628000-memory.dmpFilesize
2.2MB
-
memory/4424-135-0x0000000000400000-0x0000000001400000-memory.dmpFilesize
16.0MB
-
memory/4424-137-0x0000000000400000-0x0000000000628000-memory.dmpFilesize
2.2MB
-
memory/4424-146-0x0000000000400000-0x0000000001400000-memory.dmpFilesize
16.0MB
-
memory/4424-155-0x0000000000400000-0x0000000001400000-memory.dmpFilesize
16.0MB
-
memory/4608-154-0x0000000000400000-0x000000000043E000-memory.dmpFilesize
248KB
-
memory/4608-150-0x0000000000400000-0x000000000043E000-memory.dmpFilesize
248KB
-
memory/4608-161-0x0000000000400000-0x000000000043E000-memory.dmpFilesize
248KB
-
memory/4608-159-0x0000000000400000-0x000000000043E000-memory.dmpFilesize
248KB
-
memory/4764-134-0x0000000000400000-0x0000000000449000-memory.dmpFilesize
292KB