Analysis
-
max time kernel
128s -
max time network
132s -
platform
windows10-2004_x64 -
resource
win10v2004-20220812-en -
resource tags
arch:x64arch:x86image:win10v2004-20220812-enlocale:en-usos:windows10-2004-x64system -
submitted
03/10/2022, 13:41
Behavioral task
behavioral1
Sample
bc8b3a06a727dd28d3a7b56d7cb505065a040cd0be1f1d2cb4fd8b9a9988dedc.exe
Resource
win7-20220901-en
4 signatures
150 seconds
Behavioral task
behavioral2
Sample
bc8b3a06a727dd28d3a7b56d7cb505065a040cd0be1f1d2cb4fd8b9a9988dedc.exe
Resource
win10v2004-20220812-en
4 signatures
150 seconds
General
-
Target
bc8b3a06a727dd28d3a7b56d7cb505065a040cd0be1f1d2cb4fd8b9a9988dedc.exe
-
Size
266KB
-
MD5
0965feb61ace66db671790023743c58b
-
SHA1
92df912d2c8bca3e720a45213ea8b126f836c925
-
SHA256
bc8b3a06a727dd28d3a7b56d7cb505065a040cd0be1f1d2cb4fd8b9a9988dedc
-
SHA512
7a04ce2903bf997fe8674a9ef58e74df03cb1fbe3d250cd8e25af8565c0e1a85a89bf3b3776e5bf8392b6b8958556dfd651f1ce017c9061f6a8ea3a99585779f
-
SSDEEP
6144:7pprn6Eb4TgkGNI8XIwFcEeFBSKfMNCBXYScCB1:7HjH4UIs7+DSYMNCBI5CB1
Score
5/10
Malware Config
Signatures
-
Suspicious use of SetThreadContext 1 IoCs
description pid Process procid_target PID 628 set thread context of 2384 628 bc8b3a06a727dd28d3a7b56d7cb505065a040cd0be1f1d2cb4fd8b9a9988dedc.exe 82 -
Suspicious behavior: EnumeratesProcesses 4 IoCs
pid Process 2384 bc8b3a06a727dd28d3a7b56d7cb505065a040cd0be1f1d2cb4fd8b9a9988dedc.exe 2384 bc8b3a06a727dd28d3a7b56d7cb505065a040cd0be1f1d2cb4fd8b9a9988dedc.exe 2384 bc8b3a06a727dd28d3a7b56d7cb505065a040cd0be1f1d2cb4fd8b9a9988dedc.exe 2384 bc8b3a06a727dd28d3a7b56d7cb505065a040cd0be1f1d2cb4fd8b9a9988dedc.exe -
Suspicious use of SetWindowsHookEx 1 IoCs
pid Process 628 bc8b3a06a727dd28d3a7b56d7cb505065a040cd0be1f1d2cb4fd8b9a9988dedc.exe -
Suspicious use of WriteProcessMemory 11 IoCs
description pid Process procid_target PID 628 wrote to memory of 2384 628 bc8b3a06a727dd28d3a7b56d7cb505065a040cd0be1f1d2cb4fd8b9a9988dedc.exe 82 PID 628 wrote to memory of 2384 628 bc8b3a06a727dd28d3a7b56d7cb505065a040cd0be1f1d2cb4fd8b9a9988dedc.exe 82 PID 628 wrote to memory of 2384 628 bc8b3a06a727dd28d3a7b56d7cb505065a040cd0be1f1d2cb4fd8b9a9988dedc.exe 82 PID 628 wrote to memory of 2384 628 bc8b3a06a727dd28d3a7b56d7cb505065a040cd0be1f1d2cb4fd8b9a9988dedc.exe 82 PID 628 wrote to memory of 2384 628 bc8b3a06a727dd28d3a7b56d7cb505065a040cd0be1f1d2cb4fd8b9a9988dedc.exe 82 PID 628 wrote to memory of 2384 628 bc8b3a06a727dd28d3a7b56d7cb505065a040cd0be1f1d2cb4fd8b9a9988dedc.exe 82 PID 628 wrote to memory of 2384 628 bc8b3a06a727dd28d3a7b56d7cb505065a040cd0be1f1d2cb4fd8b9a9988dedc.exe 82 PID 2384 wrote to memory of 2016 2384 bc8b3a06a727dd28d3a7b56d7cb505065a040cd0be1f1d2cb4fd8b9a9988dedc.exe 57 PID 2384 wrote to memory of 2016 2384 bc8b3a06a727dd28d3a7b56d7cb505065a040cd0be1f1d2cb4fd8b9a9988dedc.exe 57 PID 2384 wrote to memory of 2016 2384 bc8b3a06a727dd28d3a7b56d7cb505065a040cd0be1f1d2cb4fd8b9a9988dedc.exe 57 PID 2384 wrote to memory of 2016 2384 bc8b3a06a727dd28d3a7b56d7cb505065a040cd0be1f1d2cb4fd8b9a9988dedc.exe 57
Processes
-
C:\Windows\Explorer.EXEC:\Windows\Explorer.EXE1⤵PID:2016
-
C:\Users\Admin\AppData\Local\Temp\bc8b3a06a727dd28d3a7b56d7cb505065a040cd0be1f1d2cb4fd8b9a9988dedc.exe"C:\Users\Admin\AppData\Local\Temp\bc8b3a06a727dd28d3a7b56d7cb505065a040cd0be1f1d2cb4fd8b9a9988dedc.exe"2⤵
- Suspicious use of SetThreadContext
- Suspicious use of SetWindowsHookEx
- Suspicious use of WriteProcessMemory
PID:628 -
C:\Users\Admin\AppData\Local\Temp\bc8b3a06a727dd28d3a7b56d7cb505065a040cd0be1f1d2cb4fd8b9a9988dedc.exeC:\Users\Admin\AppData\Local\Temp\bc8b3a06a727dd28d3a7b56d7cb505065a040cd0be1f1d2cb4fd8b9a9988dedc.exe3⤵
- Suspicious behavior: EnumeratesProcesses
- Suspicious use of WriteProcessMemory
PID:2384
-
-