Analysis
-
max time kernel
151s -
max time network
187s -
platform
windows10-2004_x64 -
resource
win10v2004-20221111-en -
resource tags
arch:x64arch:x86image:win10v2004-20221111-enlocale:en-usos:windows10-2004-x64system -
submitted
06/12/2022, 10:44
Behavioral task
behavioral1
Sample
b3fa491f988d9eaea26d1e1d3f3f6e811a70cf99602c25f11add6b1516e84d7c.exe
Resource
win7-20221111-en
5 signatures
150 seconds
Behavioral task
behavioral2
Sample
b3fa491f988d9eaea26d1e1d3f3f6e811a70cf99602c25f11add6b1516e84d7c.exe
Resource
win10v2004-20221111-en
5 signatures
150 seconds
General
-
Target
b3fa491f988d9eaea26d1e1d3f3f6e811a70cf99602c25f11add6b1516e84d7c.exe
-
Size
310KB
-
MD5
1728d239613dbd855cf3a3d94b6d9cd2
-
SHA1
a0fba1a1b3e76d13a764d95183a828b984d24629
-
SHA256
b3fa491f988d9eaea26d1e1d3f3f6e811a70cf99602c25f11add6b1516e84d7c
-
SHA512
e196eb8084002e8632874e042c043ea2af2a6a39fd88ea80e730bf289e043af4f51fb69c1712e89eeb2b74c116b52b35e7e80eba8e33ee16309d2d770ba65019
-
SSDEEP
6144:YMFRED9uQy6zHqiERcG3+3wChK+amnT7KQwTdCZaG7Ms6y4q:YMFG7iZB+1IrmPK9qaG7MFI
Score
8/10
Malware Config
Signatures
-
resource yara_rule behavioral2/memory/3300-132-0x0000000000400000-0x00000000004BE000-memory.dmp upx behavioral2/memory/3300-139-0x0000000000400000-0x00000000004BE000-memory.dmp upx -
Suspicious use of SetThreadContext 1 IoCs
description pid Process procid_target PID 3300 set thread context of 2020 3300 b3fa491f988d9eaea26d1e1d3f3f6e811a70cf99602c25f11add6b1516e84d7c.exe 86 -
Suspicious behavior: EnumeratesProcesses 4 IoCs
pid Process 2020 b3fa491f988d9eaea26d1e1d3f3f6e811a70cf99602c25f11add6b1516e84d7c.exe 2020 b3fa491f988d9eaea26d1e1d3f3f6e811a70cf99602c25f11add6b1516e84d7c.exe 2020 b3fa491f988d9eaea26d1e1d3f3f6e811a70cf99602c25f11add6b1516e84d7c.exe 2020 b3fa491f988d9eaea26d1e1d3f3f6e811a70cf99602c25f11add6b1516e84d7c.exe -
Suspicious use of SetWindowsHookEx 1 IoCs
pid Process 3300 b3fa491f988d9eaea26d1e1d3f3f6e811a70cf99602c25f11add6b1516e84d7c.exe -
Suspicious use of WriteProcessMemory 11 IoCs
description pid Process procid_target PID 3300 wrote to memory of 2020 3300 b3fa491f988d9eaea26d1e1d3f3f6e811a70cf99602c25f11add6b1516e84d7c.exe 86 PID 3300 wrote to memory of 2020 3300 b3fa491f988d9eaea26d1e1d3f3f6e811a70cf99602c25f11add6b1516e84d7c.exe 86 PID 3300 wrote to memory of 2020 3300 b3fa491f988d9eaea26d1e1d3f3f6e811a70cf99602c25f11add6b1516e84d7c.exe 86 PID 3300 wrote to memory of 2020 3300 b3fa491f988d9eaea26d1e1d3f3f6e811a70cf99602c25f11add6b1516e84d7c.exe 86 PID 3300 wrote to memory of 2020 3300 b3fa491f988d9eaea26d1e1d3f3f6e811a70cf99602c25f11add6b1516e84d7c.exe 86 PID 3300 wrote to memory of 2020 3300 b3fa491f988d9eaea26d1e1d3f3f6e811a70cf99602c25f11add6b1516e84d7c.exe 86 PID 3300 wrote to memory of 2020 3300 b3fa491f988d9eaea26d1e1d3f3f6e811a70cf99602c25f11add6b1516e84d7c.exe 86 PID 2020 wrote to memory of 2508 2020 b3fa491f988d9eaea26d1e1d3f3f6e811a70cf99602c25f11add6b1516e84d7c.exe 68 PID 2020 wrote to memory of 2508 2020 b3fa491f988d9eaea26d1e1d3f3f6e811a70cf99602c25f11add6b1516e84d7c.exe 68 PID 2020 wrote to memory of 2508 2020 b3fa491f988d9eaea26d1e1d3f3f6e811a70cf99602c25f11add6b1516e84d7c.exe 68 PID 2020 wrote to memory of 2508 2020 b3fa491f988d9eaea26d1e1d3f3f6e811a70cf99602c25f11add6b1516e84d7c.exe 68
Processes
-
C:\Windows\Explorer.EXEC:\Windows\Explorer.EXE1⤵PID:2508
-
C:\Users\Admin\AppData\Local\Temp\b3fa491f988d9eaea26d1e1d3f3f6e811a70cf99602c25f11add6b1516e84d7c.exe"C:\Users\Admin\AppData\Local\Temp\b3fa491f988d9eaea26d1e1d3f3f6e811a70cf99602c25f11add6b1516e84d7c.exe"2⤵
- Suspicious use of SetThreadContext
- Suspicious use of SetWindowsHookEx
- Suspicious use of WriteProcessMemory
PID:3300 -
C:\Users\Admin\AppData\Local\Temp\b3fa491f988d9eaea26d1e1d3f3f6e811a70cf99602c25f11add6b1516e84d7c.exeC:\Users\Admin\AppData\Local\Temp\b3fa491f988d9eaea26d1e1d3f3f6e811a70cf99602c25f11add6b1516e84d7c.exe3⤵
- Suspicious behavior: EnumeratesProcesses
- Suspicious use of WriteProcessMemory
PID:2020
-
-