Analysis
-
max time kernel
166s -
max time network
186s -
platform
windows10-2004_x64 -
resource
win10v2004-20221111-en -
resource tags
arch:x64arch:x86image:win10v2004-20221111-enlocale:en-usos:windows10-2004-x64system -
submitted
23-11-2022 13:17
Static task
static1
Behavioral task
behavioral1
Sample
b7d67df0f8806f4df808056e9136b3d820af8dd5b6e7591c27a0f5f6258f0e21.exe
Resource
win7-20221111-en
Behavioral task
behavioral2
Sample
b7d67df0f8806f4df808056e9136b3d820af8dd5b6e7591c27a0f5f6258f0e21.exe
Resource
win10v2004-20221111-en
General
-
Target
b7d67df0f8806f4df808056e9136b3d820af8dd5b6e7591c27a0f5f6258f0e21.exe
-
Size
377KB
-
MD5
ba1d8a076e6e175fd1e32ebccc9cc0d9
-
SHA1
bed17f1a2a2e39098525928c5e5f8eb8e5ccbc90
-
SHA256
b7d67df0f8806f4df808056e9136b3d820af8dd5b6e7591c27a0f5f6258f0e21
-
SHA512
5b7306dfb928860444571da7d76877b34406ec987614e37803b71414a15886d5eacb9f27af298247a23f71b5d95a955ee28e716e4a24963adf513d8e6954b40b
-
SSDEEP
6144:8ew00UjkA87onOlzrfGY8CLFjfXpovXnFZCoxPjLadlNogTItMCw/QcDQwe4IIBL:PMdlNoKI3YJAQTX+u
Malware Config
Signatures
-
Adds Run key to start application 2 TTPs 1 IoCs
Processes:
b7d67df0f8806f4df808056e9136b3d820af8dd5b6e7591c27a0f5f6258f0e21.exedescription ioc process Set value (str) \REGISTRY\USER\S-1-5-21-2386679933-1492765628-3466841596-1000\SOFTWARE\Microsoft\Windows\CurrentVersion\RunOnce\sidebar = "C:\\Users\\Admin\\AppData\\Roaming\\Sample.lnk" b7d67df0f8806f4df808056e9136b3d820af8dd5b6e7591c27a0f5f6258f0e21.exe -
Suspicious use of SetThreadContext 2 IoCs
Processes:
b7d67df0f8806f4df808056e9136b3d820af8dd5b6e7591c27a0f5f6258f0e21.exedescription pid process target process PID 2168 set thread context of 1452 2168 b7d67df0f8806f4df808056e9136b3d820af8dd5b6e7591c27a0f5f6258f0e21.exe AppLaunch.exe PID 2168 set thread context of 2408 2168 b7d67df0f8806f4df808056e9136b3d820af8dd5b6e7591c27a0f5f6258f0e21.exe AppLaunch.exe -
Enumerates physical storage devices 1 TTPs
Attempts to interact with connected storage/optical drive(s). Likely ransomware behaviour.
-
Suspicious behavior: EnumeratesProcesses 9 IoCs
Processes:
b7d67df0f8806f4df808056e9136b3d820af8dd5b6e7591c27a0f5f6258f0e21.exepid process 2168 b7d67df0f8806f4df808056e9136b3d820af8dd5b6e7591c27a0f5f6258f0e21.exe 2168 b7d67df0f8806f4df808056e9136b3d820af8dd5b6e7591c27a0f5f6258f0e21.exe 2168 b7d67df0f8806f4df808056e9136b3d820af8dd5b6e7591c27a0f5f6258f0e21.exe 2168 b7d67df0f8806f4df808056e9136b3d820af8dd5b6e7591c27a0f5f6258f0e21.exe 2168 b7d67df0f8806f4df808056e9136b3d820af8dd5b6e7591c27a0f5f6258f0e21.exe 2168 b7d67df0f8806f4df808056e9136b3d820af8dd5b6e7591c27a0f5f6258f0e21.exe 2168 b7d67df0f8806f4df808056e9136b3d820af8dd5b6e7591c27a0f5f6258f0e21.exe 2168 b7d67df0f8806f4df808056e9136b3d820af8dd5b6e7591c27a0f5f6258f0e21.exe 2168 b7d67df0f8806f4df808056e9136b3d820af8dd5b6e7591c27a0f5f6258f0e21.exe -
Suspicious use of AdjustPrivilegeToken 1 IoCs
Processes:
b7d67df0f8806f4df808056e9136b3d820af8dd5b6e7591c27a0f5f6258f0e21.exedescription pid process Token: SeDebugPrivilege 2168 b7d67df0f8806f4df808056e9136b3d820af8dd5b6e7591c27a0f5f6258f0e21.exe -
Suspicious use of WriteProcessMemory 26 IoCs
Processes:
b7d67df0f8806f4df808056e9136b3d820af8dd5b6e7591c27a0f5f6258f0e21.exedescription pid process target process PID 2168 wrote to memory of 3768 2168 b7d67df0f8806f4df808056e9136b3d820af8dd5b6e7591c27a0f5f6258f0e21.exe CMD.exe PID 2168 wrote to memory of 3768 2168 b7d67df0f8806f4df808056e9136b3d820af8dd5b6e7591c27a0f5f6258f0e21.exe CMD.exe PID 2168 wrote to memory of 3768 2168 b7d67df0f8806f4df808056e9136b3d820af8dd5b6e7591c27a0f5f6258f0e21.exe CMD.exe PID 2168 wrote to memory of 5008 2168 b7d67df0f8806f4df808056e9136b3d820af8dd5b6e7591c27a0f5f6258f0e21.exe CMD.exe PID 2168 wrote to memory of 5008 2168 b7d67df0f8806f4df808056e9136b3d820af8dd5b6e7591c27a0f5f6258f0e21.exe CMD.exe PID 2168 wrote to memory of 5008 2168 b7d67df0f8806f4df808056e9136b3d820af8dd5b6e7591c27a0f5f6258f0e21.exe CMD.exe PID 2168 wrote to memory of 1452 2168 b7d67df0f8806f4df808056e9136b3d820af8dd5b6e7591c27a0f5f6258f0e21.exe AppLaunch.exe PID 2168 wrote to memory of 1452 2168 b7d67df0f8806f4df808056e9136b3d820af8dd5b6e7591c27a0f5f6258f0e21.exe AppLaunch.exe PID 2168 wrote to memory of 1452 2168 b7d67df0f8806f4df808056e9136b3d820af8dd5b6e7591c27a0f5f6258f0e21.exe AppLaunch.exe PID 2168 wrote to memory of 1452 2168 b7d67df0f8806f4df808056e9136b3d820af8dd5b6e7591c27a0f5f6258f0e21.exe AppLaunch.exe PID 2168 wrote to memory of 1452 2168 b7d67df0f8806f4df808056e9136b3d820af8dd5b6e7591c27a0f5f6258f0e21.exe AppLaunch.exe PID 2168 wrote to memory of 1452 2168 b7d67df0f8806f4df808056e9136b3d820af8dd5b6e7591c27a0f5f6258f0e21.exe AppLaunch.exe PID 2168 wrote to memory of 1452 2168 b7d67df0f8806f4df808056e9136b3d820af8dd5b6e7591c27a0f5f6258f0e21.exe AppLaunch.exe PID 2168 wrote to memory of 1452 2168 b7d67df0f8806f4df808056e9136b3d820af8dd5b6e7591c27a0f5f6258f0e21.exe AppLaunch.exe PID 2168 wrote to memory of 1452 2168 b7d67df0f8806f4df808056e9136b3d820af8dd5b6e7591c27a0f5f6258f0e21.exe AppLaunch.exe PID 2168 wrote to memory of 1452 2168 b7d67df0f8806f4df808056e9136b3d820af8dd5b6e7591c27a0f5f6258f0e21.exe AppLaunch.exe PID 2168 wrote to memory of 2408 2168 b7d67df0f8806f4df808056e9136b3d820af8dd5b6e7591c27a0f5f6258f0e21.exe AppLaunch.exe PID 2168 wrote to memory of 2408 2168 b7d67df0f8806f4df808056e9136b3d820af8dd5b6e7591c27a0f5f6258f0e21.exe AppLaunch.exe PID 2168 wrote to memory of 2408 2168 b7d67df0f8806f4df808056e9136b3d820af8dd5b6e7591c27a0f5f6258f0e21.exe AppLaunch.exe PID 2168 wrote to memory of 2408 2168 b7d67df0f8806f4df808056e9136b3d820af8dd5b6e7591c27a0f5f6258f0e21.exe AppLaunch.exe PID 2168 wrote to memory of 2408 2168 b7d67df0f8806f4df808056e9136b3d820af8dd5b6e7591c27a0f5f6258f0e21.exe AppLaunch.exe PID 2168 wrote to memory of 2408 2168 b7d67df0f8806f4df808056e9136b3d820af8dd5b6e7591c27a0f5f6258f0e21.exe AppLaunch.exe PID 2168 wrote to memory of 2408 2168 b7d67df0f8806f4df808056e9136b3d820af8dd5b6e7591c27a0f5f6258f0e21.exe AppLaunch.exe PID 2168 wrote to memory of 2408 2168 b7d67df0f8806f4df808056e9136b3d820af8dd5b6e7591c27a0f5f6258f0e21.exe AppLaunch.exe PID 2168 wrote to memory of 2408 2168 b7d67df0f8806f4df808056e9136b3d820af8dd5b6e7591c27a0f5f6258f0e21.exe AppLaunch.exe PID 2168 wrote to memory of 2408 2168 b7d67df0f8806f4df808056e9136b3d820af8dd5b6e7591c27a0f5f6258f0e21.exe AppLaunch.exe
Processes
-
C:\Users\Admin\AppData\Local\Temp\b7d67df0f8806f4df808056e9136b3d820af8dd5b6e7591c27a0f5f6258f0e21.exe"C:\Users\Admin\AppData\Local\Temp\b7d67df0f8806f4df808056e9136b3d820af8dd5b6e7591c27a0f5f6258f0e21.exe"1⤵
- Adds Run key to start application
- Suspicious use of SetThreadContext
- Suspicious behavior: EnumeratesProcesses
- Suspicious use of AdjustPrivilegeToken
- Suspicious use of WriteProcessMemory
PID:2168 -
C:\Windows\SysWOW64\CMD.exe"CMD"2⤵PID:3768
-
-
C:\Windows\SysWOW64\CMD.exe"CMD"2⤵PID:5008
-
-
C:\Windows\Microsoft.NET\Framework\v2.0.50727\AppLaunch.exe"C:\Windows\Microsoft.NET\Framework\v2.0.50727\\AppLaunch.exe"2⤵PID:1452
-
-
C:\Windows\Microsoft.NET\Framework\v2.0.50727\AppLaunch.exe"C:\Windows\Microsoft.NET\Framework\v2.0.50727\\AppLaunch.exe"2⤵PID:2408
-