Analysis
-
max time kernel
113s -
max time network
133s -
platform
windows10-2004_x64 -
resource
win10v2004-20220812-en -
resource tags
arch:x64arch:x86image:win10v2004-20220812-enlocale:en-usos:windows10-2004-x64system -
submitted
11-10-2022 03:00
Behavioral task
behavioral1
Sample
246225555e80e979e32311bd52a4e6251ffc11035a9d1721f59af934b4fec9b1.exe
Resource
win7-20220812-en
Behavioral task
behavioral2
Sample
246225555e80e979e32311bd52a4e6251ffc11035a9d1721f59af934b4fec9b1.exe
Resource
win10v2004-20220812-en
General
-
Target
246225555e80e979e32311bd52a4e6251ffc11035a9d1721f59af934b4fec9b1.exe
-
Size
347KB
-
MD5
5972e7706ed905eebd292007934da2ae
-
SHA1
808fe0e25130c2848d1eb954cccef3d13f6f4164
-
SHA256
246225555e80e979e32311bd52a4e6251ffc11035a9d1721f59af934b4fec9b1
-
SHA512
4e394c1ce834cdb3000d2913c3d31e6a0c693ddf183b17a467eea5a6b1c483e5f41cae9ee303d67ea796aa08ac919f455bb1e69bb1eaa954981a06176824999c
-
SSDEEP
6144:lQ+kqZEMF7gFw/x4NmGqxLJ8hLsZKeFSZgRm6kLkku90EDelZVKVg:lhOi0Fw/xTGqx1DZ6Um6kgkuu9lZIg
Malware Config
Signatures
-
resource yara_rule behavioral2/memory/3144-132-0x0000000000400000-0x00000000004D4000-memory.dmp upx behavioral2/memory/3144-133-0x0000000000400000-0x00000000004D4000-memory.dmp upx behavioral2/memory/3144-138-0x0000000000400000-0x00000000004D4000-memory.dmp upx -
AutoIT Executable 2 IoCs
AutoIT scripts compiled to PE executables.
resource yara_rule behavioral2/memory/3144-133-0x0000000000400000-0x00000000004D4000-memory.dmp autoit_exe behavioral2/memory/3144-138-0x0000000000400000-0x00000000004D4000-memory.dmp autoit_exe -
Suspicious use of SetThreadContext 1 IoCs
description pid Process procid_target PID 3144 set thread context of 1472 3144 246225555e80e979e32311bd52a4e6251ffc11035a9d1721f59af934b4fec9b1.exe 82 -
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 4056 1472 WerFault.exe 82 -
Suspicious use of WriteProcessMemory 6 IoCs
description pid Process procid_target PID 3144 wrote to memory of 1472 3144 246225555e80e979e32311bd52a4e6251ffc11035a9d1721f59af934b4fec9b1.exe 82 PID 3144 wrote to memory of 1472 3144 246225555e80e979e32311bd52a4e6251ffc11035a9d1721f59af934b4fec9b1.exe 82 PID 3144 wrote to memory of 1472 3144 246225555e80e979e32311bd52a4e6251ffc11035a9d1721f59af934b4fec9b1.exe 82 PID 3144 wrote to memory of 1472 3144 246225555e80e979e32311bd52a4e6251ffc11035a9d1721f59af934b4fec9b1.exe 82 PID 3144 wrote to memory of 1472 3144 246225555e80e979e32311bd52a4e6251ffc11035a9d1721f59af934b4fec9b1.exe 82 PID 3144 wrote to memory of 1472 3144 246225555e80e979e32311bd52a4e6251ffc11035a9d1721f59af934b4fec9b1.exe 82
Processes
-
C:\Users\Admin\AppData\Local\Temp\246225555e80e979e32311bd52a4e6251ffc11035a9d1721f59af934b4fec9b1.exe"C:\Users\Admin\AppData\Local\Temp\246225555e80e979e32311bd52a4e6251ffc11035a9d1721f59af934b4fec9b1.exe"1⤵
- Suspicious use of SetThreadContext
- Suspicious use of WriteProcessMemory
PID:3144 -
C:\Users\Admin\AppData\Local\Temp\246225555e80e979e32311bd52a4e6251ffc11035a9d1721f59af934b4fec9b1.exe"C:\Users\Admin\AppData\Local\Temp\246225555e80e979e32311bd52a4e6251ffc11035a9d1721f59af934b4fec9b1.exe"2⤵PID:1472
-
C:\Windows\SysWOW64\WerFault.exeC:\Windows\SysWOW64\WerFault.exe -u -p 1472 -s 4603⤵
- Program crash
PID:4056
-
-
-
C:\Windows\SysWOW64\WerFault.exeC:\Windows\SysWOW64\WerFault.exe -pss -s 428 -p 1472 -ip 14721⤵PID:3464