Analysis
-
max time kernel
114s -
max time network
122s -
platform
windows10-2004_x64 -
resource
win10v2004-20220812-en -
resource tags
arch:x64arch:x86image:win10v2004-20220812-enlocale:en-usos:windows10-2004-x64system -
submitted
06-12-2022 17:03
Behavioral task
behavioral1
Sample
a2e89d87c25d95aad9489684506111e6e0682764fd5bec31699a49d85af6e7fd.exe
Resource
win7-20221111-en
Behavioral task
behavioral2
Sample
a2e89d87c25d95aad9489684506111e6e0682764fd5bec31699a49d85af6e7fd.exe
Resource
win10v2004-20220812-en
General
-
Target
a2e89d87c25d95aad9489684506111e6e0682764fd5bec31699a49d85af6e7fd.exe
-
Size
573KB
-
MD5
8b8831d1e646e6b201eadf973966db84
-
SHA1
ed1a0e74a9e9ba9acd9876891b5a8908da6aaf44
-
SHA256
a2e89d87c25d95aad9489684506111e6e0682764fd5bec31699a49d85af6e7fd
-
SHA512
e0a70f115533ce83f66248a07aa03b5104d2b045cb2f09fed821ea5125eb4dc9360a8a6f5cddc18768c0a42317552fdec6a8318ccb03f3e4c3aff2c29afd3ae9
-
SSDEEP
12288:ejkArEN249AyE/rbaMct4bO2/VQ5qoZn8Jj4/eknomg0clw:ZFE//Tct4bOsW1Zw4/zoEyw
Malware Config
Signatures
-
resource yara_rule behavioral2/memory/3116-132-0x0000000000400000-0x00000000004C1000-memory.dmp upx behavioral2/memory/3116-133-0x0000000000400000-0x00000000004C1000-memory.dmp upx behavioral2/memory/3116-138-0x0000000000400000-0x00000000004C1000-memory.dmp upx -
AutoIT Executable 1 IoCs
AutoIT scripts compiled to PE executables.
resource yara_rule behavioral2/memory/3116-138-0x0000000000400000-0x00000000004C1000-memory.dmp autoit_exe -
Suspicious use of SetThreadContext 2 IoCs
description pid Process procid_target PID 3116 set thread context of 520 3116 a2e89d87c25d95aad9489684506111e6e0682764fd5bec31699a49d85af6e7fd.exe 79 PID 520 set thread context of 3932 520 a2e89d87c25d95aad9489684506111e6e0682764fd5bec31699a49d85af6e7fd.exe 80 -
Enumerates physical storage devices 1 TTPs
Attempts to interact with connected storage/optical drive(s). Likely ransomware behaviour.
-
Suspicious behavior: EnumeratesProcesses 4 IoCs
pid Process 3932 a2e89d87c25d95aad9489684506111e6e0682764fd5bec31699a49d85af6e7fd.exe 3932 a2e89d87c25d95aad9489684506111e6e0682764fd5bec31699a49d85af6e7fd.exe 3932 a2e89d87c25d95aad9489684506111e6e0682764fd5bec31699a49d85af6e7fd.exe 3932 a2e89d87c25d95aad9489684506111e6e0682764fd5bec31699a49d85af6e7fd.exe -
Suspicious use of FindShellTrayWindow 4 IoCs
pid Process 3116 a2e89d87c25d95aad9489684506111e6e0682764fd5bec31699a49d85af6e7fd.exe 3116 a2e89d87c25d95aad9489684506111e6e0682764fd5bec31699a49d85af6e7fd.exe 3116 a2e89d87c25d95aad9489684506111e6e0682764fd5bec31699a49d85af6e7fd.exe 3116 a2e89d87c25d95aad9489684506111e6e0682764fd5bec31699a49d85af6e7fd.exe -
Suspicious use of SendNotifyMessage 4 IoCs
pid Process 3116 a2e89d87c25d95aad9489684506111e6e0682764fd5bec31699a49d85af6e7fd.exe 3116 a2e89d87c25d95aad9489684506111e6e0682764fd5bec31699a49d85af6e7fd.exe 3116 a2e89d87c25d95aad9489684506111e6e0682764fd5bec31699a49d85af6e7fd.exe 3116 a2e89d87c25d95aad9489684506111e6e0682764fd5bec31699a49d85af6e7fd.exe -
Suspicious use of SetWindowsHookEx 1 IoCs
pid Process 520 a2e89d87c25d95aad9489684506111e6e0682764fd5bec31699a49d85af6e7fd.exe -
Suspicious use of WriteProcessMemory 12 IoCs
description pid Process procid_target PID 3116 wrote to memory of 520 3116 a2e89d87c25d95aad9489684506111e6e0682764fd5bec31699a49d85af6e7fd.exe 79 PID 3116 wrote to memory of 520 3116 a2e89d87c25d95aad9489684506111e6e0682764fd5bec31699a49d85af6e7fd.exe 79 PID 3116 wrote to memory of 520 3116 a2e89d87c25d95aad9489684506111e6e0682764fd5bec31699a49d85af6e7fd.exe 79 PID 3116 wrote to memory of 520 3116 a2e89d87c25d95aad9489684506111e6e0682764fd5bec31699a49d85af6e7fd.exe 79 PID 3116 wrote to memory of 520 3116 a2e89d87c25d95aad9489684506111e6e0682764fd5bec31699a49d85af6e7fd.exe 79 PID 520 wrote to memory of 3932 520 a2e89d87c25d95aad9489684506111e6e0682764fd5bec31699a49d85af6e7fd.exe 80 PID 520 wrote to memory of 3932 520 a2e89d87c25d95aad9489684506111e6e0682764fd5bec31699a49d85af6e7fd.exe 80 PID 520 wrote to memory of 3932 520 a2e89d87c25d95aad9489684506111e6e0682764fd5bec31699a49d85af6e7fd.exe 80 PID 520 wrote to memory of 3932 520 a2e89d87c25d95aad9489684506111e6e0682764fd5bec31699a49d85af6e7fd.exe 80 PID 520 wrote to memory of 3932 520 a2e89d87c25d95aad9489684506111e6e0682764fd5bec31699a49d85af6e7fd.exe 80 PID 520 wrote to memory of 3932 520 a2e89d87c25d95aad9489684506111e6e0682764fd5bec31699a49d85af6e7fd.exe 80 PID 520 wrote to memory of 3932 520 a2e89d87c25d95aad9489684506111e6e0682764fd5bec31699a49d85af6e7fd.exe 80
Processes
-
C:\Users\Admin\AppData\Local\Temp\a2e89d87c25d95aad9489684506111e6e0682764fd5bec31699a49d85af6e7fd.exe"C:\Users\Admin\AppData\Local\Temp\a2e89d87c25d95aad9489684506111e6e0682764fd5bec31699a49d85af6e7fd.exe"1⤵
- Suspicious use of SetThreadContext
- Suspicious use of FindShellTrayWindow
- Suspicious use of SendNotifyMessage
- Suspicious use of WriteProcessMemory
PID:3116 -
C:\Users\Admin\AppData\Local\Temp\a2e89d87c25d95aad9489684506111e6e0682764fd5bec31699a49d85af6e7fd.exe"C:\Users\Admin\AppData\Local\Temp\a2e89d87c25d95aad9489684506111e6e0682764fd5bec31699a49d85af6e7fd.exe"2⤵
- Suspicious use of SetThreadContext
- Suspicious use of SetWindowsHookEx
- Suspicious use of WriteProcessMemory
PID:520 -
C:\Users\Admin\AppData\Local\Temp\a2e89d87c25d95aad9489684506111e6e0682764fd5bec31699a49d85af6e7fd.exe"C:\Users\Admin\AppData\Local\Temp\a2e89d87c25d95aad9489684506111e6e0682764fd5bec31699a49d85af6e7fd.exe"3⤵
- Suspicious behavior: EnumeratesProcesses
PID:3932
-
-