Analysis
-
max time kernel
174s -
max time network
218s -
platform
windows10-2004_x64 -
resource
win10v2004-20221111-en -
resource tags
arch:x64arch:x86image:win10v2004-20221111-enlocale:en-usos:windows10-2004-x64system -
submitted
04/12/2022, 14:05
Static task
static1
Behavioral task
behavioral1
Sample
deff089967847c546f349e9e5c12b3507f9cab76963a4ae43e9de62dc9bc36e2.exe
Resource
win7-20221111-en
Behavioral task
behavioral2
Sample
deff089967847c546f349e9e5c12b3507f9cab76963a4ae43e9de62dc9bc36e2.exe
Resource
win10v2004-20221111-en
General
-
Target
deff089967847c546f349e9e5c12b3507f9cab76963a4ae43e9de62dc9bc36e2.exe
-
Size
188KB
-
MD5
2eeabc98e35078f4f0b5fce3afcdc36b
-
SHA1
44a4d98eba5138e65d5f64df53aa82e362395eb0
-
SHA256
deff089967847c546f349e9e5c12b3507f9cab76963a4ae43e9de62dc9bc36e2
-
SHA512
87a0aea0eef84ed8191ef7da71ec7eb4a7f5467b87431fbfaee654d3f8e0b45a5e9c16a864c22d7494b8f598a857d90a2533846abdb9304f89223bedccbdd563
-
SSDEEP
3072:B+4LlGdtc7q3N87PNwof6hDKlErOHXL+F9p0HRxdemOPzrc77OWw8x8c:Y4ojr3NGGRKl+O6Lp0HRHkc769/c
Malware Config
Signatures
-
Suspicious use of SetThreadContext 1 IoCs
description pid Process procid_target PID 2608 set thread context of 3936 2608 deff089967847c546f349e9e5c12b3507f9cab76963a4ae43e9de62dc9bc36e2.exe 81 -
Modifies registry class 2 IoCs
description ioc Process Key created \REGISTRY\MACHINE\SOFTWARE\Classes\.key deff089967847c546f349e9e5c12b3507f9cab76963a4ae43e9de62dc9bc36e2.exe Set value (str) \REGISTRY\MACHINE\SOFTWARE\Classes\.key\ = "regfile" deff089967847c546f349e9e5c12b3507f9cab76963a4ae43e9de62dc9bc36e2.exe -
Suspicious use of SetWindowsHookEx 1 IoCs
pid Process 2608 deff089967847c546f349e9e5c12b3507f9cab76963a4ae43e9de62dc9bc36e2.exe -
Suspicious use of WriteProcessMemory 7 IoCs
description pid Process procid_target PID 2608 wrote to memory of 3936 2608 deff089967847c546f349e9e5c12b3507f9cab76963a4ae43e9de62dc9bc36e2.exe 81 PID 2608 wrote to memory of 3936 2608 deff089967847c546f349e9e5c12b3507f9cab76963a4ae43e9de62dc9bc36e2.exe 81 PID 2608 wrote to memory of 3936 2608 deff089967847c546f349e9e5c12b3507f9cab76963a4ae43e9de62dc9bc36e2.exe 81 PID 2608 wrote to memory of 3936 2608 deff089967847c546f349e9e5c12b3507f9cab76963a4ae43e9de62dc9bc36e2.exe 81 PID 2608 wrote to memory of 3936 2608 deff089967847c546f349e9e5c12b3507f9cab76963a4ae43e9de62dc9bc36e2.exe 81 PID 2608 wrote to memory of 3936 2608 deff089967847c546f349e9e5c12b3507f9cab76963a4ae43e9de62dc9bc36e2.exe 81 PID 2608 wrote to memory of 3936 2608 deff089967847c546f349e9e5c12b3507f9cab76963a4ae43e9de62dc9bc36e2.exe 81
Processes
-
C:\Users\Admin\AppData\Local\Temp\deff089967847c546f349e9e5c12b3507f9cab76963a4ae43e9de62dc9bc36e2.exe"C:\Users\Admin\AppData\Local\Temp\deff089967847c546f349e9e5c12b3507f9cab76963a4ae43e9de62dc9bc36e2.exe"1⤵
- Suspicious use of SetThreadContext
- Modifies registry class
- Suspicious use of SetWindowsHookEx
- Suspicious use of WriteProcessMemory
PID:2608 -
C:\Users\Admin\AppData\Local\Temp\deff089967847c546f349e9e5c12b3507f9cab76963a4ae43e9de62dc9bc36e2.exeC:\Users\Admin\AppData\Local\Temp\deff089967847c546f349e9e5c12b3507f9cab76963a4ae43e9de62dc9bc36e2.exe2⤵PID:3936
-