976a7fefb48c81afeaf9255f02201d65a353035b9bed7c8667de7df8b44b1421

Analysis

max time kernel
691s
max time network
1140s
platform
windows10-2004_x64
resource
win10v2004-20230703-en
resource tags

arch:x64arch:x86image:win10v2004-20230703-enlocale:en-usos:windows10-2004-x64system
submitted
10-07-2023 04:44

Target

GETTING UP.exe
Size

2.3MB
MD5

b9c876b131b9916df5a95e017e276fbf
SHA1

5026ca0ba6b4301cf0353e737f60cac921c5190f
SHA256

73077188c541952e4cee319a28243793d2bad1d8f1669e5d744bb55733a1ef31
SHA512

88c33d30c445ac218bffdd8e282a8d04685dade95ab2c912f41b6c41b97ef308e2efa4fd17d257946b824d3bb510432f0553765abdb57b07d716d6dc29c9db7c
SSDEEP

49152:4kWk5cS7a+9XYaQaZehc4mTYJ78V9gyBn4cIfmP/SA8N:oajJRZ942KQV9hp4LfmP/SA8

Score

3^/10

Enumerates physical storage devices 1 TTPs
Attempts to interact with connected storage/optical drive(s).

System Information Discovery
T1082
Suspicious use of SetWindowsHookEx 3 IoCs

Processes:

GETTING UP.exe

pid process

840 GETTING UP.exe
840 GETTING UP.exe
840 GETTING UP.exe

Suspicious use of WriteProcessMemory 3 IoCs

Processes:

GETTING UP.exe

description	pid	process	target process
PID 840 wrote to memory of 4668	840	GETTING UP.exe	cmd.exe
PID 840 wrote to memory of 4668	840	GETTING UP.exe	cmd.exe
PID 840 wrote to memory of 4668	840	GETTING UP.exe	cmd.exe

C:\Users\Admin\AppData\Local\Temp\GETTING UP.exe
"C:\Users\Admin\AppData\Local\Temp\GETTING UP.exe"
1⤵
- Suspicious use of SetWindowsHookEx
- Suspicious use of WriteProcessMemory
PID:840
- C:\Windows\SysWOW64\cmd.exe
  cmd.exe /c C:\Users\Admin\AppData\Local\Temp\
  2⤵
  PID:4668

Initial Access

Execution

Persistence

Privilege Escalation

Defense Evasion

Credential Access

Discovery

System Information Discovery

Lateral Movement

Collection

Command and Control

Exfiltration

Impact