Analysis
-
max time kernel
136s -
max time network
171s -
platform
windows10-2004_x64 -
resource
win10v2004-20220812-en -
resource tags
arch:x64arch:x86image:win10v2004-20220812-enlocale:en-usos:windows10-2004-x64system -
submitted
28-11-2022 07:47
Static task
static1
Behavioral task
behavioral1
Sample
fd7786f950249c6359cbbfed4ee3159654be1a376e0743690a6e8a9c469a8901.exe
Resource
win7-20220812-en
Behavioral task
behavioral2
Sample
fd7786f950249c6359cbbfed4ee3159654be1a376e0743690a6e8a9c469a8901.exe
Resource
win10v2004-20220812-en
General
-
Target
fd7786f950249c6359cbbfed4ee3159654be1a376e0743690a6e8a9c469a8901.exe
-
Size
959KB
-
MD5
09f6910998b75b3b7cf37f0f0fc47dc1
-
SHA1
767a15ad8950032ae4deec013b89106c84848c0b
-
SHA256
fd7786f950249c6359cbbfed4ee3159654be1a376e0743690a6e8a9c469a8901
-
SHA512
541e20b56963c18dbae8fa0afb090ef82affb00fc0629fd2ba67cd448cb1e1b368220fb118615dabd103c10ee55e3b19a01eeea1e1a344c8caf1ef04c3e4722a
-
SSDEEP
24576:8kb9GXioEE6FY5fQ5emJYeXOxXzF6oHU9gH:8khGXiBE6FY1ps656tgH
Malware Config
Signatures
-
Checks BIOS information in registry 2 TTPs 2 IoCs
BIOS information is often read in order to detect sandboxing environments.
description ioc Process Key value queried \REGISTRY\MACHINE\HARDWARE\DESCRIPTION\System\VideoBiosVersion fd7786f950249c6359cbbfed4ee3159654be1a376e0743690a6e8a9c469a8901.exe Key value queried \REGISTRY\MACHINE\HARDWARE\DESCRIPTION\System\SystemBiosVersion fd7786f950249c6359cbbfed4ee3159654be1a376e0743690a6e8a9c469a8901.exe -
Maps connected drives based on registry 3 TTPs 2 IoCs
Disk information is often read in order to detect sandboxing environments.
description ioc Process Key opened \REGISTRY\MACHINE\SYSTEM\ControlSet001\Services\Disk\Enum fd7786f950249c6359cbbfed4ee3159654be1a376e0743690a6e8a9c469a8901.exe Key value queried \REGISTRY\MACHINE\SYSTEM\ControlSet001\Services\disk\Enum\0 fd7786f950249c6359cbbfed4ee3159654be1a376e0743690a6e8a9c469a8901.exe -
Suspicious use of SetThreadContext 1 IoCs
description pid Process procid_target PID 872 set thread context of 4976 872 fd7786f950249c6359cbbfed4ee3159654be1a376e0743690a6e8a9c469a8901.exe 81 -
Suspicious use of SetWindowsHookEx 6 IoCs
pid Process 4976 fd7786f950249c6359cbbfed4ee3159654be1a376e0743690a6e8a9c469a8901.exe 4976 fd7786f950249c6359cbbfed4ee3159654be1a376e0743690a6e8a9c469a8901.exe 4976 fd7786f950249c6359cbbfed4ee3159654be1a376e0743690a6e8a9c469a8901.exe 4976 fd7786f950249c6359cbbfed4ee3159654be1a376e0743690a6e8a9c469a8901.exe 4976 fd7786f950249c6359cbbfed4ee3159654be1a376e0743690a6e8a9c469a8901.exe 4976 fd7786f950249c6359cbbfed4ee3159654be1a376e0743690a6e8a9c469a8901.exe -
Suspicious use of WriteProcessMemory 10 IoCs
description pid Process procid_target PID 872 wrote to memory of 4976 872 fd7786f950249c6359cbbfed4ee3159654be1a376e0743690a6e8a9c469a8901.exe 81 PID 872 wrote to memory of 4976 872 fd7786f950249c6359cbbfed4ee3159654be1a376e0743690a6e8a9c469a8901.exe 81 PID 872 wrote to memory of 4976 872 fd7786f950249c6359cbbfed4ee3159654be1a376e0743690a6e8a9c469a8901.exe 81 PID 872 wrote to memory of 4976 872 fd7786f950249c6359cbbfed4ee3159654be1a376e0743690a6e8a9c469a8901.exe 81 PID 872 wrote to memory of 4976 872 fd7786f950249c6359cbbfed4ee3159654be1a376e0743690a6e8a9c469a8901.exe 81 PID 872 wrote to memory of 4976 872 fd7786f950249c6359cbbfed4ee3159654be1a376e0743690a6e8a9c469a8901.exe 81 PID 872 wrote to memory of 4976 872 fd7786f950249c6359cbbfed4ee3159654be1a376e0743690a6e8a9c469a8901.exe 81 PID 872 wrote to memory of 4976 872 fd7786f950249c6359cbbfed4ee3159654be1a376e0743690a6e8a9c469a8901.exe 81 PID 872 wrote to memory of 4976 872 fd7786f950249c6359cbbfed4ee3159654be1a376e0743690a6e8a9c469a8901.exe 81 PID 872 wrote to memory of 4976 872 fd7786f950249c6359cbbfed4ee3159654be1a376e0743690a6e8a9c469a8901.exe 81
Processes
-
C:\Users\Admin\AppData\Local\Temp\fd7786f950249c6359cbbfed4ee3159654be1a376e0743690a6e8a9c469a8901.exe"C:\Users\Admin\AppData\Local\Temp\fd7786f950249c6359cbbfed4ee3159654be1a376e0743690a6e8a9c469a8901.exe"1⤵
- Checks BIOS information in registry
- Maps connected drives based on registry
- Suspicious use of SetThreadContext
- Suspicious use of WriteProcessMemory
PID:872 -
C:\Users\Admin\AppData\Local\Temp\fd7786f950249c6359cbbfed4ee3159654be1a376e0743690a6e8a9c469a8901.exe"C:\Users\Admin\AppData\Local\Temp\fd7786f950249c6359cbbfed4ee3159654be1a376e0743690a6e8a9c469a8901.exe" Track="0001101000"2⤵
- Suspicious use of SetWindowsHookEx
PID:4976
-