Analysis
-
max time kernel
10s -
max time network
46s -
platform
windows7_x64 -
resource
win7-20220812-en -
resource tags
arch:x64arch:x86image:win7-20220812-enlocale:en-usos:windows7-x64system -
submitted
11-10-2022 10:29
Static task
static1
Behavioral task
behavioral1
Sample
b9c8ef3c820080cd331e1e638fdd2204b49feff98f5f6c785d721360f4fcbddf.exe
Resource
win7-20220812-en
Behavioral task
behavioral2
Sample
b9c8ef3c820080cd331e1e638fdd2204b49feff98f5f6c785d721360f4fcbddf.exe
Resource
win10v2004-20220812-en
General
-
Target
b9c8ef3c820080cd331e1e638fdd2204b49feff98f5f6c785d721360f4fcbddf.exe
-
Size
24KB
-
MD5
001e69cbf0dfdba1924d31e55218d470
-
SHA1
8669fa317f69ac01b47d15ec19f17abc1f3dcebc
-
SHA256
b9c8ef3c820080cd331e1e638fdd2204b49feff98f5f6c785d721360f4fcbddf
-
SHA512
7c5e9feaaa995ae7233511316a3213644f93aa9c20408ac4b89317f1eae76889a09d1557b17117b2331aee2680988b0302b9123c406af197f5cecdf448f8f797
-
SSDEEP
384:FzgXWeJY7mBqoWcdpWRVvZXoCRh2prqCGa7YWuSXdZXKbUWShywdND:deK7mkC2Xh2p1GasWVXzfh/
Malware Config
Signatures
-
Drops file in System32 directory 1 IoCs
description ioc Process File opened for modification C:\WINDOWS\SysWOW64\REGEDIT.EXE b9c8ef3c820080cd331e1e638fdd2204b49feff98f5f6c785d721360f4fcbddf.exe -
Enumerates physical storage devices 1 TTPs
Attempts to interact with connected storage/optical drive(s). Likely ransomware behaviour.
-
Suspicious behavior: EnumeratesProcesses 1 IoCs
pid Process 304 b9c8ef3c820080cd331e1e638fdd2204b49feff98f5f6c785d721360f4fcbddf.exe -
Suspicious behavior: MapViewOfSection 21 IoCs
pid Process 304 b9c8ef3c820080cd331e1e638fdd2204b49feff98f5f6c785d721360f4fcbddf.exe 304 b9c8ef3c820080cd331e1e638fdd2204b49feff98f5f6c785d721360f4fcbddf.exe 304 b9c8ef3c820080cd331e1e638fdd2204b49feff98f5f6c785d721360f4fcbddf.exe 304 b9c8ef3c820080cd331e1e638fdd2204b49feff98f5f6c785d721360f4fcbddf.exe 304 b9c8ef3c820080cd331e1e638fdd2204b49feff98f5f6c785d721360f4fcbddf.exe 304 b9c8ef3c820080cd331e1e638fdd2204b49feff98f5f6c785d721360f4fcbddf.exe 304 b9c8ef3c820080cd331e1e638fdd2204b49feff98f5f6c785d721360f4fcbddf.exe 304 b9c8ef3c820080cd331e1e638fdd2204b49feff98f5f6c785d721360f4fcbddf.exe 304 b9c8ef3c820080cd331e1e638fdd2204b49feff98f5f6c785d721360f4fcbddf.exe 304 b9c8ef3c820080cd331e1e638fdd2204b49feff98f5f6c785d721360f4fcbddf.exe 304 b9c8ef3c820080cd331e1e638fdd2204b49feff98f5f6c785d721360f4fcbddf.exe 304 b9c8ef3c820080cd331e1e638fdd2204b49feff98f5f6c785d721360f4fcbddf.exe 304 b9c8ef3c820080cd331e1e638fdd2204b49feff98f5f6c785d721360f4fcbddf.exe 304 b9c8ef3c820080cd331e1e638fdd2204b49feff98f5f6c785d721360f4fcbddf.exe 304 b9c8ef3c820080cd331e1e638fdd2204b49feff98f5f6c785d721360f4fcbddf.exe 304 b9c8ef3c820080cd331e1e638fdd2204b49feff98f5f6c785d721360f4fcbddf.exe 304 b9c8ef3c820080cd331e1e638fdd2204b49feff98f5f6c785d721360f4fcbddf.exe 304 b9c8ef3c820080cd331e1e638fdd2204b49feff98f5f6c785d721360f4fcbddf.exe 304 b9c8ef3c820080cd331e1e638fdd2204b49feff98f5f6c785d721360f4fcbddf.exe 304 b9c8ef3c820080cd331e1e638fdd2204b49feff98f5f6c785d721360f4fcbddf.exe 304 b9c8ef3c820080cd331e1e638fdd2204b49feff98f5f6c785d721360f4fcbddf.exe -
Suspicious use of AdjustPrivilegeToken 5 IoCs
description pid Process Token: SeDebugPrivilege 304 b9c8ef3c820080cd331e1e638fdd2204b49feff98f5f6c785d721360f4fcbddf.exe Token: SeTakeOwnershipPrivilege 304 b9c8ef3c820080cd331e1e638fdd2204b49feff98f5f6c785d721360f4fcbddf.exe Token: SeRestorePrivilege 304 b9c8ef3c820080cd331e1e638fdd2204b49feff98f5f6c785d721360f4fcbddf.exe Token: SeBackupPrivilege 304 b9c8ef3c820080cd331e1e638fdd2204b49feff98f5f6c785d721360f4fcbddf.exe Token: SeChangeNotifyPrivilege 304 b9c8ef3c820080cd331e1e638fdd2204b49feff98f5f6c785d721360f4fcbddf.exe -
Suspicious use of WriteProcessMemory 64 IoCs
description pid Process procid_target PID 304 wrote to memory of 368 304 b9c8ef3c820080cd331e1e638fdd2204b49feff98f5f6c785d721360f4fcbddf.exe 5 PID 304 wrote to memory of 368 304 b9c8ef3c820080cd331e1e638fdd2204b49feff98f5f6c785d721360f4fcbddf.exe 5 PID 304 wrote to memory of 368 304 b9c8ef3c820080cd331e1e638fdd2204b49feff98f5f6c785d721360f4fcbddf.exe 5 PID 304 wrote to memory of 368 304 b9c8ef3c820080cd331e1e638fdd2204b49feff98f5f6c785d721360f4fcbddf.exe 5 PID 304 wrote to memory of 368 304 b9c8ef3c820080cd331e1e638fdd2204b49feff98f5f6c785d721360f4fcbddf.exe 5 PID 304 wrote to memory of 368 304 b9c8ef3c820080cd331e1e638fdd2204b49feff98f5f6c785d721360f4fcbddf.exe 5 PID 304 wrote to memory of 376 304 b9c8ef3c820080cd331e1e638fdd2204b49feff98f5f6c785d721360f4fcbddf.exe 4 PID 304 wrote to memory of 376 304 b9c8ef3c820080cd331e1e638fdd2204b49feff98f5f6c785d721360f4fcbddf.exe 4 PID 304 wrote to memory of 376 304 b9c8ef3c820080cd331e1e638fdd2204b49feff98f5f6c785d721360f4fcbddf.exe 4 PID 304 wrote to memory of 376 304 b9c8ef3c820080cd331e1e638fdd2204b49feff98f5f6c785d721360f4fcbddf.exe 4 PID 304 wrote to memory of 376 304 b9c8ef3c820080cd331e1e638fdd2204b49feff98f5f6c785d721360f4fcbddf.exe 4 PID 304 wrote to memory of 376 304 b9c8ef3c820080cd331e1e638fdd2204b49feff98f5f6c785d721360f4fcbddf.exe 4 PID 304 wrote to memory of 416 304 b9c8ef3c820080cd331e1e638fdd2204b49feff98f5f6c785d721360f4fcbddf.exe 3 PID 304 wrote to memory of 416 304 b9c8ef3c820080cd331e1e638fdd2204b49feff98f5f6c785d721360f4fcbddf.exe 3 PID 304 wrote to memory of 416 304 b9c8ef3c820080cd331e1e638fdd2204b49feff98f5f6c785d721360f4fcbddf.exe 3 PID 304 wrote to memory of 416 304 b9c8ef3c820080cd331e1e638fdd2204b49feff98f5f6c785d721360f4fcbddf.exe 3 PID 304 wrote to memory of 416 304 b9c8ef3c820080cd331e1e638fdd2204b49feff98f5f6c785d721360f4fcbddf.exe 3 PID 304 wrote to memory of 416 304 b9c8ef3c820080cd331e1e638fdd2204b49feff98f5f6c785d721360f4fcbddf.exe 3 PID 304 wrote to memory of 460 304 b9c8ef3c820080cd331e1e638fdd2204b49feff98f5f6c785d721360f4fcbddf.exe 2 PID 304 wrote to memory of 460 304 b9c8ef3c820080cd331e1e638fdd2204b49feff98f5f6c785d721360f4fcbddf.exe 2 PID 304 wrote to memory of 460 304 b9c8ef3c820080cd331e1e638fdd2204b49feff98f5f6c785d721360f4fcbddf.exe 2 PID 304 wrote to memory of 460 304 b9c8ef3c820080cd331e1e638fdd2204b49feff98f5f6c785d721360f4fcbddf.exe 2 PID 304 wrote to memory of 460 304 b9c8ef3c820080cd331e1e638fdd2204b49feff98f5f6c785d721360f4fcbddf.exe 2 PID 304 wrote to memory of 460 304 b9c8ef3c820080cd331e1e638fdd2204b49feff98f5f6c785d721360f4fcbddf.exe 2 PID 304 wrote to memory of 476 304 b9c8ef3c820080cd331e1e638fdd2204b49feff98f5f6c785d721360f4fcbddf.exe 1 PID 304 wrote to memory of 476 304 b9c8ef3c820080cd331e1e638fdd2204b49feff98f5f6c785d721360f4fcbddf.exe 1 PID 304 wrote to memory of 476 304 b9c8ef3c820080cd331e1e638fdd2204b49feff98f5f6c785d721360f4fcbddf.exe 1 PID 304 wrote to memory of 476 304 b9c8ef3c820080cd331e1e638fdd2204b49feff98f5f6c785d721360f4fcbddf.exe 1 PID 304 wrote to memory of 476 304 b9c8ef3c820080cd331e1e638fdd2204b49feff98f5f6c785d721360f4fcbddf.exe 1 PID 304 wrote to memory of 476 304 b9c8ef3c820080cd331e1e638fdd2204b49feff98f5f6c785d721360f4fcbddf.exe 1 PID 304 wrote to memory of 484 304 b9c8ef3c820080cd331e1e638fdd2204b49feff98f5f6c785d721360f4fcbddf.exe 8 PID 304 wrote to memory of 484 304 b9c8ef3c820080cd331e1e638fdd2204b49feff98f5f6c785d721360f4fcbddf.exe 8 PID 304 wrote to memory of 484 304 b9c8ef3c820080cd331e1e638fdd2204b49feff98f5f6c785d721360f4fcbddf.exe 8 PID 304 wrote to memory of 484 304 b9c8ef3c820080cd331e1e638fdd2204b49feff98f5f6c785d721360f4fcbddf.exe 8 PID 304 wrote to memory of 484 304 b9c8ef3c820080cd331e1e638fdd2204b49feff98f5f6c785d721360f4fcbddf.exe 8 PID 304 wrote to memory of 484 304 b9c8ef3c820080cd331e1e638fdd2204b49feff98f5f6c785d721360f4fcbddf.exe 8 PID 304 wrote to memory of 576 304 b9c8ef3c820080cd331e1e638fdd2204b49feff98f5f6c785d721360f4fcbddf.exe 26 PID 304 wrote to memory of 576 304 b9c8ef3c820080cd331e1e638fdd2204b49feff98f5f6c785d721360f4fcbddf.exe 26 PID 304 wrote to memory of 576 304 b9c8ef3c820080cd331e1e638fdd2204b49feff98f5f6c785d721360f4fcbddf.exe 26 PID 304 wrote to memory of 576 304 b9c8ef3c820080cd331e1e638fdd2204b49feff98f5f6c785d721360f4fcbddf.exe 26 PID 304 wrote to memory of 576 304 b9c8ef3c820080cd331e1e638fdd2204b49feff98f5f6c785d721360f4fcbddf.exe 26 PID 304 wrote to memory of 576 304 b9c8ef3c820080cd331e1e638fdd2204b49feff98f5f6c785d721360f4fcbddf.exe 26 PID 304 wrote to memory of 652 304 b9c8ef3c820080cd331e1e638fdd2204b49feff98f5f6c785d721360f4fcbddf.exe 25 PID 304 wrote to memory of 652 304 b9c8ef3c820080cd331e1e638fdd2204b49feff98f5f6c785d721360f4fcbddf.exe 25 PID 304 wrote to memory of 652 304 b9c8ef3c820080cd331e1e638fdd2204b49feff98f5f6c785d721360f4fcbddf.exe 25 PID 304 wrote to memory of 652 304 b9c8ef3c820080cd331e1e638fdd2204b49feff98f5f6c785d721360f4fcbddf.exe 25 PID 304 wrote to memory of 652 304 b9c8ef3c820080cd331e1e638fdd2204b49feff98f5f6c785d721360f4fcbddf.exe 25 PID 304 wrote to memory of 652 304 b9c8ef3c820080cd331e1e638fdd2204b49feff98f5f6c785d721360f4fcbddf.exe 25 PID 304 wrote to memory of 732 304 b9c8ef3c820080cd331e1e638fdd2204b49feff98f5f6c785d721360f4fcbddf.exe 24 PID 304 wrote to memory of 732 304 b9c8ef3c820080cd331e1e638fdd2204b49feff98f5f6c785d721360f4fcbddf.exe 24 PID 304 wrote to memory of 732 304 b9c8ef3c820080cd331e1e638fdd2204b49feff98f5f6c785d721360f4fcbddf.exe 24 PID 304 wrote to memory of 732 304 b9c8ef3c820080cd331e1e638fdd2204b49feff98f5f6c785d721360f4fcbddf.exe 24 PID 304 wrote to memory of 732 304 b9c8ef3c820080cd331e1e638fdd2204b49feff98f5f6c785d721360f4fcbddf.exe 24 PID 304 wrote to memory of 732 304 b9c8ef3c820080cd331e1e638fdd2204b49feff98f5f6c785d721360f4fcbddf.exe 24 PID 304 wrote to memory of 796 304 b9c8ef3c820080cd331e1e638fdd2204b49feff98f5f6c785d721360f4fcbddf.exe 23 PID 304 wrote to memory of 796 304 b9c8ef3c820080cd331e1e638fdd2204b49feff98f5f6c785d721360f4fcbddf.exe 23 PID 304 wrote to memory of 796 304 b9c8ef3c820080cd331e1e638fdd2204b49feff98f5f6c785d721360f4fcbddf.exe 23 PID 304 wrote to memory of 796 304 b9c8ef3c820080cd331e1e638fdd2204b49feff98f5f6c785d721360f4fcbddf.exe 23 PID 304 wrote to memory of 796 304 b9c8ef3c820080cd331e1e638fdd2204b49feff98f5f6c785d721360f4fcbddf.exe 23 PID 304 wrote to memory of 796 304 b9c8ef3c820080cd331e1e638fdd2204b49feff98f5f6c785d721360f4fcbddf.exe 23 PID 304 wrote to memory of 844 304 b9c8ef3c820080cd331e1e638fdd2204b49feff98f5f6c785d721360f4fcbddf.exe 22 PID 304 wrote to memory of 844 304 b9c8ef3c820080cd331e1e638fdd2204b49feff98f5f6c785d721360f4fcbddf.exe 22 PID 304 wrote to memory of 844 304 b9c8ef3c820080cd331e1e638fdd2204b49feff98f5f6c785d721360f4fcbddf.exe 22 PID 304 wrote to memory of 844 304 b9c8ef3c820080cd331e1e638fdd2204b49feff98f5f6c785d721360f4fcbddf.exe 22
Processes
-
C:\Windows\system32\lsass.exeC:\Windows\system32\lsass.exe1⤵PID:476
-
C:\Windows\system32\services.exeC:\Windows\system32\services.exe1⤵PID:460
-
C:\Windows\system32\sppsvc.exeC:\Windows\system32\sppsvc.exe2⤵PID:1676
-
-
C:\Windows\system32\svchost.exeC:\Windows\system32\svchost.exe -k LocalServiceAndNoImpersonation2⤵PID:1512
-
-
C:\Windows\system32\taskhost.exe"taskhost.exe"2⤵PID:1260
-
-
C:\Windows\system32\svchost.exeC:\Windows\system32\svchost.exe -k LocalServiceNoNetwork2⤵PID:1032
-
-
C:\Windows\System32\spoolsv.exeC:\Windows\System32\spoolsv.exe2⤵PID:276
-
-
C:\Windows\system32\svchost.exeC:\Windows\system32\svchost.exe -k NetworkService2⤵PID:300
-
-
C:\Windows\system32\svchost.exeC:\Windows\system32\svchost.exe -k netsvcs2⤵PID:872
-
-
C:\Windows\system32\svchost.exeC:\Windows\system32\svchost.exe -k LocalService2⤵PID:844
-
-
C:\Windows\System32\svchost.exeC:\Windows\System32\svchost.exe -k LocalSystemNetworkRestricted2⤵PID:796
-
-
C:\Windows\System32\svchost.exeC:\Windows\System32\svchost.exe -k LocalServiceNetworkRestricted2⤵PID:732
-
-
C:\Windows\system32\svchost.exeC:\Windows\system32\svchost.exe -k RPCSS2⤵PID:652
-
-
C:\Windows\system32\svchost.exeC:\Windows\system32\svchost.exe -k DcomLaunch2⤵PID:576
-
-
C:\Windows\system32\winlogon.exewinlogon.exe1⤵PID:416
-
C:\Windows\system32\csrss.exe%SystemRoot%\system32\csrss.exe ObjectDirectory=\Windows SharedSection=1024,20480,768 Windows=On SubSystemType=Windows ServerDll=basesrv,1 ServerDll=winsrv:UserServerDllInitialization,3 ServerDll=winsrv:ConServerDllInitialization,2 ServerDll=sxssrv,4 ProfileControl=Off MaxRequestThreads=161⤵PID:376
-
C:\Windows\system32\wininit.exewininit.exe1⤵PID:368
-
C:\Windows\system32\lsm.exeC:\Windows\system32\lsm.exe2⤵PID:484
-
-
\\?\C:\Windows\system32\wbem\WMIADAP.EXEwmiadap.exe /F /T /R1⤵PID:1088
-
C:\Windows\Explorer.EXEC:\Windows\Explorer.EXE1⤵PID:1420
-
C:\Users\Admin\AppData\Local\Temp\b9c8ef3c820080cd331e1e638fdd2204b49feff98f5f6c785d721360f4fcbddf.exe"C:\Users\Admin\AppData\Local\Temp\b9c8ef3c820080cd331e1e638fdd2204b49feff98f5f6c785d721360f4fcbddf.exe"2⤵
- Drops file in System32 directory
- Suspicious behavior: EnumeratesProcesses
- Suspicious behavior: MapViewOfSection
- Suspicious use of AdjustPrivilegeToken
- Suspicious use of WriteProcessMemory
PID:304
-
-
C:\Windows\system32\Dwm.exe"C:\Windows\system32\Dwm.exe"1⤵PID:1364