Analysis
-
max time kernel
149s -
max time network
155s -
platform
windows10-2004_x64 -
resource
win10v2004-20220812-en -
resource tags
arch:x64arch:x86image:win10v2004-20220812-enlocale:en-usos:windows10-2004-x64system -
submitted
07-11-2022 07:19
Static task
static1
Behavioral task
behavioral1
Sample
abb24fd6aa54ed0d5d56535fef8313690e8dd4f69570f00f175e9c2a698fb45c.exe
Resource
win7-20220901-en
Behavioral task
behavioral2
Sample
abb24fd6aa54ed0d5d56535fef8313690e8dd4f69570f00f175e9c2a698fb45c.exe
Resource
win10v2004-20220812-en
General
-
Target
abb24fd6aa54ed0d5d56535fef8313690e8dd4f69570f00f175e9c2a698fb45c.exe
-
Size
312KB
-
MD5
9017a6d7eea1f36145701ab99a14a9aa
-
SHA1
7603f937d6c1bf49cd09eb4dda900b997b0c7220
-
SHA256
abb24fd6aa54ed0d5d56535fef8313690e8dd4f69570f00f175e9c2a698fb45c
-
SHA512
617ad0beac9f142ab658efc54854db89d13dcad837e3995f2a9998ac995641cbf8b72f4c4d77f4f67a8937907dd9e22d274e292f16464ab12cdede3f2c8f15a6
-
SSDEEP
6144:s1h36CMlJ02kuaJckFvqIQmcWBO2y33/v:s1h3lc+EaJcsv+1Wc2y3P
Malware Config
Signatures
-
Suspicious use of SetThreadContext 1 IoCs
Processes:
abb24fd6aa54ed0d5d56535fef8313690e8dd4f69570f00f175e9c2a698fb45c.exedescription pid Process procid_target PID 4576 set thread context of 5104 4576 abb24fd6aa54ed0d5d56535fef8313690e8dd4f69570f00f175e9c2a698fb45c.exe 82 -
Suspicious use of WriteProcessMemory 10 IoCs
Processes:
abb24fd6aa54ed0d5d56535fef8313690e8dd4f69570f00f175e9c2a698fb45c.exedescription pid Process procid_target PID 4576 wrote to memory of 5104 4576 abb24fd6aa54ed0d5d56535fef8313690e8dd4f69570f00f175e9c2a698fb45c.exe 82 PID 4576 wrote to memory of 5104 4576 abb24fd6aa54ed0d5d56535fef8313690e8dd4f69570f00f175e9c2a698fb45c.exe 82 PID 4576 wrote to memory of 5104 4576 abb24fd6aa54ed0d5d56535fef8313690e8dd4f69570f00f175e9c2a698fb45c.exe 82 PID 4576 wrote to memory of 5104 4576 abb24fd6aa54ed0d5d56535fef8313690e8dd4f69570f00f175e9c2a698fb45c.exe 82 PID 4576 wrote to memory of 5104 4576 abb24fd6aa54ed0d5d56535fef8313690e8dd4f69570f00f175e9c2a698fb45c.exe 82 PID 4576 wrote to memory of 5104 4576 abb24fd6aa54ed0d5d56535fef8313690e8dd4f69570f00f175e9c2a698fb45c.exe 82 PID 4576 wrote to memory of 5104 4576 abb24fd6aa54ed0d5d56535fef8313690e8dd4f69570f00f175e9c2a698fb45c.exe 82 PID 4576 wrote to memory of 5104 4576 abb24fd6aa54ed0d5d56535fef8313690e8dd4f69570f00f175e9c2a698fb45c.exe 82 PID 4576 wrote to memory of 5104 4576 abb24fd6aa54ed0d5d56535fef8313690e8dd4f69570f00f175e9c2a698fb45c.exe 82 PID 4576 wrote to memory of 5104 4576 abb24fd6aa54ed0d5d56535fef8313690e8dd4f69570f00f175e9c2a698fb45c.exe 82
Processes
-
C:\Users\Admin\AppData\Local\Temp\abb24fd6aa54ed0d5d56535fef8313690e8dd4f69570f00f175e9c2a698fb45c.exe"C:\Users\Admin\AppData\Local\Temp\abb24fd6aa54ed0d5d56535fef8313690e8dd4f69570f00f175e9c2a698fb45c.exe"1⤵
- Suspicious use of SetThreadContext
- Suspicious use of WriteProcessMemory
PID:4576 -
C:\Users\Admin\AppData\Local\Temp\abb24fd6aa54ed0d5d56535fef8313690e8dd4f69570f00f175e9c2a698fb45c.exe"C:\Users\Admin\AppData\Local\Temp\abb24fd6aa54ed0d5d56535fef8313690e8dd4f69570f00f175e9c2a698fb45c.exe"2⤵PID:5104
-