Analysis
-
max time kernel
150s -
max time network
149s -
platform
windows10_x64 -
resource
win10v20210410 -
submitted
07-05-2021 04:53
Static task
static1
Behavioral task
behavioral1
Sample
tracking_number.pdf(2).exe
Resource
win7v20210408
Behavioral task
behavioral2
Sample
tracking_number.pdf(2).exe
Resource
win10v20210410
General
-
Target
tracking_number.pdf(2).exe
-
Size
214KB
-
MD5
b4fc1596157eb7b7900dd1da72c301c4
-
SHA1
e0c4095c71475036bd79f8bb926fcb575d446d36
-
SHA256
0452a7ada10bdeda0eb905da0549955f9ce8486ff7cf76a51d73f90a90e89aad
-
SHA512
6a7f72c23344c128dc1d7c25942affedd7c36960da229caebee274c395013d07db9bcb77a24f8cf00e765cbbd1d346cb925dc67a63ac9da2c3621c49c1c1cf48
Malware Config
Signatures
-
GandCrab Payload 1 IoCs
resource yara_rule behavioral2/memory/512-116-0x00000000004B0000-0x00000000004C7000-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 tracking_number.pdf(2).exe Set value (str) \REGISTRY\MACHINE\SOFTWARE\WOW6432Node\Microsoft\Windows\CurrentVersion\RunOnce\ggtxztonolk = "\"C:\\Users\\Admin\\AppData\\Roaming\\Microsoft\\ukeukr.exe\"" tracking_number.pdf(2).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) \??\Q: tracking_number.pdf(2).exe File opened (read-only) \??\T: tracking_number.pdf(2).exe File opened (read-only) \??\V: tracking_number.pdf(2).exe File opened (read-only) \??\Y: tracking_number.pdf(2).exe File opened (read-only) \??\Z: tracking_number.pdf(2).exe File opened (read-only) \??\H: tracking_number.pdf(2).exe File opened (read-only) \??\N: tracking_number.pdf(2).exe File opened (read-only) \??\F: tracking_number.pdf(2).exe File opened (read-only) \??\L: tracking_number.pdf(2).exe File opened (read-only) \??\M: tracking_number.pdf(2).exe File opened (read-only) \??\R: tracking_number.pdf(2).exe File opened (read-only) \??\W: tracking_number.pdf(2).exe File opened (read-only) \??\A: tracking_number.pdf(2).exe File opened (read-only) \??\E: tracking_number.pdf(2).exe File opened (read-only) \??\J: tracking_number.pdf(2).exe File opened (read-only) \??\P: tracking_number.pdf(2).exe File opened (read-only) \??\S: tracking_number.pdf(2).exe File opened (read-only) \??\X: tracking_number.pdf(2).exe File opened (read-only) \??\B: tracking_number.pdf(2).exe File opened (read-only) \??\I: tracking_number.pdf(2).exe File opened (read-only) \??\O: tracking_number.pdf(2).exe File opened (read-only) \??\U: tracking_number.pdf(2).exe File opened (read-only) \??\G: tracking_number.pdf(2).exe File opened (read-only) \??\K: tracking_number.pdf(2).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 value queried \REGISTRY\MACHINE\HARDWARE\DESCRIPTION\System\CentralProcessor\0\ProcessorNameString tracking_number.pdf(2).exe Key value queried \REGISTRY\MACHINE\HARDWARE\DESCRIPTION\System\CentralProcessor\0\Identifier tracking_number.pdf(2).exe Key opened \REGISTRY\MACHINE\HARDWARE\DESCRIPTION\System\CentralProcessor\0 tracking_number.pdf(2).exe -
Suspicious behavior: EnumeratesProcesses 4 IoCs
pid Process 512 tracking_number.pdf(2).exe 512 tracking_number.pdf(2).exe 512 tracking_number.pdf(2).exe 512 tracking_number.pdf(2).exe -
Suspicious use of WriteProcessMemory 64 IoCs
description pid Process procid_target PID 512 wrote to memory of 3856 512 tracking_number.pdf(2).exe 76 PID 512 wrote to memory of 3856 512 tracking_number.pdf(2).exe 76 PID 512 wrote to memory of 3856 512 tracking_number.pdf(2).exe 76 PID 512 wrote to memory of 2408 512 tracking_number.pdf(2).exe 80 PID 512 wrote to memory of 2408 512 tracking_number.pdf(2).exe 80 PID 512 wrote to memory of 2408 512 tracking_number.pdf(2).exe 80 PID 512 wrote to memory of 1008 512 tracking_number.pdf(2).exe 82 PID 512 wrote to memory of 1008 512 tracking_number.pdf(2).exe 82 PID 512 wrote to memory of 1008 512 tracking_number.pdf(2).exe 82 PID 512 wrote to memory of 3808 512 tracking_number.pdf(2).exe 84 PID 512 wrote to memory of 3808 512 tracking_number.pdf(2).exe 84 PID 512 wrote to memory of 3808 512 tracking_number.pdf(2).exe 84 PID 512 wrote to memory of 2188 512 tracking_number.pdf(2).exe 86 PID 512 wrote to memory of 2188 512 tracking_number.pdf(2).exe 86 PID 512 wrote to memory of 2188 512 tracking_number.pdf(2).exe 86 PID 512 wrote to memory of 3520 512 tracking_number.pdf(2).exe 89 PID 512 wrote to memory of 3520 512 tracking_number.pdf(2).exe 89 PID 512 wrote to memory of 3520 512 tracking_number.pdf(2).exe 89 PID 512 wrote to memory of 1324 512 tracking_number.pdf(2).exe 91 PID 512 wrote to memory of 1324 512 tracking_number.pdf(2).exe 91 PID 512 wrote to memory of 1324 512 tracking_number.pdf(2).exe 91 PID 512 wrote to memory of 1584 512 tracking_number.pdf(2).exe 93 PID 512 wrote to memory of 1584 512 tracking_number.pdf(2).exe 93 PID 512 wrote to memory of 1584 512 tracking_number.pdf(2).exe 93 PID 512 wrote to memory of 1772 512 tracking_number.pdf(2).exe 95 PID 512 wrote to memory of 1772 512 tracking_number.pdf(2).exe 95 PID 512 wrote to memory of 1772 512 tracking_number.pdf(2).exe 95 PID 512 wrote to memory of 3336 512 tracking_number.pdf(2).exe 97 PID 512 wrote to memory of 3336 512 tracking_number.pdf(2).exe 97 PID 512 wrote to memory of 3336 512 tracking_number.pdf(2).exe 97 PID 512 wrote to memory of 3508 512 tracking_number.pdf(2).exe 99 PID 512 wrote to memory of 3508 512 tracking_number.pdf(2).exe 99 PID 512 wrote to memory of 3508 512 tracking_number.pdf(2).exe 99 PID 512 wrote to memory of 856 512 tracking_number.pdf(2).exe 101 PID 512 wrote to memory of 856 512 tracking_number.pdf(2).exe 101 PID 512 wrote to memory of 856 512 tracking_number.pdf(2).exe 101 PID 512 wrote to memory of 8 512 tracking_number.pdf(2).exe 103 PID 512 wrote to memory of 8 512 tracking_number.pdf(2).exe 103 PID 512 wrote to memory of 8 512 tracking_number.pdf(2).exe 103 PID 512 wrote to memory of 1664 512 tracking_number.pdf(2).exe 105 PID 512 wrote to memory of 1664 512 tracking_number.pdf(2).exe 105 PID 512 wrote to memory of 1664 512 tracking_number.pdf(2).exe 105 PID 512 wrote to memory of 1724 512 tracking_number.pdf(2).exe 107 PID 512 wrote to memory of 1724 512 tracking_number.pdf(2).exe 107 PID 512 wrote to memory of 1724 512 tracking_number.pdf(2).exe 107 PID 512 wrote to memory of 3748 512 tracking_number.pdf(2).exe 109 PID 512 wrote to memory of 3748 512 tracking_number.pdf(2).exe 109 PID 512 wrote to memory of 3748 512 tracking_number.pdf(2).exe 109 PID 512 wrote to memory of 2464 512 tracking_number.pdf(2).exe 111 PID 512 wrote to memory of 2464 512 tracking_number.pdf(2).exe 111 PID 512 wrote to memory of 2464 512 tracking_number.pdf(2).exe 111 PID 512 wrote to memory of 3828 512 tracking_number.pdf(2).exe 113 PID 512 wrote to memory of 3828 512 tracking_number.pdf(2).exe 113 PID 512 wrote to memory of 3828 512 tracking_number.pdf(2).exe 113 PID 512 wrote to memory of 64 512 tracking_number.pdf(2).exe 115 PID 512 wrote to memory of 64 512 tracking_number.pdf(2).exe 115 PID 512 wrote to memory of 64 512 tracking_number.pdf(2).exe 115 PID 512 wrote to memory of 1320 512 tracking_number.pdf(2).exe 117 PID 512 wrote to memory of 1320 512 tracking_number.pdf(2).exe 117 PID 512 wrote to memory of 1320 512 tracking_number.pdf(2).exe 117 PID 512 wrote to memory of 1248 512 tracking_number.pdf(2).exe 119 PID 512 wrote to memory of 1248 512 tracking_number.pdf(2).exe 119 PID 512 wrote to memory of 1248 512 tracking_number.pdf(2).exe 119 PID 512 wrote to memory of 3572 512 tracking_number.pdf(2).exe 121
Processes
-
C:\Users\Admin\AppData\Local\Temp\tracking_number.pdf(2).exe"C:\Users\Admin\AppData\Local\Temp\tracking_number.pdf(2).exe"1⤵
- Adds Run key to start application
- Enumerates connected drives
- Checks processor information in registry
- Suspicious behavior: EnumeratesProcesses
- Suspicious use of WriteProcessMemory
PID:512 -
C:\Windows\SysWOW64\nslookup.exenslookup carder.bit ns1.wowservers.ru2⤵PID:3856
-
-
C:\Windows\SysWOW64\nslookup.exenslookup ransomware.bit ns2.wowservers.ru2⤵PID:2408
-
-
C:\Windows\SysWOW64\nslookup.exenslookup carder.bit ns2.wowservers.ru2⤵PID:1008
-
-
C:\Windows\SysWOW64\nslookup.exenslookup ransomware.bit ns1.wowservers.ru2⤵PID:3808
-
-
C:\Windows\SysWOW64\nslookup.exenslookup carder.bit ns1.wowservers.ru2⤵PID:2188
-
-
C:\Windows\SysWOW64\nslookup.exenslookup ransomware.bit ns2.wowservers.ru2⤵PID:3520
-
-
C:\Windows\SysWOW64\nslookup.exenslookup carder.bit ns2.wowservers.ru2⤵PID:1324
-
-
C:\Windows\SysWOW64\nslookup.exenslookup ransomware.bit ns1.wowservers.ru2⤵PID:1584
-
-
C:\Windows\SysWOW64\nslookup.exenslookup carder.bit ns1.wowservers.ru2⤵PID:1772
-
-
C:\Windows\SysWOW64\nslookup.exenslookup ransomware.bit ns2.wowservers.ru2⤵PID:3336
-
-
C:\Windows\SysWOW64\nslookup.exenslookup carder.bit ns2.wowservers.ru2⤵PID:3508
-
-
C:\Windows\SysWOW64\nslookup.exenslookup ransomware.bit ns1.wowservers.ru2⤵PID:856
-
-
C:\Windows\SysWOW64\nslookup.exenslookup carder.bit ns1.wowservers.ru2⤵PID:8
-
-
C:\Windows\SysWOW64\nslookup.exenslookup ransomware.bit ns2.wowservers.ru2⤵PID:1664
-
-
C:\Windows\SysWOW64\nslookup.exenslookup carder.bit ns2.wowservers.ru2⤵PID:1724
-
-
C:\Windows\SysWOW64\nslookup.exenslookup ransomware.bit ns1.wowservers.ru2⤵PID:3748
-
-
C:\Windows\SysWOW64\nslookup.exenslookup carder.bit ns1.wowservers.ru2⤵PID:2464
-
-
C:\Windows\SysWOW64\nslookup.exenslookup ransomware.bit ns2.wowservers.ru2⤵PID:3828
-
-
C:\Windows\SysWOW64\nslookup.exenslookup carder.bit ns2.wowservers.ru2⤵PID:64
-
-
C:\Windows\SysWOW64\nslookup.exenslookup ransomware.bit ns1.wowservers.ru2⤵PID:1320
-
-
C:\Windows\SysWOW64\nslookup.exenslookup carder.bit ns1.wowservers.ru2⤵PID:1248
-
-
C:\Windows\SysWOW64\nslookup.exenslookup ransomware.bit ns2.wowservers.ru2⤵PID:3572
-
-
C:\Windows\SysWOW64\nslookup.exenslookup carder.bit ns2.wowservers.ru2⤵PID:1928
-
-
C:\Windows\SysWOW64\nslookup.exenslookup ransomware.bit ns1.wowservers.ru2⤵PID:2080
-
-
C:\Windows\SysWOW64\nslookup.exenslookup carder.bit ns1.wowservers.ru2⤵PID:3824
-
-
C:\Windows\SysWOW64\nslookup.exenslookup ransomware.bit ns2.wowservers.ru2⤵PID:1200
-
-
C:\Windows\SysWOW64\nslookup.exenslookup carder.bit ns2.wowservers.ru2⤵PID:3240
-
-
C:\Windows\SysWOW64\nslookup.exenslookup ransomware.bit ns1.wowservers.ru2⤵PID:784
-
-
C:\Windows\SysWOW64\nslookup.exenslookup carder.bit ns1.wowservers.ru2⤵PID:1776
-
-
C:\Windows\SysWOW64\nslookup.exenslookup ransomware.bit ns2.wowservers.ru2⤵PID:4016
-
-
C:\Windows\SysWOW64\nslookup.exenslookup carder.bit ns2.wowservers.ru2⤵PID:3728
-
-
C:\Windows\SysWOW64\nslookup.exenslookup ransomware.bit ns1.wowservers.ru2⤵PID:3836
-
-
C:\Windows\SysWOW64\nslookup.exenslookup carder.bit ns1.wowservers.ru2⤵PID:3380
-
-
C:\Windows\SysWOW64\nslookup.exenslookup ransomware.bit ns2.wowservers.ru2⤵PID:2212
-
-
C:\Windows\SysWOW64\nslookup.exenslookup carder.bit ns2.wowservers.ru2⤵PID:3196
-
-
C:\Windows\SysWOW64\nslookup.exenslookup ransomware.bit ns1.wowservers.ru2⤵PID:3076
-
-
C:\Windows\SysWOW64\nslookup.exenslookup carder.bit ns1.wowservers.ru2⤵PID:3328
-
-
C:\Windows\SysWOW64\nslookup.exenslookup ransomware.bit ns2.wowservers.ru2⤵PID:2124
-
-
C:\Windows\SysWOW64\nslookup.exenslookup carder.bit ns2.wowservers.ru2⤵PID:1556
-
-
C:\Windows\SysWOW64\nslookup.exenslookup ransomware.bit ns1.wowservers.ru2⤵PID:3400
-
-
C:\Windows\SysWOW64\nslookup.exenslookup carder.bit ns1.wowservers.ru2⤵PID:1668
-
-
C:\Windows\SysWOW64\nslookup.exenslookup ransomware.bit ns2.wowservers.ru2⤵PID:1788
-
-
C:\Windows\SysWOW64\nslookup.exenslookup carder.bit ns2.wowservers.ru2⤵PID:2172
-
-
C:\Windows\SysWOW64\nslookup.exenslookup ransomware.bit ns1.wowservers.ru2⤵PID:2444
-
-
C:\Windows\SysWOW64\nslookup.exenslookup carder.bit ns1.wowservers.ru2⤵PID:3832
-
-
C:\Windows\SysWOW64\nslookup.exenslookup ransomware.bit ns2.wowservers.ru2⤵PID:2132
-
-
C:\Windows\SysWOW64\nslookup.exenslookup carder.bit ns2.wowservers.ru2⤵PID:3492
-
-
C:\Windows\SysWOW64\nslookup.exenslookup ransomware.bit ns1.wowservers.ru2⤵PID:4088
-
-
C:\Windows\SysWOW64\nslookup.exenslookup carder.bit ns1.wowservers.ru2⤵PID:2200
-
-
C:\Windows\SysWOW64\nslookup.exenslookup ransomware.bit ns2.wowservers.ru2⤵PID:3100
-
-
C:\Windows\SysWOW64\nslookup.exenslookup carder.bit ns2.wowservers.ru2⤵PID:2128
-
-
C:\Windows\SysWOW64\nslookup.exenslookup ransomware.bit ns1.wowservers.ru2⤵PID:496
-
-
C:\Windows\SysWOW64\nslookup.exenslookup carder.bit ns1.wowservers.ru2⤵PID:3464
-
-
C:\Windows\SysWOW64\nslookup.exenslookup ransomware.bit ns2.wowservers.ru2⤵PID:3712
-
-
C:\Windows\SysWOW64\nslookup.exenslookup carder.bit ns2.wowservers.ru2⤵PID:2208
-
-
C:\Windows\SysWOW64\nslookup.exenslookup ransomware.bit ns1.wowservers.ru2⤵PID:2168
-
-
C:\Windows\SysWOW64\nslookup.exenslookup carder.bit ns1.wowservers.ru2⤵PID:1520
-
-
C:\Windows\SysWOW64\nslookup.exenslookup ransomware.bit ns2.wowservers.ru2⤵PID:1836
-
-
C:\Windows\SysWOW64\nslookup.exenslookup carder.bit ns2.wowservers.ru2⤵PID:3700
-
-
C:\Windows\SysWOW64\nslookup.exenslookup ransomware.bit ns1.wowservers.ru2⤵PID:196
-
-
C:\Windows\SysWOW64\nslookup.exenslookup carder.bit ns1.wowservers.ru2⤵PID:3288
-
-
C:\Windows\SysWOW64\nslookup.exenslookup ransomware.bit ns2.wowservers.ru2⤵PID:2412
-
-
C:\Windows\SysWOW64\nslookup.exenslookup carder.bit ns2.wowservers.ru2⤵PID:2896
-
-
C:\Windows\SysWOW64\nslookup.exenslookup ransomware.bit ns1.wowservers.ru2⤵PID:2220
-
-
C:\Windows\SysWOW64\nslookup.exenslookup carder.bit ns1.wowservers.ru2⤵PID:1596
-
-
C:\Windows\SysWOW64\nslookup.exenslookup ransomware.bit ns2.wowservers.ru2⤵PID:1972
-
-
C:\Windows\SysWOW64\nslookup.exenslookup carder.bit ns2.wowservers.ru2⤵PID:3424
-
-
C:\Windows\SysWOW64\nslookup.exenslookup ransomware.bit ns1.wowservers.ru2⤵PID:3368
-
-
C:\Windows\SysWOW64\nslookup.exenslookup carder.bit ns1.wowservers.ru2⤵PID:2352
-
-
C:\Windows\SysWOW64\nslookup.exenslookup ransomware.bit ns2.wowservers.ru2⤵PID:2804
-
-
C:\Windows\SysWOW64\nslookup.exenslookup carder.bit ns2.wowservers.ru2⤵PID:2844
-
-
C:\Windows\SysWOW64\nslookup.exenslookup ransomware.bit ns1.wowservers.ru2⤵PID:1560
-
-
C:\Windows\SysWOW64\nslookup.exenslookup carder.bit ns1.wowservers.ru2⤵PID:2460
-
-
C:\Windows\SysWOW64\nslookup.exenslookup ransomware.bit ns2.wowservers.ru2⤵PID:1804
-
-
C:\Windows\SysWOW64\nslookup.exenslookup carder.bit ns2.wowservers.ru2⤵PID:1576
-
-
C:\Windows\SysWOW64\nslookup.exenslookup ransomware.bit ns1.wowservers.ru2⤵PID:3640
-
-
C:\Windows\SysWOW64\nslookup.exenslookup carder.bit ns1.wowservers.ru2⤵PID:420
-
-
C:\Windows\SysWOW64\nslookup.exenslookup ransomware.bit ns2.wowservers.ru2⤵PID:2892
-
-
C:\Windows\SysWOW64\nslookup.exenslookup carder.bit ns2.wowservers.ru2⤵PID:1476
-
-
C:\Windows\SysWOW64\nslookup.exenslookup ransomware.bit ns1.wowservers.ru2⤵PID:1792
-
-
C:\Windows\SysWOW64\nslookup.exenslookup carder.bit ns1.wowservers.ru2⤵PID:1012
-
-
C:\Windows\SysWOW64\nslookup.exenslookup ransomware.bit ns2.wowservers.ru2⤵PID:3600
-
-
C:\Windows\SysWOW64\nslookup.exenslookup carder.bit ns2.wowservers.ru2⤵PID:2636
-
-
C:\Windows\SysWOW64\nslookup.exenslookup ransomware.bit ns1.wowservers.ru2⤵PID:3244
-
-
C:\Windows\SysWOW64\nslookup.exenslookup carder.bit ns1.wowservers.ru2⤵PID:2064
-
-
C:\Windows\SysWOW64\nslookup.exenslookup ransomware.bit ns2.wowservers.ru2⤵PID:2788
-
-
C:\Windows\SysWOW64\nslookup.exenslookup carder.bit ns2.wowservers.ru2⤵PID:2196
-
-
C:\Windows\SysWOW64\nslookup.exenslookup ransomware.bit ns1.wowservers.ru2⤵PID:2528
-
-
C:\Windows\SysWOW64\nslookup.exenslookup carder.bit ns1.wowservers.ru2⤵PID:2000
-
-
C:\Windows\SysWOW64\nslookup.exenslookup ransomware.bit ns2.wowservers.ru2⤵PID:3852
-
-
C:\Windows\SysWOW64\nslookup.exenslookup carder.bit ns2.wowservers.ru2⤵PID:3564
-
-
C:\Windows\SysWOW64\nslookup.exenslookup ransomware.bit ns1.wowservers.ru2⤵PID:3284
-
-
C:\Windows\SysWOW64\nslookup.exenslookup carder.bit ns1.wowservers.ru2⤵PID:340
-
-
C:\Windows\SysWOW64\nslookup.exenslookup ransomware.bit ns2.wowservers.ru2⤵PID:2156
-
-
C:\Windows\SysWOW64\nslookup.exenslookup carder.bit ns2.wowservers.ru2⤵PID:3984
-
-
C:\Windows\SysWOW64\nslookup.exenslookup ransomware.bit ns1.wowservers.ru2⤵PID:3504
-
-
C:\Windows\SysWOW64\nslookup.exenslookup carder.bit ns1.wowservers.ru2⤵PID:3160
-
-
C:\Windows\SysWOW64\nslookup.exenslookup ransomware.bit ns2.wowservers.ru2⤵PID:1364
-
-
C:\Windows\SysWOW64\nslookup.exenslookup carder.bit ns2.wowservers.ru2⤵PID:2252
-
-
C:\Windows\SysWOW64\nslookup.exenslookup ransomware.bit ns1.wowservers.ru2⤵PID:3488
-
-
C:\Windows\SysWOW64\nslookup.exenslookup carder.bit ns1.wowservers.ru2⤵PID:2964
-
-
C:\Windows\SysWOW64\nslookup.exenslookup ransomware.bit ns2.wowservers.ru2⤵PID:3880
-
-
C:\Windows\SysWOW64\nslookup.exenslookup carder.bit ns2.wowservers.ru2⤵PID:2036
-
-
C:\Windows\SysWOW64\nslookup.exenslookup ransomware.bit ns1.wowservers.ru2⤵PID:3816
-
-
C:\Windows\SysWOW64\nslookup.exenslookup carder.bit ns1.wowservers.ru2⤵PID:2216
-
-
C:\Windows\SysWOW64\nslookup.exenslookup ransomware.bit ns2.wowservers.ru2⤵PID:3988
-
-
C:\Windows\SysWOW64\nslookup.exenslookup carder.bit ns2.wowservers.ru2⤵PID:3200
-
-
C:\Windows\SysWOW64\nslookup.exenslookup ransomware.bit ns1.wowservers.ru2⤵PID:1572
-
-
C:\Windows\SysWOW64\nslookup.exenslookup carder.bit ns1.wowservers.ru2⤵PID:640
-
-
C:\Windows\SysWOW64\nslookup.exenslookup ransomware.bit ns2.wowservers.ru2⤵PID:2040
-
-
C:\Windows\SysWOW64\nslookup.exenslookup carder.bit ns2.wowservers.ru2⤵PID:2244
-
-
C:\Windows\SysWOW64\nslookup.exenslookup ransomware.bit ns1.wowservers.ru2⤵PID:3784
-
-
C:\Windows\SysWOW64\nslookup.exenslookup carder.bit ns1.wowservers.ru2⤵PID:188
-
-
C:\Windows\SysWOW64\nslookup.exenslookup ransomware.bit ns2.wowservers.ru2⤵PID:3168
-
-
C:\Windows\SysWOW64\nslookup.exenslookup carder.bit ns2.wowservers.ru2⤵PID:3940
-
-
C:\Windows\SysWOW64\nslookup.exenslookup ransomware.bit ns1.wowservers.ru2⤵PID:3704
-
-
C:\Windows\SysWOW64\nslookup.exenslookup carder.bit ns1.wowservers.ru2⤵PID:3960
-
-
C:\Windows\SysWOW64\nslookup.exenslookup ransomware.bit ns2.wowservers.ru2⤵PID:1980
-
-
C:\Windows\SysWOW64\nslookup.exenslookup carder.bit ns2.wowservers.ru2⤵PID:936
-
-
C:\Windows\SysWOW64\nslookup.exenslookup ransomware.bit ns1.wowservers.ru2⤵PID:2704
-
-
C:\Windows\SysWOW64\nslookup.exenslookup carder.bit ns1.wowservers.ru2⤵PID:2164
-
-
C:\Windows\SysWOW64\nslookup.exenslookup ransomware.bit ns2.wowservers.ru2⤵PID:3720
-
-
C:\Windows\SysWOW64\nslookup.exenslookup carder.bit ns2.wowservers.ru2⤵PID:4056
-
-
C:\Windows\SysWOW64\nslookup.exenslookup ransomware.bit ns1.wowservers.ru2⤵PID:1340
-
-
C:\Windows\SysWOW64\nslookup.exenslookup carder.bit ns1.wowservers.ru2⤵PID:1204
-
-
C:\Windows\SysWOW64\nslookup.exenslookup ransomware.bit ns2.wowservers.ru2⤵PID:4000
-
-
C:\Windows\SysWOW64\nslookup.exenslookup carder.bit ns2.wowservers.ru2⤵PID:3812
-
-
C:\Windows\SysWOW64\nslookup.exenslookup ransomware.bit ns1.wowservers.ru2⤵PID:3936
-
-
C:\Windows\SysWOW64\nslookup.exenslookup carder.bit ns1.wowservers.ru2⤵PID:680
-
-
C:\Windows\SysWOW64\nslookup.exenslookup ransomware.bit ns2.wowservers.ru2⤵PID:2648
-