Analysis
-
max time kernel
143s -
max time network
151s -
platform
windows7_x64 -
resource
win7-20220901-en -
resource tags
arch:x64arch:x86image:win7-20220901-enlocale:en-usos:windows7-x64system -
submitted
29/10/2022, 13:29
Static task
static1
Behavioral task
behavioral1
Sample
cf3e3a9b003e109efbbbeddcd85fb692354d90d1c10673976fd8d5406cc70144.exe
Resource
win7-20220901-en
Behavioral task
behavioral2
Sample
cf3e3a9b003e109efbbbeddcd85fb692354d90d1c10673976fd8d5406cc70144.exe
Resource
win10v2004-20220812-en
General
-
Target
cf3e3a9b003e109efbbbeddcd85fb692354d90d1c10673976fd8d5406cc70144.exe
-
Size
70KB
-
MD5
0a17f1947f34d487a1340e70d71f8c4b
-
SHA1
cc4726d9bb28cf28d661aeae9e6b50de0417c83c
-
SHA256
cf3e3a9b003e109efbbbeddcd85fb692354d90d1c10673976fd8d5406cc70144
-
SHA512
61da36e6eb7381d512a5e19f677041f2fc6d74e6c9dcabc52b3ad8c7965266f0e0fbc89e549765b26f1929ae72a13f2d76ab3801bd89f922e4b8a07c13f15caa
-
SSDEEP
1536:G5KMGwMPrZ3SNmLQLhz/sgoouGS/f/JaAg9uXvWSAoh9:G6DVSNmEzUpBpo9ob9
Malware Config
Signatures
-
Reads user/profile data of web browsers 2 TTPs
Infostealers often target stored browser data, which can include saved credentials etc.
-
Adds Run key to start application 2 TTPs 1 IoCs
description ioc Process Set value (str) \REGISTRY\USER\S-1-5-21-4063495947-34355257-727531523-1000\Software\Microsoft\Windows\CurrentVersion\Run\EvtMgr = "c:\\td49vvt3tq32vme\\Dxqbxfe.exe /Klaunchp" Dxqbxfe.exe -
Enumerates connected drives 3 TTPs 24 IoCs
Attempts to read the root path of hard drives other than the default C: drive.
description ioc Process File opened (read-only) \??\g: Dxqbxfe.exe File opened (read-only) \??\i: Dxqbxfe.exe File opened (read-only) \??\r: Dxqbxfe.exe File opened (read-only) \??\t: Dxqbxfe.exe File opened (read-only) \??\b: Dxqbxfe.exe File opened (read-only) \??\f: Dxqbxfe.exe File opened (read-only) \??\o: Dxqbxfe.exe File opened (read-only) \??\p: Dxqbxfe.exe File opened (read-only) \??\w: Dxqbxfe.exe File opened (read-only) \??\j: Dxqbxfe.exe File opened (read-only) \??\l: Dxqbxfe.exe File opened (read-only) \??\k: Dxqbxfe.exe File opened (read-only) \??\m: Dxqbxfe.exe File opened (read-only) \??\n: Dxqbxfe.exe File opened (read-only) \??\e: Dxqbxfe.exe File opened (read-only) \??\h: Dxqbxfe.exe File opened (read-only) \??\s: Dxqbxfe.exe File opened (read-only) \??\u: Dxqbxfe.exe File opened (read-only) \??\v: Dxqbxfe.exe File opened (read-only) \??\x: Dxqbxfe.exe File opened (read-only) \??\y: Dxqbxfe.exe File opened (read-only) \??\z: Dxqbxfe.exe File opened (read-only) \??\a: Dxqbxfe.exe File opened (read-only) \??\q: Dxqbxfe.exe -
Writes to the Master Boot Record (MBR) 1 TTPs 2 IoCs
Bootkits write to the MBR to gain persistence at a level below the operating system.
description ioc Process File opened for modification \??\PHYSICALDRIVE0 cf3e3a9b003e109efbbbeddcd85fb692354d90d1c10673976fd8d5406cc70144.exe File opened for modification \??\PHYSICALDRIVE0 Dxqbxfe.exe -
Checks processor information in registry 2 TTPs 2 IoCs
Processor information is often read in order to detect sandboxing environments.
description ioc Process Key opened \REGISTRY\MACHINE\HARDWARE\DESCRIPTION\System\CentralProcessor\0 Dxqbxfe.exe Key value queried \REGISTRY\MACHINE\HARDWARE\DESCRIPTION\System\CentralProcessor\0\ProcessorNameString Dxqbxfe.exe -
Suspicious behavior: EnumeratesProcesses 2 IoCs
pid Process 840 Dxqbxfe.exe 840 Dxqbxfe.exe -
Suspicious behavior: RenamesItself 1 IoCs
pid Process 1768 cf3e3a9b003e109efbbbeddcd85fb692354d90d1c10673976fd8d5406cc70144.exe -
Suspicious use of AdjustPrivilegeToken 5 IoCs
description pid Process Token: SeDebugPrivilege 1768 cf3e3a9b003e109efbbbeddcd85fb692354d90d1c10673976fd8d5406cc70144.exe Token: SeDebugPrivilege 1768 cf3e3a9b003e109efbbbeddcd85fb692354d90d1c10673976fd8d5406cc70144.exe Token: SeDebugPrivilege 840 Dxqbxfe.exe Token: SeDebugPrivilege 840 Dxqbxfe.exe Token: SeDebugPrivilege 840 Dxqbxfe.exe -
Suspicious use of SetWindowsHookEx 2 IoCs
pid Process 1768 cf3e3a9b003e109efbbbeddcd85fb692354d90d1c10673976fd8d5406cc70144.exe 840 Dxqbxfe.exe -
Suspicious use of WriteProcessMemory 4 IoCs
description pid Process procid_target PID 1768 wrote to memory of 840 1768 cf3e3a9b003e109efbbbeddcd85fb692354d90d1c10673976fd8d5406cc70144.exe 27 PID 1768 wrote to memory of 840 1768 cf3e3a9b003e109efbbbeddcd85fb692354d90d1c10673976fd8d5406cc70144.exe 27 PID 1768 wrote to memory of 840 1768 cf3e3a9b003e109efbbbeddcd85fb692354d90d1c10673976fd8d5406cc70144.exe 27 PID 1768 wrote to memory of 840 1768 cf3e3a9b003e109efbbbeddcd85fb692354d90d1c10673976fd8d5406cc70144.exe 27
Processes
-
C:\Users\Admin\AppData\Local\Temp\cf3e3a9b003e109efbbbeddcd85fb692354d90d1c10673976fd8d5406cc70144.exe"C:\Users\Admin\AppData\Local\Temp\cf3e3a9b003e109efbbbeddcd85fb692354d90d1c10673976fd8d5406cc70144.exe"1⤵
- Writes to the Master Boot Record (MBR)
- Suspicious behavior: RenamesItself
- Suspicious use of AdjustPrivilegeToken
- Suspicious use of SetWindowsHookEx
- Suspicious use of WriteProcessMemory
PID:1768 -
\??\c:\td49vvt3tq32vme\Dxqbxfe.exelaunch2⤵
- Adds Run key to start application
- Enumerates connected drives
- Writes to the Master Boot Record (MBR)
- Checks processor information in registry
- Suspicious behavior: EnumeratesProcesses
- Suspicious use of AdjustPrivilegeToken
- Suspicious use of SetWindowsHookEx
PID:840
-