Analysis
-
max time kernel
171s -
max time network
182s -
platform
windows10-2004_x64 -
resource
win10v2004-20220812-en -
resource tags
arch:x64arch:x86image:win10v2004-20220812-enlocale:en-usos:windows10-2004-x64system -
submitted
27/11/2022, 03:05
Static task
static1
Behavioral task
behavioral1
Sample
ebc4de2d00d1de57287005e56afc97d2fe3653e9e263101050391a186fe93bb9.exe
Resource
win7-20220812-en
Behavioral task
behavioral2
Sample
ebc4de2d00d1de57287005e56afc97d2fe3653e9e263101050391a186fe93bb9.exe
Resource
win10v2004-20220812-en
General
-
Target
ebc4de2d00d1de57287005e56afc97d2fe3653e9e263101050391a186fe93bb9.exe
-
Size
1.0MB
-
MD5
2dc789cf6ab7e403a73644f425f16007
-
SHA1
2d68045348e0dc12d29f545b0fd354289012baca
-
SHA256
ebc4de2d00d1de57287005e56afc97d2fe3653e9e263101050391a186fe93bb9
-
SHA512
8c50e6a333bb254aa07ae7e96ec654561aab239a40e731c6bdc96f57b12fa06b5d826e635dbfb12f9fc3627984617f683dfe1b06b09e578160a29692cf727d27
-
SSDEEP
24576:zlafNPaNMDJOpKROZRpulZBVOkeOLimGHCmO+:RaANaRGRpuHetmGimZ
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\SystemBiosVersion ebc4de2d00d1de57287005e56afc97d2fe3653e9e263101050391a186fe93bb9.exe Key value queried \REGISTRY\MACHINE\HARDWARE\DESCRIPTION\System\VideoBiosVersion ebc4de2d00d1de57287005e56afc97d2fe3653e9e263101050391a186fe93bb9.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 ebc4de2d00d1de57287005e56afc97d2fe3653e9e263101050391a186fe93bb9.exe Key value queried \REGISTRY\MACHINE\SYSTEM\ControlSet001\Services\disk\Enum\0 ebc4de2d00d1de57287005e56afc97d2fe3653e9e263101050391a186fe93bb9.exe -
Suspicious use of SetThreadContext 1 IoCs
description pid Process procid_target PID 4764 set thread context of 4916 4764 ebc4de2d00d1de57287005e56afc97d2fe3653e9e263101050391a186fe93bb9.exe 80 -
Suspicious use of SetWindowsHookEx 6 IoCs
pid Process 4916 ebc4de2d00d1de57287005e56afc97d2fe3653e9e263101050391a186fe93bb9.exe 4916 ebc4de2d00d1de57287005e56afc97d2fe3653e9e263101050391a186fe93bb9.exe 4916 ebc4de2d00d1de57287005e56afc97d2fe3653e9e263101050391a186fe93bb9.exe 4916 ebc4de2d00d1de57287005e56afc97d2fe3653e9e263101050391a186fe93bb9.exe 4916 ebc4de2d00d1de57287005e56afc97d2fe3653e9e263101050391a186fe93bb9.exe 4916 ebc4de2d00d1de57287005e56afc97d2fe3653e9e263101050391a186fe93bb9.exe -
Suspicious use of WriteProcessMemory 10 IoCs
description pid Process procid_target PID 4764 wrote to memory of 4916 4764 ebc4de2d00d1de57287005e56afc97d2fe3653e9e263101050391a186fe93bb9.exe 80 PID 4764 wrote to memory of 4916 4764 ebc4de2d00d1de57287005e56afc97d2fe3653e9e263101050391a186fe93bb9.exe 80 PID 4764 wrote to memory of 4916 4764 ebc4de2d00d1de57287005e56afc97d2fe3653e9e263101050391a186fe93bb9.exe 80 PID 4764 wrote to memory of 4916 4764 ebc4de2d00d1de57287005e56afc97d2fe3653e9e263101050391a186fe93bb9.exe 80 PID 4764 wrote to memory of 4916 4764 ebc4de2d00d1de57287005e56afc97d2fe3653e9e263101050391a186fe93bb9.exe 80 PID 4764 wrote to memory of 4916 4764 ebc4de2d00d1de57287005e56afc97d2fe3653e9e263101050391a186fe93bb9.exe 80 PID 4764 wrote to memory of 4916 4764 ebc4de2d00d1de57287005e56afc97d2fe3653e9e263101050391a186fe93bb9.exe 80 PID 4764 wrote to memory of 4916 4764 ebc4de2d00d1de57287005e56afc97d2fe3653e9e263101050391a186fe93bb9.exe 80 PID 4764 wrote to memory of 4916 4764 ebc4de2d00d1de57287005e56afc97d2fe3653e9e263101050391a186fe93bb9.exe 80 PID 4764 wrote to memory of 4916 4764 ebc4de2d00d1de57287005e56afc97d2fe3653e9e263101050391a186fe93bb9.exe 80
Processes
-
C:\Users\Admin\AppData\Local\Temp\ebc4de2d00d1de57287005e56afc97d2fe3653e9e263101050391a186fe93bb9.exe"C:\Users\Admin\AppData\Local\Temp\ebc4de2d00d1de57287005e56afc97d2fe3653e9e263101050391a186fe93bb9.exe"1⤵
- Checks BIOS information in registry
- Maps connected drives based on registry
- Suspicious use of SetThreadContext
- Suspicious use of WriteProcessMemory
PID:4764 -
C:\Users\Admin\AppData\Local\Temp\ebc4de2d00d1de57287005e56afc97d2fe3653e9e263101050391a186fe93bb9.exe"C:\Users\Admin\AppData\Local\Temp\ebc4de2d00d1de57287005e56afc97d2fe3653e9e263101050391a186fe93bb9.exe" Track="0001001000"2⤵
- Suspicious use of SetWindowsHookEx
PID:4916
-