Analysis
-
max time kernel
148s -
max time network
153s -
platform
windows7_x64 -
resource
win7-20240221-en -
resource tags
arch:x64arch:x86image:win7-20240221-enlocale:en-usos:windows7-x64system -
submitted
12-03-2024 04:34
Static task
static1
Behavioral task
behavioral1
Sample
efb100b1174ae52287b3119bb43a6e50.exe
Resource
win7-20240221-en
Behavioral task
behavioral2
Sample
efb100b1174ae52287b3119bb43a6e50.exe
Resource
win10v2004-20240226-en
General
-
Target
efb100b1174ae52287b3119bb43a6e50.exe
-
Size
308KB
-
MD5
efb100b1174ae52287b3119bb43a6e50
-
SHA1
ddd88c1fccd2ce77cef76d0b4f95d88bb9862036
-
SHA256
33696c9ae9e42910f5c8cc5ad818c36592ac19fc7d9b1c724b72f8fedff4460f
-
SHA512
c92ee49f334570f2ff501f5c60573a9b64a29207bf7d6e1d1297378f2ac00aa39ed22552fcb3464fc8cb0d8164ed4e01d2ade98320c4b6dcb550145f36eafc16
-
SSDEEP
6144:hzL7ShWDLVzVNam6GxI29dqG3KdYAYqTuPZp:vDHNam62ZdKmZmuPH
Malware Config
Signatures
-
GandCrab payload 4 IoCs
resource yara_rule behavioral1/memory/2848-2-0x0000000000400000-0x0000000001400000-memory.dmp family_gandcrab behavioral1/memory/2848-3-0x0000000000260000-0x0000000000277000-memory.dmp family_gandcrab behavioral1/memory/2848-10-0x0000000000400000-0x0000000001400000-memory.dmp family_gandcrab behavioral1/memory/2848-13-0x0000000000260000-0x0000000000277000-memory.dmp family_gandcrab -
Gandcrab
Gandcrab is a Trojan horse that encrypts files on a computer.
-
Adds Run key to start application 2 TTPs 1 IoCs
description ioc Process Set value (str) \REGISTRY\MACHINE\SOFTWARE\Wow6432Node\Microsoft\Windows\CurrentVersion\RunOnce\ilidvokqqwi = "\"C:\\Users\\Admin\\AppData\\Roaming\\Microsoft\\fazkzf.exe\"" efb100b1174ae52287b3119bb43a6e50.exe -
Enumerates connected drives 3 TTPs 23 IoCs
Attempts to read the root path of hard drives other than the default C: drive.
description ioc Process File opened (read-only) \??\J: efb100b1174ae52287b3119bb43a6e50.exe File opened (read-only) \??\P: efb100b1174ae52287b3119bb43a6e50.exe File opened (read-only) \??\T: efb100b1174ae52287b3119bb43a6e50.exe File opened (read-only) \??\U: efb100b1174ae52287b3119bb43a6e50.exe File opened (read-only) \??\Z: efb100b1174ae52287b3119bb43a6e50.exe File opened (read-only) \??\S: efb100b1174ae52287b3119bb43a6e50.exe File opened (read-only) \??\X: efb100b1174ae52287b3119bb43a6e50.exe File opened (read-only) \??\B: efb100b1174ae52287b3119bb43a6e50.exe File opened (read-only) \??\I: efb100b1174ae52287b3119bb43a6e50.exe File opened (read-only) \??\K: efb100b1174ae52287b3119bb43a6e50.exe File opened (read-only) \??\L: efb100b1174ae52287b3119bb43a6e50.exe File opened (read-only) \??\M: efb100b1174ae52287b3119bb43a6e50.exe File opened (read-only) \??\O: efb100b1174ae52287b3119bb43a6e50.exe File opened (read-only) \??\Y: efb100b1174ae52287b3119bb43a6e50.exe File opened (read-only) \??\G: efb100b1174ae52287b3119bb43a6e50.exe File opened (read-only) \??\H: efb100b1174ae52287b3119bb43a6e50.exe File opened (read-only) \??\R: efb100b1174ae52287b3119bb43a6e50.exe File opened (read-only) \??\W: efb100b1174ae52287b3119bb43a6e50.exe File opened (read-only) \??\A: efb100b1174ae52287b3119bb43a6e50.exe File opened (read-only) \??\E: efb100b1174ae52287b3119bb43a6e50.exe File opened (read-only) \??\N: efb100b1174ae52287b3119bb43a6e50.exe File opened (read-only) \??\Q: efb100b1174ae52287b3119bb43a6e50.exe File opened (read-only) \??\V: efb100b1174ae52287b3119bb43a6e50.exe -
Checks processor information in registry 2 TTPs 3 IoCs
Processor information is often read in order to detect sandboxing environments.
description ioc Process Key opened \REGISTRY\MACHINE\HARDWARE\DESCRIPTION\System\CentralProcessor\0 efb100b1174ae52287b3119bb43a6e50.exe Key value queried \REGISTRY\MACHINE\HARDWARE\DESCRIPTION\System\CentralProcessor\0\ProcessorNameString efb100b1174ae52287b3119bb43a6e50.exe Key value queried \REGISTRY\MACHINE\HARDWARE\DESCRIPTION\System\CentralProcessor\0\Identifier efb100b1174ae52287b3119bb43a6e50.exe -
Suspicious behavior: EnumeratesProcesses 2 IoCs
pid Process 2848 efb100b1174ae52287b3119bb43a6e50.exe 2848 efb100b1174ae52287b3119bb43a6e50.exe -
Suspicious use of WriteProcessMemory 64 IoCs
description pid Process procid_target PID 2848 wrote to memory of 2952 2848 efb100b1174ae52287b3119bb43a6e50.exe 28 PID 2848 wrote to memory of 2952 2848 efb100b1174ae52287b3119bb43a6e50.exe 28 PID 2848 wrote to memory of 2952 2848 efb100b1174ae52287b3119bb43a6e50.exe 28 PID 2848 wrote to memory of 2952 2848 efb100b1174ae52287b3119bb43a6e50.exe 28 PID 2848 wrote to memory of 2548 2848 efb100b1174ae52287b3119bb43a6e50.exe 30 PID 2848 wrote to memory of 2548 2848 efb100b1174ae52287b3119bb43a6e50.exe 30 PID 2848 wrote to memory of 2548 2848 efb100b1174ae52287b3119bb43a6e50.exe 30 PID 2848 wrote to memory of 2548 2848 efb100b1174ae52287b3119bb43a6e50.exe 30 PID 2848 wrote to memory of 2552 2848 efb100b1174ae52287b3119bb43a6e50.exe 32 PID 2848 wrote to memory of 2552 2848 efb100b1174ae52287b3119bb43a6e50.exe 32 PID 2848 wrote to memory of 2552 2848 efb100b1174ae52287b3119bb43a6e50.exe 32 PID 2848 wrote to memory of 2552 2848 efb100b1174ae52287b3119bb43a6e50.exe 32 PID 2848 wrote to memory of 2648 2848 efb100b1174ae52287b3119bb43a6e50.exe 34 PID 2848 wrote to memory of 2648 2848 efb100b1174ae52287b3119bb43a6e50.exe 34 PID 2848 wrote to memory of 2648 2848 efb100b1174ae52287b3119bb43a6e50.exe 34 PID 2848 wrote to memory of 2648 2848 efb100b1174ae52287b3119bb43a6e50.exe 34 PID 2848 wrote to memory of 2664 2848 efb100b1174ae52287b3119bb43a6e50.exe 36 PID 2848 wrote to memory of 2664 2848 efb100b1174ae52287b3119bb43a6e50.exe 36 PID 2848 wrote to memory of 2664 2848 efb100b1174ae52287b3119bb43a6e50.exe 36 PID 2848 wrote to memory of 2664 2848 efb100b1174ae52287b3119bb43a6e50.exe 36 PID 2848 wrote to memory of 2924 2848 efb100b1174ae52287b3119bb43a6e50.exe 40 PID 2848 wrote to memory of 2924 2848 efb100b1174ae52287b3119bb43a6e50.exe 40 PID 2848 wrote to memory of 2924 2848 efb100b1174ae52287b3119bb43a6e50.exe 40 PID 2848 wrote to memory of 2924 2848 efb100b1174ae52287b3119bb43a6e50.exe 40 PID 2848 wrote to memory of 528 2848 efb100b1174ae52287b3119bb43a6e50.exe 42 PID 2848 wrote to memory of 528 2848 efb100b1174ae52287b3119bb43a6e50.exe 42 PID 2848 wrote to memory of 528 2848 efb100b1174ae52287b3119bb43a6e50.exe 42 PID 2848 wrote to memory of 528 2848 efb100b1174ae52287b3119bb43a6e50.exe 42 PID 2848 wrote to memory of 1740 2848 efb100b1174ae52287b3119bb43a6e50.exe 44 PID 2848 wrote to memory of 1740 2848 efb100b1174ae52287b3119bb43a6e50.exe 44 PID 2848 wrote to memory of 1740 2848 efb100b1174ae52287b3119bb43a6e50.exe 44 PID 2848 wrote to memory of 1740 2848 efb100b1174ae52287b3119bb43a6e50.exe 44 PID 2848 wrote to memory of 880 2848 efb100b1174ae52287b3119bb43a6e50.exe 46 PID 2848 wrote to memory of 880 2848 efb100b1174ae52287b3119bb43a6e50.exe 46 PID 2848 wrote to memory of 880 2848 efb100b1174ae52287b3119bb43a6e50.exe 46 PID 2848 wrote to memory of 880 2848 efb100b1174ae52287b3119bb43a6e50.exe 46 PID 2848 wrote to memory of 380 2848 efb100b1174ae52287b3119bb43a6e50.exe 48 PID 2848 wrote to memory of 380 2848 efb100b1174ae52287b3119bb43a6e50.exe 48 PID 2848 wrote to memory of 380 2848 efb100b1174ae52287b3119bb43a6e50.exe 48 PID 2848 wrote to memory of 380 2848 efb100b1174ae52287b3119bb43a6e50.exe 48 PID 2848 wrote to memory of 2748 2848 efb100b1174ae52287b3119bb43a6e50.exe 50 PID 2848 wrote to memory of 2748 2848 efb100b1174ae52287b3119bb43a6e50.exe 50 PID 2848 wrote to memory of 2748 2848 efb100b1174ae52287b3119bb43a6e50.exe 50 PID 2848 wrote to memory of 2748 2848 efb100b1174ae52287b3119bb43a6e50.exe 50 PID 2848 wrote to memory of 860 2848 efb100b1174ae52287b3119bb43a6e50.exe 52 PID 2848 wrote to memory of 860 2848 efb100b1174ae52287b3119bb43a6e50.exe 52 PID 2848 wrote to memory of 860 2848 efb100b1174ae52287b3119bb43a6e50.exe 52 PID 2848 wrote to memory of 860 2848 efb100b1174ae52287b3119bb43a6e50.exe 52 PID 2848 wrote to memory of 940 2848 efb100b1174ae52287b3119bb43a6e50.exe 54 PID 2848 wrote to memory of 940 2848 efb100b1174ae52287b3119bb43a6e50.exe 54 PID 2848 wrote to memory of 940 2848 efb100b1174ae52287b3119bb43a6e50.exe 54 PID 2848 wrote to memory of 940 2848 efb100b1174ae52287b3119bb43a6e50.exe 54 PID 2848 wrote to memory of 2916 2848 efb100b1174ae52287b3119bb43a6e50.exe 56 PID 2848 wrote to memory of 2916 2848 efb100b1174ae52287b3119bb43a6e50.exe 56 PID 2848 wrote to memory of 2916 2848 efb100b1174ae52287b3119bb43a6e50.exe 56 PID 2848 wrote to memory of 2916 2848 efb100b1174ae52287b3119bb43a6e50.exe 56 PID 2848 wrote to memory of 1720 2848 efb100b1174ae52287b3119bb43a6e50.exe 58 PID 2848 wrote to memory of 1720 2848 efb100b1174ae52287b3119bb43a6e50.exe 58 PID 2848 wrote to memory of 1720 2848 efb100b1174ae52287b3119bb43a6e50.exe 58 PID 2848 wrote to memory of 1720 2848 efb100b1174ae52287b3119bb43a6e50.exe 58 PID 2848 wrote to memory of 1464 2848 efb100b1174ae52287b3119bb43a6e50.exe 60 PID 2848 wrote to memory of 1464 2848 efb100b1174ae52287b3119bb43a6e50.exe 60 PID 2848 wrote to memory of 1464 2848 efb100b1174ae52287b3119bb43a6e50.exe 60 PID 2848 wrote to memory of 1464 2848 efb100b1174ae52287b3119bb43a6e50.exe 60
Processes
-
C:\Users\Admin\AppData\Local\Temp\efb100b1174ae52287b3119bb43a6e50.exe"C:\Users\Admin\AppData\Local\Temp\efb100b1174ae52287b3119bb43a6e50.exe"1⤵
- Adds Run key to start application
- Enumerates connected drives
- Checks processor information in registry
- Suspicious behavior: EnumeratesProcesses
- Suspicious use of WriteProcessMemory
PID:2848 -
C:\Windows\SysWOW64\nslookup.exenslookup carder.bit ns1.wowservers.ru2⤵PID:2952
-
-
C:\Windows\SysWOW64\nslookup.exenslookup ransomware.bit ns2.wowservers.ru2⤵PID:2548
-
-
C:\Windows\SysWOW64\nslookup.exenslookup carder.bit ns2.wowservers.ru2⤵PID:2552
-
-
C:\Windows\SysWOW64\nslookup.exenslookup ransomware.bit ns1.wowservers.ru2⤵PID:2648
-
-
C:\Windows\SysWOW64\nslookup.exenslookup carder.bit ns1.wowservers.ru2⤵PID:2664
-
-
C:\Windows\SysWOW64\nslookup.exenslookup ransomware.bit ns2.wowservers.ru2⤵PID:2924
-
-
C:\Windows\SysWOW64\nslookup.exenslookup carder.bit ns2.wowservers.ru2⤵PID:528
-
-
C:\Windows\SysWOW64\nslookup.exenslookup ransomware.bit ns1.wowservers.ru2⤵PID:1740
-
-
C:\Windows\SysWOW64\nslookup.exenslookup carder.bit ns1.wowservers.ru2⤵PID:880
-
-
C:\Windows\SysWOW64\nslookup.exenslookup ransomware.bit ns2.wowservers.ru2⤵PID:380
-
-
C:\Windows\SysWOW64\nslookup.exenslookup carder.bit ns2.wowservers.ru2⤵PID:2748
-
-
C:\Windows\SysWOW64\nslookup.exenslookup ransomware.bit ns1.wowservers.ru2⤵PID:860
-
-
C:\Windows\SysWOW64\nslookup.exenslookup carder.bit ns1.wowservers.ru2⤵PID:940
-
-
C:\Windows\SysWOW64\nslookup.exenslookup ransomware.bit ns2.wowservers.ru2⤵PID:2916
-
-
C:\Windows\SysWOW64\nslookup.exenslookup carder.bit ns2.wowservers.ru2⤵PID:1720
-
-
C:\Windows\SysWOW64\nslookup.exenslookup ransomware.bit ns1.wowservers.ru2⤵PID:1464
-
-
C:\Windows\SysWOW64\nslookup.exenslookup carder.bit ns1.wowservers.ru2⤵PID:764
-
-
C:\Windows\SysWOW64\nslookup.exenslookup ransomware.bit ns2.wowservers.ru2⤵PID:1924
-
-
C:\Windows\SysWOW64\nslookup.exenslookup carder.bit ns2.wowservers.ru2⤵PID:1812
-
-
C:\Windows\SysWOW64\nslookup.exenslookup ransomware.bit ns1.wowservers.ru2⤵PID:1144
-
-
C:\Windows\SysWOW64\nslookup.exenslookup carder.bit ns1.wowservers.ru2⤵PID:1964
-
-
C:\Windows\SysWOW64\nslookup.exenslookup ransomware.bit ns2.wowservers.ru2⤵PID:1120
-