Analysis
-
max time kernel
46s -
max time network
49s -
platform
windows7_x64 -
resource
win7-20220812-en -
resource tags
arch:x64arch:x86image:win7-20220812-enlocale:en-usos:windows7-x64system -
submitted
06-11-2022 06:30
Static task
static1
Behavioral task
behavioral1
Sample
bf96b20e80b7293edb71ab0281876e0a52345ea897110a53bf49f9568e61f143.exe
Resource
win7-20220812-en
Behavioral task
behavioral2
Sample
bf96b20e80b7293edb71ab0281876e0a52345ea897110a53bf49f9568e61f143.exe
Resource
win10v2004-20220812-en
General
-
Target
bf96b20e80b7293edb71ab0281876e0a52345ea897110a53bf49f9568e61f143.exe
-
Size
295KB
-
MD5
38d62dd66ca579db65283740a580c9c0
-
SHA1
82ccd4f61ed996fac852704c06c68bf2cb547423
-
SHA256
bf96b20e80b7293edb71ab0281876e0a52345ea897110a53bf49f9568e61f143
-
SHA512
ef1db856bd54a887ef83430816e0a0683aff702afbb271b07f2a4f652b5665c952e8c01aae9ad138809dc54179497a119a221d81b92de662799553ff25ce295f
-
SSDEEP
6144:qiffBMJ7w++eVUsGVOx39ksI5G8qwNyoov4f1FCX:qOfB+oSUTVOxtWqwNLoC1Fe
Malware Config
Signatures
-
Suspicious use of WriteProcessMemory 4 IoCs
description pid Process procid_target PID 2012 wrote to memory of 1964 2012 bf96b20e80b7293edb71ab0281876e0a52345ea897110a53bf49f9568e61f143.exe 28 PID 2012 wrote to memory of 1964 2012 bf96b20e80b7293edb71ab0281876e0a52345ea897110a53bf49f9568e61f143.exe 28 PID 2012 wrote to memory of 1964 2012 bf96b20e80b7293edb71ab0281876e0a52345ea897110a53bf49f9568e61f143.exe 28 PID 2012 wrote to memory of 1964 2012 bf96b20e80b7293edb71ab0281876e0a52345ea897110a53bf49f9568e61f143.exe 28
Processes
-
C:\Users\Admin\AppData\Local\Temp\bf96b20e80b7293edb71ab0281876e0a52345ea897110a53bf49f9568e61f143.exe"C:\Users\Admin\AppData\Local\Temp\bf96b20e80b7293edb71ab0281876e0a52345ea897110a53bf49f9568e61f143.exe"1⤵
- Suspicious use of WriteProcessMemory
PID:2012 -
C:\Users\Admin\AppData\Local\Temp\bf96b20e80b7293edb71ab0281876e0a52345ea897110a53bf49f9568e61f143.exetear2⤵PID:1964
-