Analysis
-
max time kernel
189s -
max time network
196s -
platform
windows10-2004_x64 -
resource
win10v2004-20221111-en -
resource tags
arch:x64arch:x86image:win10v2004-20221111-enlocale:en-usos:windows10-2004-x64system -
submitted
23-11-2022 11:49
Static task
static1
Behavioral task
behavioral1
Sample
ef194f1db964fa221e432071835bfa7d09146d6b50a330fc76fba2e1ab834b66.exe
Resource
win7-20220812-en
Behavioral task
behavioral2
Sample
ef194f1db964fa221e432071835bfa7d09146d6b50a330fc76fba2e1ab834b66.exe
Resource
win10v2004-20221111-en
General
-
Target
ef194f1db964fa221e432071835bfa7d09146d6b50a330fc76fba2e1ab834b66.exe
-
Size
522KB
-
MD5
cae07e6af5399584f12c23a0294cc541
-
SHA1
da7853818cb2faff721cbed462765bc9371d803a
-
SHA256
ef194f1db964fa221e432071835bfa7d09146d6b50a330fc76fba2e1ab834b66
-
SHA512
30217f6c5f1dbd8e44821b5978e12f2dd54d3032ac4b6cc3a662450952789b3563e82d7d822c45e3df6b673a9bd3a5e30d64dce56ff48c2efcd7d8dba7154b06
-
SSDEEP
12288:2QKVzFPZiuYGFf8n00gzTypy18xQqpx8O5x:2jVzFPr/Fkn05Eatqpx8
Malware Config
Signatures
-
Suspicious use of WriteProcessMemory 6 IoCs
Processes:
ef194f1db964fa221e432071835bfa7d09146d6b50a330fc76fba2e1ab834b66.exedescription pid process target process PID 3160 wrote to memory of 652 3160 ef194f1db964fa221e432071835bfa7d09146d6b50a330fc76fba2e1ab834b66.exe ef194f1db964fa221e432071835bfa7d09146d6b50a330fc76fba2e1ab834b66.exe PID 3160 wrote to memory of 652 3160 ef194f1db964fa221e432071835bfa7d09146d6b50a330fc76fba2e1ab834b66.exe ef194f1db964fa221e432071835bfa7d09146d6b50a330fc76fba2e1ab834b66.exe PID 3160 wrote to memory of 652 3160 ef194f1db964fa221e432071835bfa7d09146d6b50a330fc76fba2e1ab834b66.exe ef194f1db964fa221e432071835bfa7d09146d6b50a330fc76fba2e1ab834b66.exe PID 3160 wrote to memory of 3500 3160 ef194f1db964fa221e432071835bfa7d09146d6b50a330fc76fba2e1ab834b66.exe ef194f1db964fa221e432071835bfa7d09146d6b50a330fc76fba2e1ab834b66.exe PID 3160 wrote to memory of 3500 3160 ef194f1db964fa221e432071835bfa7d09146d6b50a330fc76fba2e1ab834b66.exe ef194f1db964fa221e432071835bfa7d09146d6b50a330fc76fba2e1ab834b66.exe PID 3160 wrote to memory of 3500 3160 ef194f1db964fa221e432071835bfa7d09146d6b50a330fc76fba2e1ab834b66.exe ef194f1db964fa221e432071835bfa7d09146d6b50a330fc76fba2e1ab834b66.exe
Processes
-
C:\Users\Admin\AppData\Local\Temp\ef194f1db964fa221e432071835bfa7d09146d6b50a330fc76fba2e1ab834b66.exe"C:\Users\Admin\AppData\Local\Temp\ef194f1db964fa221e432071835bfa7d09146d6b50a330fc76fba2e1ab834b66.exe"1⤵
- Suspicious use of WriteProcessMemory
PID:3160 -
C:\Users\Admin\AppData\Local\Temp\ef194f1db964fa221e432071835bfa7d09146d6b50a330fc76fba2e1ab834b66.exestart2⤵PID:652
-
C:\Users\Admin\AppData\Local\Temp\ef194f1db964fa221e432071835bfa7d09146d6b50a330fc76fba2e1ab834b66.exewatch2⤵PID:3500