Analysis
-
max time kernel
94s -
max time network
147s -
platform
windows10-2004_x64 -
resource
win10v2004-20240611-en -
resource tags
arch:x64arch:x86image:win10v2004-20240611-enlocale:en-usos:windows10-2004-x64system -
submitted
14-06-2024 04:51
Static task
static1
Behavioral task
behavioral1
Sample
dba8c30c30c1a9b9d98ebf8bfe7a6385eb24c844be6c10fd4a496ebc1d4736fd.exe
Resource
win7-20240419-en
Behavioral task
behavioral2
Sample
dba8c30c30c1a9b9d98ebf8bfe7a6385eb24c844be6c10fd4a496ebc1d4736fd.exe
Resource
win10v2004-20240611-en
General
-
Target
dba8c30c30c1a9b9d98ebf8bfe7a6385eb24c844be6c10fd4a496ebc1d4736fd.exe
-
Size
846KB
-
MD5
00620b3b6eac51d742e2c3fa65e32745
-
SHA1
0565981aa138aa726de0bc30ab22f6387f7c65ad
-
SHA256
dba8c30c30c1a9b9d98ebf8bfe7a6385eb24c844be6c10fd4a496ebc1d4736fd
-
SHA512
338e4fb591c192c822c858d174b0b08a045741966804dd6ebbed2e4dd23fdb303b8bf039ef3b535bcc94fa8ad1bb243db59ea81f4ed0adcd5ac31cab6a7567b9
-
SSDEEP
24576:0AHnh+eWsN3skA4RV1Hom2KXMmHaL9D5:Dh+ZkldoPK8YaLH
Malware Config
Signatures
-
Checks computer location settings 2 TTPs 1 IoCs
Looks up country code configured in the registry, likely geofence.
description ioc Process Key value queried \REGISTRY\USER\S-1-5-21-3169499791-3545231813-3156325206-1000\Control Panel\International\Geo\Nation dba8c30c30c1a9b9d98ebf8bfe7a6385eb24c844be6c10fd4a496ebc1d4736fd.exe -
Enumerates physical storage devices 1 TTPs
Attempts to interact with connected storage/optical drive(s).
-
Suspicious behavior: EnumeratesProcesses 2 IoCs
pid Process 4072 powershell.exe 4072 powershell.exe -
Suspicious use of AdjustPrivilegeToken 1 IoCs
description pid Process Token: SeDebugPrivilege 4072 powershell.exe -
Suspicious use of FindShellTrayWindow 25 IoCs
pid Process 5096 dba8c30c30c1a9b9d98ebf8bfe7a6385eb24c844be6c10fd4a496ebc1d4736fd.exe 5096 dba8c30c30c1a9b9d98ebf8bfe7a6385eb24c844be6c10fd4a496ebc1d4736fd.exe 5096 dba8c30c30c1a9b9d98ebf8bfe7a6385eb24c844be6c10fd4a496ebc1d4736fd.exe 5096 dba8c30c30c1a9b9d98ebf8bfe7a6385eb24c844be6c10fd4a496ebc1d4736fd.exe 5096 dba8c30c30c1a9b9d98ebf8bfe7a6385eb24c844be6c10fd4a496ebc1d4736fd.exe 5096 dba8c30c30c1a9b9d98ebf8bfe7a6385eb24c844be6c10fd4a496ebc1d4736fd.exe 5096 dba8c30c30c1a9b9d98ebf8bfe7a6385eb24c844be6c10fd4a496ebc1d4736fd.exe 5096 dba8c30c30c1a9b9d98ebf8bfe7a6385eb24c844be6c10fd4a496ebc1d4736fd.exe 5096 dba8c30c30c1a9b9d98ebf8bfe7a6385eb24c844be6c10fd4a496ebc1d4736fd.exe 5096 dba8c30c30c1a9b9d98ebf8bfe7a6385eb24c844be6c10fd4a496ebc1d4736fd.exe 5096 dba8c30c30c1a9b9d98ebf8bfe7a6385eb24c844be6c10fd4a496ebc1d4736fd.exe 5096 dba8c30c30c1a9b9d98ebf8bfe7a6385eb24c844be6c10fd4a496ebc1d4736fd.exe 5096 dba8c30c30c1a9b9d98ebf8bfe7a6385eb24c844be6c10fd4a496ebc1d4736fd.exe 5096 dba8c30c30c1a9b9d98ebf8bfe7a6385eb24c844be6c10fd4a496ebc1d4736fd.exe 5096 dba8c30c30c1a9b9d98ebf8bfe7a6385eb24c844be6c10fd4a496ebc1d4736fd.exe 5096 dba8c30c30c1a9b9d98ebf8bfe7a6385eb24c844be6c10fd4a496ebc1d4736fd.exe 5096 dba8c30c30c1a9b9d98ebf8bfe7a6385eb24c844be6c10fd4a496ebc1d4736fd.exe 5096 dba8c30c30c1a9b9d98ebf8bfe7a6385eb24c844be6c10fd4a496ebc1d4736fd.exe 5096 dba8c30c30c1a9b9d98ebf8bfe7a6385eb24c844be6c10fd4a496ebc1d4736fd.exe 5096 dba8c30c30c1a9b9d98ebf8bfe7a6385eb24c844be6c10fd4a496ebc1d4736fd.exe 5096 dba8c30c30c1a9b9d98ebf8bfe7a6385eb24c844be6c10fd4a496ebc1d4736fd.exe 5096 dba8c30c30c1a9b9d98ebf8bfe7a6385eb24c844be6c10fd4a496ebc1d4736fd.exe 5096 dba8c30c30c1a9b9d98ebf8bfe7a6385eb24c844be6c10fd4a496ebc1d4736fd.exe 5096 dba8c30c30c1a9b9d98ebf8bfe7a6385eb24c844be6c10fd4a496ebc1d4736fd.exe 5096 dba8c30c30c1a9b9d98ebf8bfe7a6385eb24c844be6c10fd4a496ebc1d4736fd.exe -
Suspicious use of SendNotifyMessage 25 IoCs
pid Process 5096 dba8c30c30c1a9b9d98ebf8bfe7a6385eb24c844be6c10fd4a496ebc1d4736fd.exe 5096 dba8c30c30c1a9b9d98ebf8bfe7a6385eb24c844be6c10fd4a496ebc1d4736fd.exe 5096 dba8c30c30c1a9b9d98ebf8bfe7a6385eb24c844be6c10fd4a496ebc1d4736fd.exe 5096 dba8c30c30c1a9b9d98ebf8bfe7a6385eb24c844be6c10fd4a496ebc1d4736fd.exe 5096 dba8c30c30c1a9b9d98ebf8bfe7a6385eb24c844be6c10fd4a496ebc1d4736fd.exe 5096 dba8c30c30c1a9b9d98ebf8bfe7a6385eb24c844be6c10fd4a496ebc1d4736fd.exe 5096 dba8c30c30c1a9b9d98ebf8bfe7a6385eb24c844be6c10fd4a496ebc1d4736fd.exe 5096 dba8c30c30c1a9b9d98ebf8bfe7a6385eb24c844be6c10fd4a496ebc1d4736fd.exe 5096 dba8c30c30c1a9b9d98ebf8bfe7a6385eb24c844be6c10fd4a496ebc1d4736fd.exe 5096 dba8c30c30c1a9b9d98ebf8bfe7a6385eb24c844be6c10fd4a496ebc1d4736fd.exe 5096 dba8c30c30c1a9b9d98ebf8bfe7a6385eb24c844be6c10fd4a496ebc1d4736fd.exe 5096 dba8c30c30c1a9b9d98ebf8bfe7a6385eb24c844be6c10fd4a496ebc1d4736fd.exe 5096 dba8c30c30c1a9b9d98ebf8bfe7a6385eb24c844be6c10fd4a496ebc1d4736fd.exe 5096 dba8c30c30c1a9b9d98ebf8bfe7a6385eb24c844be6c10fd4a496ebc1d4736fd.exe 5096 dba8c30c30c1a9b9d98ebf8bfe7a6385eb24c844be6c10fd4a496ebc1d4736fd.exe 5096 dba8c30c30c1a9b9d98ebf8bfe7a6385eb24c844be6c10fd4a496ebc1d4736fd.exe 5096 dba8c30c30c1a9b9d98ebf8bfe7a6385eb24c844be6c10fd4a496ebc1d4736fd.exe 5096 dba8c30c30c1a9b9d98ebf8bfe7a6385eb24c844be6c10fd4a496ebc1d4736fd.exe 5096 dba8c30c30c1a9b9d98ebf8bfe7a6385eb24c844be6c10fd4a496ebc1d4736fd.exe 5096 dba8c30c30c1a9b9d98ebf8bfe7a6385eb24c844be6c10fd4a496ebc1d4736fd.exe 5096 dba8c30c30c1a9b9d98ebf8bfe7a6385eb24c844be6c10fd4a496ebc1d4736fd.exe 5096 dba8c30c30c1a9b9d98ebf8bfe7a6385eb24c844be6c10fd4a496ebc1d4736fd.exe 5096 dba8c30c30c1a9b9d98ebf8bfe7a6385eb24c844be6c10fd4a496ebc1d4736fd.exe 5096 dba8c30c30c1a9b9d98ebf8bfe7a6385eb24c844be6c10fd4a496ebc1d4736fd.exe 5096 dba8c30c30c1a9b9d98ebf8bfe7a6385eb24c844be6c10fd4a496ebc1d4736fd.exe -
Suspicious use of WriteProcessMemory 6 IoCs
description pid Process procid_target PID 5096 wrote to memory of 4072 5096 dba8c30c30c1a9b9d98ebf8bfe7a6385eb24c844be6c10fd4a496ebc1d4736fd.exe 82 PID 5096 wrote to memory of 4072 5096 dba8c30c30c1a9b9d98ebf8bfe7a6385eb24c844be6c10fd4a496ebc1d4736fd.exe 82 PID 5096 wrote to memory of 4072 5096 dba8c30c30c1a9b9d98ebf8bfe7a6385eb24c844be6c10fd4a496ebc1d4736fd.exe 82 PID 5096 wrote to memory of 1952 5096 dba8c30c30c1a9b9d98ebf8bfe7a6385eb24c844be6c10fd4a496ebc1d4736fd.exe 88 PID 5096 wrote to memory of 1952 5096 dba8c30c30c1a9b9d98ebf8bfe7a6385eb24c844be6c10fd4a496ebc1d4736fd.exe 88 PID 5096 wrote to memory of 1952 5096 dba8c30c30c1a9b9d98ebf8bfe7a6385eb24c844be6c10fd4a496ebc1d4736fd.exe 88
Processes
-
C:\Users\Admin\AppData\Local\Temp\dba8c30c30c1a9b9d98ebf8bfe7a6385eb24c844be6c10fd4a496ebc1d4736fd.exe"C:\Users\Admin\AppData\Local\Temp\dba8c30c30c1a9b9d98ebf8bfe7a6385eb24c844be6c10fd4a496ebc1d4736fd.exe"1⤵
- Checks computer location settings
- Suspicious use of FindShellTrayWindow
- Suspicious use of SendNotifyMessage
- Suspicious use of WriteProcessMemory
PID:5096 -
C:\Windows\SysWOW64\WindowsPowerShell\v1.0\powershell.exe"C:\Windows\System32\WindowsPowerShell\v1.0\powershell.exe" Compress-Archive -Path C:\Users\Admin\AppData\Local\Temp -DestinationPath C:\Users\Admin\AppData\Local\Temp\..\Temp.zip -Force -CompressionLevel Optimal2⤵
- Suspicious behavior: EnumeratesProcesses
- Suspicious use of AdjustPrivilegeToken
PID:4072
-
-
C:\Windows\SysWOW64\cmd.exeC:\Windows\SysWOW64\cmd.exe /C del /F /Q "C:\Users\Admin\AppData\Local\Temp\dba8c30c30c1a9b9d98ebf8bfe7a6385eb24c844be6c10fd4a496ebc1d4736fd.exe" && rmdir /S /Q "C:\Users\Admin\AppData\Local\Temp"2⤵PID:1952
-
Network
MITRE ATT&CK Enterprise v15
Replay Monitor
Loading Replay Monitor...
Downloads
-
Filesize
60B
MD5d17fe0a3f47be24a6453e9ef58c94641
SHA16ab83620379fc69f80c0242105ddffd7d98d5d9d
SHA25696ad1146eb96877eab5942ae0736b82d8b5e2039a80d3d6932665c1a4c87dcf7
SHA5125b592e58f26c264604f98f6aa12860758ce606d1c63220736cf0c779e4e18e3cec8706930a16c38b20161754d1017d1657d35258e58ca22b18f5b232880dec82