Analysis
- max time kernel
54s - max time network
74s - platform
windows10-1703_x64 - resource
win10-20220812-en - resource tags
arch:x64arch:x86image:win10-20220812-enlocale:en-usos:windows10-1703-x64system - submitted
01/11/2022, 11:52
Static task
static1
Behavioral task
behavioral1
Sample
3aa9cf4a033a78e9dfddb734885bea383e2a533db89d9cbdbe4723530b24e911.exe
Resource
win10-20220812-en
3 signatures
150 seconds
General
- Target 3aa9cf4a033a78e9dfddb734885bea383e2a533db89d9cbdbe4723530b24e911.exe
- Size 324KB
- Sample221101-n1ybpacegp
- SHA256 3aa9cf4a033a78e9dfddb734885bea383e2a533db89d9cbdbe4723530b24e911
- MD5 1b612605f47fbf71685231788003208e
- SHA1 e57538d6d51e0d30999315f039088ed698040a23
- SHA512 1385a6a0009c2e4f6b34f1d0b83b0641c7266bce71ba49892b9c09e73d6ff75f9cc42dfa15d91e9d29508dfbb3cddcb656b11d849e8950c2ccda06945db6bfe8
- SSDEEP 6144:eKlzr1sYCzek2ciDaP9Xk6Ln1W8W/9InBSkZZmLdGcAdgdY6RKpjS:eGhQ2ciDq9ZL1W8q9InBRqELdolRKpj
- MD5 SHA1 SHA512 SSDEEP
Score
5/10
Malware Config
Signatures
- Suspicious use of SetThreadContext 1 IoCs
description pid Process procid_target PID 2668 set thread context of 4784 2668 3aa9cf4a033a78e9dfddb734885bea383e2a533db89d9cbdbe4723530b24e911.exe 66 - Program crash 1 IoCs
pid pid_target Process procid_target 5108 4784 WerFault.exe 66 - Suspicious use of WriteProcessMemory 9 IoCs
description pid Process procid_target PID 2668 wrote to memory of 4784 2668 3aa9cf4a033a78e9dfddb734885bea383e2a533db89d9cbdbe4723530b24e911.exe 66 PID 2668 wrote to memory of 4784 2668 3aa9cf4a033a78e9dfddb734885bea383e2a533db89d9cbdbe4723530b24e911.exe 66 PID 2668 wrote to memory of 4784 2668 3aa9cf4a033a78e9dfddb734885bea383e2a533db89d9cbdbe4723530b24e911.exe 66 PID 2668 wrote to memory of 4784 2668 3aa9cf4a033a78e9dfddb734885bea383e2a533db89d9cbdbe4723530b24e911.exe 66 PID 2668 wrote to memory of 4784 2668 3aa9cf4a033a78e9dfddb734885bea383e2a533db89d9cbdbe4723530b24e911.exe 66 PID 2668 wrote to memory of 4784 2668 3aa9cf4a033a78e9dfddb734885bea383e2a533db89d9cbdbe4723530b24e911.exe 66 PID 2668 wrote to memory of 4784 2668 3aa9cf4a033a78e9dfddb734885bea383e2a533db89d9cbdbe4723530b24e911.exe 66 PID 2668 wrote to memory of 4784 2668 3aa9cf4a033a78e9dfddb734885bea383e2a533db89d9cbdbe4723530b24e911.exe 66 PID 2668 wrote to memory of 4784 2668 3aa9cf4a033a78e9dfddb734885bea383e2a533db89d9cbdbe4723530b24e911.exe 66
Processes
-
C:\Users\Admin\AppData\Local\Temp\3aa9cf4a033a78e9dfddb734885bea383e2a533db89d9cbdbe4723530b24e911.exe"C:\Users\Admin\AppData\Local\Temp\3aa9cf4a033a78e9dfddb734885bea383e2a533db89d9cbdbe4723530b24e911.exe"1⤵
- Suspicious use of SetThreadContext
- Suspicious use of WriteProcessMemory
PID:2668 -
C:\Users\Admin\AppData\Local\Temp\3aa9cf4a033a78e9dfddb734885bea383e2a533db89d9cbdbe4723530b24e911.exeC:\Users\Admin\AppData\Local\Temp\3aa9cf4a033a78e9dfddb734885bea383e2a533db89d9cbdbe4723530b24e911.exe2⤵PID:4784
-
C:\Windows\SysWOW64\WerFault.exeC:\Windows\SysWOW64\WerFault.exe -u -p 4784 -s 1523⤵
- Program crash
PID:5108
-
-