Analysis
-
max time kernel
90s -
max time network
156s -
platform
windows10-2004_x64 -
resource
win10v2004-20220901-en -
resource tags
arch:x64arch:x86image:win10v2004-20220901-enlocale:en-usos:windows10-2004-x64system -
submitted
30/10/2022, 06:25
Behavioral task
behavioral1
Sample
19efeb9c5a1089a41610cd3cb11ef28fed2e89ad39a5cb391d5ff534741b17cc.exe
Resource
win7-20220901-en
Behavioral task
behavioral2
Sample
19efeb9c5a1089a41610cd3cb11ef28fed2e89ad39a5cb391d5ff534741b17cc.exe
Resource
win10v2004-20220901-en
General
-
Target
19efeb9c5a1089a41610cd3cb11ef28fed2e89ad39a5cb391d5ff534741b17cc.exe
-
Size
1.2MB
-
MD5
a27cac37dcd72f1736acf681847662f5
-
SHA1
944c807db3868dd9efbd57e92b58207e1c53bd84
-
SHA256
19efeb9c5a1089a41610cd3cb11ef28fed2e89ad39a5cb391d5ff534741b17cc
-
SHA512
5055cc3899855823c6437c085c4698d8179e1e7c6e332f10fccfdcf5e605fe3b7faa6073b9e9218bfd80e3e77a41d469cba7c5a4c3b0af94e66ade6d3549056a
-
SSDEEP
24576:9MmnDC+rPnAveavusQoiFMJA9u/1olqXefho2Scl7TjFk:9jDCiofupzFMJHNAhLl7Tjy
Malware Config
Signatures
-
resource yara_rule behavioral2/memory/3752-132-0x0000000000400000-0x00000000004C9000-memory.dmp upx behavioral2/memory/3752-134-0x0000000000400000-0x00000000004C9000-memory.dmp upx -
AutoIT Executable 1 IoCs
AutoIT scripts compiled to PE executables.
resource yara_rule behavioral2/memory/3752-134-0x0000000000400000-0x00000000004C9000-memory.dmp autoit_exe -
Suspicious use of SetThreadContext 1 IoCs
description pid Process procid_target PID 3752 set thread context of 5088 3752 19efeb9c5a1089a41610cd3cb11ef28fed2e89ad39a5cb391d5ff534741b17cc.exe 84 -
Enumerates physical storage devices 1 TTPs
Attempts to interact with connected storage/optical drive(s). Likely ransomware behaviour.
-
Program crash 1 IoCs
pid pid_target Process procid_target 1644 5088 WerFault.exe 84 -
Suspicious use of WriteProcessMemory 3 IoCs
description pid Process procid_target PID 3752 wrote to memory of 5088 3752 19efeb9c5a1089a41610cd3cb11ef28fed2e89ad39a5cb391d5ff534741b17cc.exe 84 PID 3752 wrote to memory of 5088 3752 19efeb9c5a1089a41610cd3cb11ef28fed2e89ad39a5cb391d5ff534741b17cc.exe 84 PID 3752 wrote to memory of 5088 3752 19efeb9c5a1089a41610cd3cb11ef28fed2e89ad39a5cb391d5ff534741b17cc.exe 84
Processes
-
C:\Users\Admin\AppData\Local\Temp\19efeb9c5a1089a41610cd3cb11ef28fed2e89ad39a5cb391d5ff534741b17cc.exe"C:\Users\Admin\AppData\Local\Temp\19efeb9c5a1089a41610cd3cb11ef28fed2e89ad39a5cb391d5ff534741b17cc.exe"1⤵
- Suspicious use of SetThreadContext
- Suspicious use of WriteProcessMemory
PID:3752 -
C:\Users\Admin\AppData\Local\Temp\19efeb9c5a1089a41610cd3cb11ef28fed2e89ad39a5cb391d5ff534741b17cc.exe"C:\Users\Admin\AppData\Local\Temp\19efeb9c5a1089a41610cd3cb11ef28fed2e89ad39a5cb391d5ff534741b17cc.exe"2⤵PID:5088
-
C:\Windows\SysWOW64\WerFault.exeC:\Windows\SysWOW64\WerFault.exe -u -p 5088 -s 123⤵
- Program crash
PID:1644
-
-
-
C:\Windows\SysWOW64\WerFault.exeC:\Windows\SysWOW64\WerFault.exe -pss -s 184 -p 5088 -ip 50881⤵PID:4936