Analysis
-
max time kernel
150s -
max time network
154s -
platform
windows7_x64 -
resource
win7-20220901-en -
resource tags
arch:x64arch:x86image:win7-20220901-enlocale:en-usos:windows7-x64system -
submitted
08/09/2022, 19:39
Static task
static1
Behavioral task
behavioral1
Sample
a2e6bfd745bc83b4f14aea053eb4fe3a.exe
Resource
win7-20220901-en
Behavioral task
behavioral2
Sample
a2e6bfd745bc83b4f14aea053eb4fe3a.exe
Resource
win10v2004-20220812-en
General
-
Target
a2e6bfd745bc83b4f14aea053eb4fe3a.exe
-
Size
320KB
-
MD5
a2e6bfd745bc83b4f14aea053eb4fe3a
-
SHA1
210a88e6f3a38fe020eb1f2cc6acb515e512d09e
-
SHA256
cbf38461235deb57b33399dc72694cd95b13c0bb5e30b80829955850f1296090
-
SHA512
65db02ffdf2385d662757af9302706e21390a859163232d02135b2071a860b006da41e7fe92f5bef46625b4d3d9d3633be52a411bd6ff8f3502c3c0b6b2289e9
-
SSDEEP
3072:BbRXn2p4B/51pzVyqZ5iQ88ZJmj3h2OdyC9aNhw3cvo2bDi5fBbHHD+FtW89:Bb9+g/pzVwQ82Jm7h2As36CtaJHjN89
Malware Config
Signatures
-
GandCrab payload 4 IoCs
resource yara_rule behavioral1/memory/1672-56-0x0000000000400000-0x000000000238C000-memory.dmp family_gandcrab behavioral1/memory/1672-59-0x0000000000400000-0x000000000238C000-memory.dmp family_gandcrab behavioral1/memory/1672-60-0x0000000000250000-0x0000000000267000-memory.dmp family_gandcrab behavioral1/memory/1672-66-0x0000000000250000-0x0000000000267000-memory.dmp family_gandcrab -
Gandcrab
Gandcrab is a Trojan horse that encrypts files on a computer.
-
Adds Run key to start application 2 TTPs 2 IoCs
description ioc Process Key created \REGISTRY\MACHINE\SOFTWARE\Wow6432Node\Microsoft\Windows\CurrentVersion\RunOnce a2e6bfd745bc83b4f14aea053eb4fe3a.exe Set value (str) \REGISTRY\MACHINE\SOFTWARE\Wow6432Node\Microsoft\Windows\CurrentVersion\RunOnce\cpjacegenhw = "\"C:\\Users\\Admin\\AppData\\Roaming\\Microsoft\\hmetcd.exe\"" a2e6bfd745bc83b4f14aea053eb4fe3a.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) \??\B: a2e6bfd745bc83b4f14aea053eb4fe3a.exe File opened (read-only) \??\L: a2e6bfd745bc83b4f14aea053eb4fe3a.exe File opened (read-only) \??\N: a2e6bfd745bc83b4f14aea053eb4fe3a.exe File opened (read-only) \??\P: a2e6bfd745bc83b4f14aea053eb4fe3a.exe File opened (read-only) \??\Q: a2e6bfd745bc83b4f14aea053eb4fe3a.exe File opened (read-only) \??\S: a2e6bfd745bc83b4f14aea053eb4fe3a.exe File opened (read-only) \??\U: a2e6bfd745bc83b4f14aea053eb4fe3a.exe File opened (read-only) \??\V: a2e6bfd745bc83b4f14aea053eb4fe3a.exe File opened (read-only) \??\H: a2e6bfd745bc83b4f14aea053eb4fe3a.exe File opened (read-only) \??\J: a2e6bfd745bc83b4f14aea053eb4fe3a.exe File opened (read-only) \??\R: a2e6bfd745bc83b4f14aea053eb4fe3a.exe File opened (read-only) \??\T: a2e6bfd745bc83b4f14aea053eb4fe3a.exe File opened (read-only) \??\W: a2e6bfd745bc83b4f14aea053eb4fe3a.exe File opened (read-only) \??\Y: a2e6bfd745bc83b4f14aea053eb4fe3a.exe File opened (read-only) \??\Z: a2e6bfd745bc83b4f14aea053eb4fe3a.exe File opened (read-only) \??\A: a2e6bfd745bc83b4f14aea053eb4fe3a.exe File opened (read-only) \??\E: a2e6bfd745bc83b4f14aea053eb4fe3a.exe File opened (read-only) \??\M: a2e6bfd745bc83b4f14aea053eb4fe3a.exe File opened (read-only) \??\O: a2e6bfd745bc83b4f14aea053eb4fe3a.exe File opened (read-only) \??\F: a2e6bfd745bc83b4f14aea053eb4fe3a.exe File opened (read-only) \??\G: a2e6bfd745bc83b4f14aea053eb4fe3a.exe File opened (read-only) \??\I: a2e6bfd745bc83b4f14aea053eb4fe3a.exe File opened (read-only) \??\K: a2e6bfd745bc83b4f14aea053eb4fe3a.exe File opened (read-only) \??\X: a2e6bfd745bc83b4f14aea053eb4fe3a.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 a2e6bfd745bc83b4f14aea053eb4fe3a.exe Key value queried \REGISTRY\MACHINE\HARDWARE\DESCRIPTION\System\CentralProcessor\0\ProcessorNameString a2e6bfd745bc83b4f14aea053eb4fe3a.exe Key value queried \REGISTRY\MACHINE\HARDWARE\DESCRIPTION\System\CentralProcessor\0\Identifier a2e6bfd745bc83b4f14aea053eb4fe3a.exe -
Suspicious behavior: EnumeratesProcesses 2 IoCs
pid Process 1672 a2e6bfd745bc83b4f14aea053eb4fe3a.exe 1672 a2e6bfd745bc83b4f14aea053eb4fe3a.exe -
Suspicious use of WriteProcessMemory 64 IoCs
description pid Process procid_target PID 1672 wrote to memory of 1932 1672 a2e6bfd745bc83b4f14aea053eb4fe3a.exe 27 PID 1672 wrote to memory of 1932 1672 a2e6bfd745bc83b4f14aea053eb4fe3a.exe 27 PID 1672 wrote to memory of 1932 1672 a2e6bfd745bc83b4f14aea053eb4fe3a.exe 27 PID 1672 wrote to memory of 1932 1672 a2e6bfd745bc83b4f14aea053eb4fe3a.exe 27 PID 1672 wrote to memory of 1784 1672 a2e6bfd745bc83b4f14aea053eb4fe3a.exe 29 PID 1672 wrote to memory of 1784 1672 a2e6bfd745bc83b4f14aea053eb4fe3a.exe 29 PID 1672 wrote to memory of 1784 1672 a2e6bfd745bc83b4f14aea053eb4fe3a.exe 29 PID 1672 wrote to memory of 1784 1672 a2e6bfd745bc83b4f14aea053eb4fe3a.exe 29 PID 1672 wrote to memory of 1232 1672 a2e6bfd745bc83b4f14aea053eb4fe3a.exe 31 PID 1672 wrote to memory of 1232 1672 a2e6bfd745bc83b4f14aea053eb4fe3a.exe 31 PID 1672 wrote to memory of 1232 1672 a2e6bfd745bc83b4f14aea053eb4fe3a.exe 31 PID 1672 wrote to memory of 1232 1672 a2e6bfd745bc83b4f14aea053eb4fe3a.exe 31 PID 1672 wrote to memory of 1344 1672 a2e6bfd745bc83b4f14aea053eb4fe3a.exe 33 PID 1672 wrote to memory of 1344 1672 a2e6bfd745bc83b4f14aea053eb4fe3a.exe 33 PID 1672 wrote to memory of 1344 1672 a2e6bfd745bc83b4f14aea053eb4fe3a.exe 33 PID 1672 wrote to memory of 1344 1672 a2e6bfd745bc83b4f14aea053eb4fe3a.exe 33 PID 1672 wrote to memory of 548 1672 a2e6bfd745bc83b4f14aea053eb4fe3a.exe 35 PID 1672 wrote to memory of 548 1672 a2e6bfd745bc83b4f14aea053eb4fe3a.exe 35 PID 1672 wrote to memory of 548 1672 a2e6bfd745bc83b4f14aea053eb4fe3a.exe 35 PID 1672 wrote to memory of 548 1672 a2e6bfd745bc83b4f14aea053eb4fe3a.exe 35 PID 1672 wrote to memory of 1892 1672 a2e6bfd745bc83b4f14aea053eb4fe3a.exe 37 PID 1672 wrote to memory of 1892 1672 a2e6bfd745bc83b4f14aea053eb4fe3a.exe 37 PID 1672 wrote to memory of 1892 1672 a2e6bfd745bc83b4f14aea053eb4fe3a.exe 37 PID 1672 wrote to memory of 1892 1672 a2e6bfd745bc83b4f14aea053eb4fe3a.exe 37 PID 1672 wrote to memory of 1372 1672 a2e6bfd745bc83b4f14aea053eb4fe3a.exe 39 PID 1672 wrote to memory of 1372 1672 a2e6bfd745bc83b4f14aea053eb4fe3a.exe 39 PID 1672 wrote to memory of 1372 1672 a2e6bfd745bc83b4f14aea053eb4fe3a.exe 39 PID 1672 wrote to memory of 1372 1672 a2e6bfd745bc83b4f14aea053eb4fe3a.exe 39 PID 1672 wrote to memory of 1296 1672 a2e6bfd745bc83b4f14aea053eb4fe3a.exe 41 PID 1672 wrote to memory of 1296 1672 a2e6bfd745bc83b4f14aea053eb4fe3a.exe 41 PID 1672 wrote to memory of 1296 1672 a2e6bfd745bc83b4f14aea053eb4fe3a.exe 41 PID 1672 wrote to memory of 1296 1672 a2e6bfd745bc83b4f14aea053eb4fe3a.exe 41 PID 1672 wrote to memory of 1052 1672 a2e6bfd745bc83b4f14aea053eb4fe3a.exe 43 PID 1672 wrote to memory of 1052 1672 a2e6bfd745bc83b4f14aea053eb4fe3a.exe 43 PID 1672 wrote to memory of 1052 1672 a2e6bfd745bc83b4f14aea053eb4fe3a.exe 43 PID 1672 wrote to memory of 1052 1672 a2e6bfd745bc83b4f14aea053eb4fe3a.exe 43 PID 1672 wrote to memory of 1740 1672 a2e6bfd745bc83b4f14aea053eb4fe3a.exe 45 PID 1672 wrote to memory of 1740 1672 a2e6bfd745bc83b4f14aea053eb4fe3a.exe 45 PID 1672 wrote to memory of 1740 1672 a2e6bfd745bc83b4f14aea053eb4fe3a.exe 45 PID 1672 wrote to memory of 1740 1672 a2e6bfd745bc83b4f14aea053eb4fe3a.exe 45 PID 1672 wrote to memory of 1380 1672 a2e6bfd745bc83b4f14aea053eb4fe3a.exe 47 PID 1672 wrote to memory of 1380 1672 a2e6bfd745bc83b4f14aea053eb4fe3a.exe 47 PID 1672 wrote to memory of 1380 1672 a2e6bfd745bc83b4f14aea053eb4fe3a.exe 47 PID 1672 wrote to memory of 1380 1672 a2e6bfd745bc83b4f14aea053eb4fe3a.exe 47 PID 1672 wrote to memory of 392 1672 a2e6bfd745bc83b4f14aea053eb4fe3a.exe 49 PID 1672 wrote to memory of 392 1672 a2e6bfd745bc83b4f14aea053eb4fe3a.exe 49 PID 1672 wrote to memory of 392 1672 a2e6bfd745bc83b4f14aea053eb4fe3a.exe 49 PID 1672 wrote to memory of 392 1672 a2e6bfd745bc83b4f14aea053eb4fe3a.exe 49 PID 1672 wrote to memory of 1020 1672 a2e6bfd745bc83b4f14aea053eb4fe3a.exe 51 PID 1672 wrote to memory of 1020 1672 a2e6bfd745bc83b4f14aea053eb4fe3a.exe 51 PID 1672 wrote to memory of 1020 1672 a2e6bfd745bc83b4f14aea053eb4fe3a.exe 51 PID 1672 wrote to memory of 1020 1672 a2e6bfd745bc83b4f14aea053eb4fe3a.exe 51 PID 1672 wrote to memory of 1952 1672 a2e6bfd745bc83b4f14aea053eb4fe3a.exe 53 PID 1672 wrote to memory of 1952 1672 a2e6bfd745bc83b4f14aea053eb4fe3a.exe 53 PID 1672 wrote to memory of 1952 1672 a2e6bfd745bc83b4f14aea053eb4fe3a.exe 53 PID 1672 wrote to memory of 1952 1672 a2e6bfd745bc83b4f14aea053eb4fe3a.exe 53 PID 1672 wrote to memory of 1600 1672 a2e6bfd745bc83b4f14aea053eb4fe3a.exe 55 PID 1672 wrote to memory of 1600 1672 a2e6bfd745bc83b4f14aea053eb4fe3a.exe 55 PID 1672 wrote to memory of 1600 1672 a2e6bfd745bc83b4f14aea053eb4fe3a.exe 55 PID 1672 wrote to memory of 1600 1672 a2e6bfd745bc83b4f14aea053eb4fe3a.exe 55 PID 1672 wrote to memory of 1540 1672 a2e6bfd745bc83b4f14aea053eb4fe3a.exe 57 PID 1672 wrote to memory of 1540 1672 a2e6bfd745bc83b4f14aea053eb4fe3a.exe 57 PID 1672 wrote to memory of 1540 1672 a2e6bfd745bc83b4f14aea053eb4fe3a.exe 57 PID 1672 wrote to memory of 1540 1672 a2e6bfd745bc83b4f14aea053eb4fe3a.exe 57
Processes
-
C:\Users\Admin\AppData\Local\Temp\a2e6bfd745bc83b4f14aea053eb4fe3a.exe"C:\Users\Admin\AppData\Local\Temp\a2e6bfd745bc83b4f14aea053eb4fe3a.exe"1⤵
- Adds Run key to start application
- Enumerates connected drives
- Checks processor information in registry
- Suspicious behavior: EnumeratesProcesses
- Suspicious use of WriteProcessMemory
PID:1672 -
C:\Windows\SysWOW64\nslookup.exenslookup carder.bit ns1.wowservers.ru2⤵PID:1932
-
-
C:\Windows\SysWOW64\nslookup.exenslookup ransomware.bit ns2.wowservers.ru2⤵PID:1784
-
-
C:\Windows\SysWOW64\nslookup.exenslookup carder.bit ns2.wowservers.ru2⤵PID:1232
-
-
C:\Windows\SysWOW64\nslookup.exenslookup ransomware.bit ns1.wowservers.ru2⤵PID:1344
-
-
C:\Windows\SysWOW64\nslookup.exenslookup carder.bit ns1.wowservers.ru2⤵PID:548
-
-
C:\Windows\SysWOW64\nslookup.exenslookup ransomware.bit ns2.wowservers.ru2⤵PID:1892
-
-
C:\Windows\SysWOW64\nslookup.exenslookup carder.bit ns2.wowservers.ru2⤵PID:1372
-
-
C:\Windows\SysWOW64\nslookup.exenslookup ransomware.bit ns1.wowservers.ru2⤵PID:1296
-
-
C:\Windows\SysWOW64\nslookup.exenslookup carder.bit ns1.wowservers.ru2⤵PID:1052
-
-
C:\Windows\SysWOW64\nslookup.exenslookup ransomware.bit ns2.wowservers.ru2⤵PID:1740
-
-
C:\Windows\SysWOW64\nslookup.exenslookup carder.bit ns2.wowservers.ru2⤵PID:1380
-
-
C:\Windows\SysWOW64\nslookup.exenslookup ransomware.bit ns1.wowservers.ru2⤵PID:392
-
-
C:\Windows\SysWOW64\nslookup.exenslookup carder.bit ns1.wowservers.ru2⤵PID:1020
-
-
C:\Windows\SysWOW64\nslookup.exenslookup ransomware.bit ns2.wowservers.ru2⤵PID:1952
-
-
C:\Windows\SysWOW64\nslookup.exenslookup carder.bit ns2.wowservers.ru2⤵PID:1600
-
-
C:\Windows\SysWOW64\nslookup.exenslookup ransomware.bit ns1.wowservers.ru2⤵PID:1540
-
-
C:\Windows\SysWOW64\nslookup.exenslookup carder.bit ns1.wowservers.ru2⤵PID:1552
-
-
C:\Windows\SysWOW64\nslookup.exenslookup ransomware.bit ns2.wowservers.ru2⤵PID:1100
-
-
C:\Windows\SysWOW64\nslookup.exenslookup carder.bit ns2.wowservers.ru2⤵PID:1484
-
-
C:\Windows\SysWOW64\nslookup.exenslookup ransomware.bit ns1.wowservers.ru2⤵PID:976
-
-
C:\Windows\SysWOW64\nslookup.exenslookup carder.bit ns1.wowservers.ru2⤵PID:872
-
-
C:\Windows\SysWOW64\nslookup.exenslookup ransomware.bit ns2.wowservers.ru2⤵PID:1476
-
-
C:\Windows\SysWOW64\nslookup.exenslookup carder.bit ns2.wowservers.ru2⤵PID:1160
-
-
C:\Windows\SysWOW64\nslookup.exenslookup ransomware.bit ns1.wowservers.ru2⤵PID:1272
-
-
C:\Windows\SysWOW64\nslookup.exenslookup carder.bit ns1.wowservers.ru2⤵PID:1092
-
-
C:\Windows\SysWOW64\nslookup.exenslookup ransomware.bit ns2.wowservers.ru2⤵PID:384
-
-
C:\Windows\SysWOW64\nslookup.exenslookup carder.bit ns2.wowservers.ru2⤵PID:1384
-
-
C:\Windows\SysWOW64\nslookup.exenslookup ransomware.bit ns1.wowservers.ru2⤵PID:1364
-
-
C:\Windows\SysWOW64\nslookup.exenslookup carder.bit ns1.wowservers.ru2⤵PID:972
-
-
C:\Windows\SysWOW64\nslookup.exenslookup ransomware.bit ns2.wowservers.ru2⤵PID:1456
-
-
C:\Windows\SysWOW64\nslookup.exenslookup carder.bit ns2.wowservers.ru2⤵PID:1516
-
-
C:\Windows\SysWOW64\nslookup.exenslookup ransomware.bit ns1.wowservers.ru2⤵PID:552
-
-
C:\Windows\SysWOW64\nslookup.exenslookup carder.bit ns1.wowservers.ru2⤵PID:684
-
-
C:\Windows\SysWOW64\nslookup.exenslookup ransomware.bit ns2.wowservers.ru2⤵PID:1816
-
-
C:\Windows\SysWOW64\nslookup.exenslookup carder.bit ns2.wowservers.ru2⤵PID:1568
-
-
C:\Windows\SysWOW64\nslookup.exenslookup ransomware.bit ns1.wowservers.ru2⤵PID:1872
-
-
C:\Windows\SysWOW64\nslookup.exenslookup carder.bit ns1.wowservers.ru2⤵PID:1964
-
-
C:\Windows\SysWOW64\nslookup.exenslookup ransomware.bit ns2.wowservers.ru2⤵PID:1404
-
-
C:\Windows\SysWOW64\nslookup.exenslookup carder.bit ns2.wowservers.ru2⤵PID:1460
-
-
C:\Windows\SysWOW64\nslookup.exenslookup ransomware.bit ns1.wowservers.ru2⤵PID:936
-
-
C:\Windows\SysWOW64\nslookup.exenslookup carder.bit ns1.wowservers.ru2⤵PID:1992
-
-
C:\Windows\SysWOW64\nslookup.exenslookup ransomware.bit ns2.wowservers.ru2⤵PID:924
-
-
C:\Windows\SysWOW64\nslookup.exenslookup carder.bit ns2.wowservers.ru2⤵PID:1944
-
-
C:\Windows\SysWOW64\nslookup.exenslookup ransomware.bit ns1.wowservers.ru2⤵PID:960
-
-
C:\Windows\SysWOW64\nslookup.exenslookup carder.bit ns1.wowservers.ru2⤵PID:1596
-
-
C:\Windows\SysWOW64\nslookup.exenslookup ransomware.bit ns2.wowservers.ru2⤵PID:1108
-
-
C:\Windows\SysWOW64\nslookup.exenslookup carder.bit ns2.wowservers.ru2⤵PID:1776
-
-
C:\Windows\SysWOW64\nslookup.exenslookup ransomware.bit ns1.wowservers.ru2⤵PID:1480
-
-
C:\Windows\SysWOW64\nslookup.exenslookup carder.bit ns1.wowservers.ru2⤵PID:604
-
-
C:\Windows\SysWOW64\nslookup.exenslookup ransomware.bit ns2.wowservers.ru2⤵PID:788
-
-
C:\Windows\SysWOW64\nslookup.exenslookup carder.bit ns2.wowservers.ru2⤵PID:852
-
-
C:\Windows\SysWOW64\nslookup.exenslookup ransomware.bit ns1.wowservers.ru2⤵PID:1264
-
-
C:\Windows\SysWOW64\nslookup.exenslookup carder.bit ns1.wowservers.ru2⤵PID:980
-
-
C:\Windows\SysWOW64\nslookup.exenslookup ransomware.bit ns2.wowservers.ru2⤵PID:556
-
-
C:\Windows\SysWOW64\nslookup.exenslookup carder.bit ns2.wowservers.ru2⤵PID:1496
-
-
C:\Windows\SysWOW64\nslookup.exenslookup ransomware.bit ns1.wowservers.ru2⤵PID:1880
-
-
C:\Windows\SysWOW64\nslookup.exenslookup carder.bit ns1.wowservers.ru2⤵PID:572
-
-
C:\Windows\SysWOW64\nslookup.exenslookup ransomware.bit ns2.wowservers.ru2⤵PID:1804
-
-
C:\Windows\SysWOW64\nslookup.exenslookup carder.bit ns2.wowservers.ru2⤵PID:1200
-
-
C:\Windows\SysWOW64\nslookup.exenslookup ransomware.bit ns1.wowservers.ru2⤵PID:516
-
-
C:\Windows\SysWOW64\nslookup.exenslookup carder.bit ns1.wowservers.ru2⤵PID:1548
-
-
C:\Windows\SysWOW64\nslookup.exenslookup ransomware.bit ns2.wowservers.ru2⤵PID:108
-
-
C:\Windows\SysWOW64\nslookup.exenslookup carder.bit ns2.wowservers.ru2⤵PID:1064
-
-
C:\Windows\SysWOW64\nslookup.exenslookup ransomware.bit ns1.wowservers.ru2⤵PID:1864
-
-
C:\Windows\SysWOW64\nslookup.exenslookup carder.bit ns1.wowservers.ru2⤵PID:1976
-
-
C:\Windows\SysWOW64\nslookup.exenslookup ransomware.bit ns2.wowservers.ru2⤵PID:1172
-
-
C:\Windows\SysWOW64\nslookup.exenslookup carder.bit ns2.wowservers.ru2⤵PID:1684
-
-
C:\Windows\SysWOW64\nslookup.exenslookup ransomware.bit ns1.wowservers.ru2⤵PID:2032
-
-
C:\Windows\SysWOW64\nslookup.exenslookup carder.bit ns1.wowservers.ru2⤵PID:1788
-
-
C:\Windows\SysWOW64\nslookup.exenslookup ransomware.bit ns2.wowservers.ru2⤵PID:1348
-