Analysis
-
max time kernel
180s -
max time network
195s -
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 12:18
Static task
static1
Behavioral task
behavioral1
Sample
350d19b7573d3f96a6b1e93798b8cc936354c6204d6b86e4d82b68c2ea06618d.exe
Resource
win7-20221111-en
Behavioral task
behavioral2
Sample
350d19b7573d3f96a6b1e93798b8cc936354c6204d6b86e4d82b68c2ea06618d.exe
Resource
win10v2004-20221111-en
General
-
Target
350d19b7573d3f96a6b1e93798b8cc936354c6204d6b86e4d82b68c2ea06618d.exe
-
Size
526KB
-
MD5
d6faa3a6f87c373b7db4ec24460c0c19
-
SHA1
2fb06b427c89f4bbbfd00252bea1490d22107628
-
SHA256
350d19b7573d3f96a6b1e93798b8cc936354c6204d6b86e4d82b68c2ea06618d
-
SHA512
487f887d36563ef30c278adf89277abea4ffdeffa7df7a4192a7ecb3ab3f7e758272b1eefe9900af1b16da37ac3ce9346f644d249ccea38435e33ce6e187ba85
-
SSDEEP
12288:bX/admSbbZqrYTSTXzoJ7y18xQqpx8O5pK:bX/az8BL0datqpx8L
Malware Config
Signatures
-
Suspicious use of WriteProcessMemory 6 IoCs
Processes:
350d19b7573d3f96a6b1e93798b8cc936354c6204d6b86e4d82b68c2ea06618d.exedescription pid process target process PID 5096 wrote to memory of 1668 5096 350d19b7573d3f96a6b1e93798b8cc936354c6204d6b86e4d82b68c2ea06618d.exe 350d19b7573d3f96a6b1e93798b8cc936354c6204d6b86e4d82b68c2ea06618d.exe PID 5096 wrote to memory of 1668 5096 350d19b7573d3f96a6b1e93798b8cc936354c6204d6b86e4d82b68c2ea06618d.exe 350d19b7573d3f96a6b1e93798b8cc936354c6204d6b86e4d82b68c2ea06618d.exe PID 5096 wrote to memory of 1668 5096 350d19b7573d3f96a6b1e93798b8cc936354c6204d6b86e4d82b68c2ea06618d.exe 350d19b7573d3f96a6b1e93798b8cc936354c6204d6b86e4d82b68c2ea06618d.exe PID 5096 wrote to memory of 4360 5096 350d19b7573d3f96a6b1e93798b8cc936354c6204d6b86e4d82b68c2ea06618d.exe 350d19b7573d3f96a6b1e93798b8cc936354c6204d6b86e4d82b68c2ea06618d.exe PID 5096 wrote to memory of 4360 5096 350d19b7573d3f96a6b1e93798b8cc936354c6204d6b86e4d82b68c2ea06618d.exe 350d19b7573d3f96a6b1e93798b8cc936354c6204d6b86e4d82b68c2ea06618d.exe PID 5096 wrote to memory of 4360 5096 350d19b7573d3f96a6b1e93798b8cc936354c6204d6b86e4d82b68c2ea06618d.exe 350d19b7573d3f96a6b1e93798b8cc936354c6204d6b86e4d82b68c2ea06618d.exe
Processes
-
C:\Users\Admin\AppData\Local\Temp\350d19b7573d3f96a6b1e93798b8cc936354c6204d6b86e4d82b68c2ea06618d.exe"C:\Users\Admin\AppData\Local\Temp\350d19b7573d3f96a6b1e93798b8cc936354c6204d6b86e4d82b68c2ea06618d.exe"1⤵
- Suspicious use of WriteProcessMemory
PID:5096 -
C:\Users\Admin\AppData\Local\Temp\350d19b7573d3f96a6b1e93798b8cc936354c6204d6b86e4d82b68c2ea06618d.exestart2⤵PID:1668
-
C:\Users\Admin\AppData\Local\Temp\350d19b7573d3f96a6b1e93798b8cc936354c6204d6b86e4d82b68c2ea06618d.exewatch2⤵PID:4360