Analysis
-
max time kernel
332s -
max time network
343s -
platform
windows10-2004_x64 -
resource
win10v2004-20221111-en -
resource tags
arch:x64arch:x86image:win10v2004-20221111-enlocale:en-usos:windows10-2004-x64system -
submitted
27-11-2022 01:37
Static task
static1
Behavioral task
behavioral1
Sample
ba7493b37a3f341c4af47f07c02f261526fe180247fdd48b3060fccd438ed157.exe
Resource
win7-20221111-en
Behavioral task
behavioral2
Sample
ba7493b37a3f341c4af47f07c02f261526fe180247fdd48b3060fccd438ed157.exe
Resource
win10v2004-20221111-en
General
-
Target
ba7493b37a3f341c4af47f07c02f261526fe180247fdd48b3060fccd438ed157.exe
-
Size
598KB
-
MD5
988c93c1604be2107921463122471e5c
-
SHA1
5267b6437962f8360dbfb910498a46cae63b19a9
-
SHA256
ba7493b37a3f341c4af47f07c02f261526fe180247fdd48b3060fccd438ed157
-
SHA512
591d3908d6ea6f6d8c543f0c3b346ff5508803c5c8dc9b3046341e5c35890c80458ce54d88dbb005f7c8f5b7aeff28b60204bca7bfda5fb4dda76120421420eb
-
SSDEEP
12288:yeFSHA02FWBtTsEsfoOYxdY1TQT1t6AIlZu13AL:yAS6WrA9fo38TC1tJ9U
Malware Config
Signatures
-
Checks computer location settings 2 TTPs 1 IoCs
Looks up country code configured in the registry, likely geofence.
Processes:
ba7493b37a3f341c4af47f07c02f261526fe180247fdd48b3060fccd438ed157.exedescription ioc process Key value queried \REGISTRY\USER\S-1-5-21-2971393436-602173351-1645505021-1000\Control Panel\International\Geo\Nation ba7493b37a3f341c4af47f07c02f261526fe180247fdd48b3060fccd438ed157.exe -
Suspicious use of SetThreadContext 1 IoCs
Processes:
ba7493b37a3f341c4af47f07c02f261526fe180247fdd48b3060fccd438ed157.exedescription pid process target process PID 2388 set thread context of 5024 2388 ba7493b37a3f341c4af47f07c02f261526fe180247fdd48b3060fccd438ed157.exe ba7493b37a3f341c4af47f07c02f261526fe180247fdd48b3060fccd438ed157.exe -
Enumerates physical storage devices 1 TTPs
Attempts to interact with connected storage/optical drive(s). Likely ransomware behaviour.
-
Runs ping.exe 1 TTPs 1 IoCs
-
Suspicious behavior: EnumeratesProcesses 4 IoCs
Processes:
ba7493b37a3f341c4af47f07c02f261526fe180247fdd48b3060fccd438ed157.exepid process 2388 ba7493b37a3f341c4af47f07c02f261526fe180247fdd48b3060fccd438ed157.exe 2388 ba7493b37a3f341c4af47f07c02f261526fe180247fdd48b3060fccd438ed157.exe 2388 ba7493b37a3f341c4af47f07c02f261526fe180247fdd48b3060fccd438ed157.exe 2388 ba7493b37a3f341c4af47f07c02f261526fe180247fdd48b3060fccd438ed157.exe -
Suspicious use of AdjustPrivilegeToken 1 IoCs
Processes:
ba7493b37a3f341c4af47f07c02f261526fe180247fdd48b3060fccd438ed157.exedescription pid process Token: SeDebugPrivilege 2388 ba7493b37a3f341c4af47f07c02f261526fe180247fdd48b3060fccd438ed157.exe -
Suspicious use of WriteProcessMemory 20 IoCs
Processes:
ba7493b37a3f341c4af47f07c02f261526fe180247fdd48b3060fccd438ed157.execmd.exedescription pid process target process PID 2388 wrote to memory of 1320 2388 ba7493b37a3f341c4af47f07c02f261526fe180247fdd48b3060fccd438ed157.exe cmd.exe PID 2388 wrote to memory of 1320 2388 ba7493b37a3f341c4af47f07c02f261526fe180247fdd48b3060fccd438ed157.exe cmd.exe PID 2388 wrote to memory of 1320 2388 ba7493b37a3f341c4af47f07c02f261526fe180247fdd48b3060fccd438ed157.exe cmd.exe PID 1320 wrote to memory of 1488 1320 cmd.exe PING.EXE PID 1320 wrote to memory of 1488 1320 cmd.exe PING.EXE PID 1320 wrote to memory of 1488 1320 cmd.exe PING.EXE PID 2388 wrote to memory of 1944 2388 ba7493b37a3f341c4af47f07c02f261526fe180247fdd48b3060fccd438ed157.exe ba7493b37a3f341c4af47f07c02f261526fe180247fdd48b3060fccd438ed157.exe PID 2388 wrote to memory of 1944 2388 ba7493b37a3f341c4af47f07c02f261526fe180247fdd48b3060fccd438ed157.exe ba7493b37a3f341c4af47f07c02f261526fe180247fdd48b3060fccd438ed157.exe PID 2388 wrote to memory of 1944 2388 ba7493b37a3f341c4af47f07c02f261526fe180247fdd48b3060fccd438ed157.exe ba7493b37a3f341c4af47f07c02f261526fe180247fdd48b3060fccd438ed157.exe PID 2388 wrote to memory of 2584 2388 ba7493b37a3f341c4af47f07c02f261526fe180247fdd48b3060fccd438ed157.exe ba7493b37a3f341c4af47f07c02f261526fe180247fdd48b3060fccd438ed157.exe PID 2388 wrote to memory of 2584 2388 ba7493b37a3f341c4af47f07c02f261526fe180247fdd48b3060fccd438ed157.exe ba7493b37a3f341c4af47f07c02f261526fe180247fdd48b3060fccd438ed157.exe PID 2388 wrote to memory of 2584 2388 ba7493b37a3f341c4af47f07c02f261526fe180247fdd48b3060fccd438ed157.exe ba7493b37a3f341c4af47f07c02f261526fe180247fdd48b3060fccd438ed157.exe PID 2388 wrote to memory of 5024 2388 ba7493b37a3f341c4af47f07c02f261526fe180247fdd48b3060fccd438ed157.exe ba7493b37a3f341c4af47f07c02f261526fe180247fdd48b3060fccd438ed157.exe PID 2388 wrote to memory of 5024 2388 ba7493b37a3f341c4af47f07c02f261526fe180247fdd48b3060fccd438ed157.exe ba7493b37a3f341c4af47f07c02f261526fe180247fdd48b3060fccd438ed157.exe PID 2388 wrote to memory of 5024 2388 ba7493b37a3f341c4af47f07c02f261526fe180247fdd48b3060fccd438ed157.exe ba7493b37a3f341c4af47f07c02f261526fe180247fdd48b3060fccd438ed157.exe PID 2388 wrote to memory of 5024 2388 ba7493b37a3f341c4af47f07c02f261526fe180247fdd48b3060fccd438ed157.exe ba7493b37a3f341c4af47f07c02f261526fe180247fdd48b3060fccd438ed157.exe PID 2388 wrote to memory of 5024 2388 ba7493b37a3f341c4af47f07c02f261526fe180247fdd48b3060fccd438ed157.exe ba7493b37a3f341c4af47f07c02f261526fe180247fdd48b3060fccd438ed157.exe PID 2388 wrote to memory of 5024 2388 ba7493b37a3f341c4af47f07c02f261526fe180247fdd48b3060fccd438ed157.exe ba7493b37a3f341c4af47f07c02f261526fe180247fdd48b3060fccd438ed157.exe PID 2388 wrote to memory of 5024 2388 ba7493b37a3f341c4af47f07c02f261526fe180247fdd48b3060fccd438ed157.exe ba7493b37a3f341c4af47f07c02f261526fe180247fdd48b3060fccd438ed157.exe PID 2388 wrote to memory of 5024 2388 ba7493b37a3f341c4af47f07c02f261526fe180247fdd48b3060fccd438ed157.exe ba7493b37a3f341c4af47f07c02f261526fe180247fdd48b3060fccd438ed157.exe
Processes
-
C:\Users\Admin\AppData\Local\Temp\ba7493b37a3f341c4af47f07c02f261526fe180247fdd48b3060fccd438ed157.exe"C:\Users\Admin\AppData\Local\Temp\ba7493b37a3f341c4af47f07c02f261526fe180247fdd48b3060fccd438ed157.exe"1⤵
- Checks computer location settings
- Suspicious use of SetThreadContext
- Suspicious behavior: EnumeratesProcesses
- Suspicious use of AdjustPrivilegeToken
- Suspicious use of WriteProcessMemory
PID:2388 -
C:\Windows\SysWOW64\cmd.exe"C:\Windows\System32\cmd.exe" /c PING 127.0.0.1 -n 10 > nul2⤵
- Suspicious use of WriteProcessMemory
PID:1320 -
C:\Windows\SysWOW64\PING.EXEPING 127.0.0.1 -n 103⤵
- Runs ping.exe
PID:1488
-
-
-
C:\Users\Admin\AppData\Local\Temp\ba7493b37a3f341c4af47f07c02f261526fe180247fdd48b3060fccd438ed157.exe"C:\Users\Admin\AppData\Local\Temp\ba7493b37a3f341c4af47f07c02f261526fe180247fdd48b3060fccd438ed157.exe"2⤵PID:1944
-
-
C:\Users\Admin\AppData\Local\Temp\ba7493b37a3f341c4af47f07c02f261526fe180247fdd48b3060fccd438ed157.exe"C:\Users\Admin\AppData\Local\Temp\ba7493b37a3f341c4af47f07c02f261526fe180247fdd48b3060fccd438ed157.exe"2⤵PID:2584
-
-
C:\Users\Admin\AppData\Local\Temp\ba7493b37a3f341c4af47f07c02f261526fe180247fdd48b3060fccd438ed157.exe"C:\Users\Admin\AppData\Local\Temp\ba7493b37a3f341c4af47f07c02f261526fe180247fdd48b3060fccd438ed157.exe"2⤵PID:5024
-