Analysis
-
max time kernel
150s -
max time network
153s -
platform
windows10_x64 -
resource
win10v20210410 -
submitted
18-05-2021 11:39
Static task
static1
Behavioral task
behavioral1
Sample
2d427458f0c4e9ba28d6d9f785c365213c0ac9e3527e3efa7dedd90e009fef5e.exe
Resource
win7v20210408
Behavioral task
behavioral2
Sample
2d427458f0c4e9ba28d6d9f785c365213c0ac9e3527e3efa7dedd90e009fef5e.exe
Resource
win10v20210410
General
-
Target
2d427458f0c4e9ba28d6d9f785c365213c0ac9e3527e3efa7dedd90e009fef5e.exe
-
Size
320KB
-
MD5
103a75dfc9efa5283555bc538f38898a
-
SHA1
ebe5cc5a41e9c40b5041d9d2581995f3b6aa81bd
-
SHA256
2d427458f0c4e9ba28d6d9f785c365213c0ac9e3527e3efa7dedd90e009fef5e
-
SHA512
814a3f64e43c4035443ac4baddfaa610cd471f82d3617df5b54c2f7b38eda831e099e372f784606165fe45694056f3032d9452e0b845c7cf5ac94e4300dc3224
Malware Config
Signatures
-
Adds Run key to start application 2 TTPs 2 IoCs
Processes:
2d427458f0c4e9ba28d6d9f785c365213c0ac9e3527e3efa7dedd90e009fef5e.exedescription ioc process Key created \REGISTRY\MACHINE\SOFTWARE\WOW6432Node\Microsoft\Windows\CurrentVersion\RunOnce 2d427458f0c4e9ba28d6d9f785c365213c0ac9e3527e3efa7dedd90e009fef5e.exe Set value (str) \REGISTRY\MACHINE\SOFTWARE\WOW6432Node\Microsoft\Windows\CurrentVersion\RunOnce\uwancofhefi = "\"C:\\Users\\Admin\\AppData\\Roaming\\Microsoft\\gfupde.exe\"" 2d427458f0c4e9ba28d6d9f785c365213c0ac9e3527e3efa7dedd90e009fef5e.exe -
Enumerates connected drives 3 TTPs 24 IoCs
Attempts to read the root path of hard drives other than the default C: drive.
Processes:
2d427458f0c4e9ba28d6d9f785c365213c0ac9e3527e3efa7dedd90e009fef5e.exedescription ioc process File opened (read-only) \??\A: 2d427458f0c4e9ba28d6d9f785c365213c0ac9e3527e3efa7dedd90e009fef5e.exe File opened (read-only) \??\F: 2d427458f0c4e9ba28d6d9f785c365213c0ac9e3527e3efa7dedd90e009fef5e.exe File opened (read-only) \??\G: 2d427458f0c4e9ba28d6d9f785c365213c0ac9e3527e3efa7dedd90e009fef5e.exe File opened (read-only) \??\I: 2d427458f0c4e9ba28d6d9f785c365213c0ac9e3527e3efa7dedd90e009fef5e.exe File opened (read-only) \??\O: 2d427458f0c4e9ba28d6d9f785c365213c0ac9e3527e3efa7dedd90e009fef5e.exe File opened (read-only) \??\Q: 2d427458f0c4e9ba28d6d9f785c365213c0ac9e3527e3efa7dedd90e009fef5e.exe File opened (read-only) \??\V: 2d427458f0c4e9ba28d6d9f785c365213c0ac9e3527e3efa7dedd90e009fef5e.exe File opened (read-only) \??\Y: 2d427458f0c4e9ba28d6d9f785c365213c0ac9e3527e3efa7dedd90e009fef5e.exe File opened (read-only) \??\H: 2d427458f0c4e9ba28d6d9f785c365213c0ac9e3527e3efa7dedd90e009fef5e.exe File opened (read-only) \??\J: 2d427458f0c4e9ba28d6d9f785c365213c0ac9e3527e3efa7dedd90e009fef5e.exe File opened (read-only) \??\M: 2d427458f0c4e9ba28d6d9f785c365213c0ac9e3527e3efa7dedd90e009fef5e.exe File opened (read-only) \??\N: 2d427458f0c4e9ba28d6d9f785c365213c0ac9e3527e3efa7dedd90e009fef5e.exe File opened (read-only) \??\P: 2d427458f0c4e9ba28d6d9f785c365213c0ac9e3527e3efa7dedd90e009fef5e.exe File opened (read-only) \??\S: 2d427458f0c4e9ba28d6d9f785c365213c0ac9e3527e3efa7dedd90e009fef5e.exe File opened (read-only) \??\T: 2d427458f0c4e9ba28d6d9f785c365213c0ac9e3527e3efa7dedd90e009fef5e.exe File opened (read-only) \??\W: 2d427458f0c4e9ba28d6d9f785c365213c0ac9e3527e3efa7dedd90e009fef5e.exe File opened (read-only) \??\Z: 2d427458f0c4e9ba28d6d9f785c365213c0ac9e3527e3efa7dedd90e009fef5e.exe File opened (read-only) \??\L: 2d427458f0c4e9ba28d6d9f785c365213c0ac9e3527e3efa7dedd90e009fef5e.exe File opened (read-only) \??\R: 2d427458f0c4e9ba28d6d9f785c365213c0ac9e3527e3efa7dedd90e009fef5e.exe File opened (read-only) \??\U: 2d427458f0c4e9ba28d6d9f785c365213c0ac9e3527e3efa7dedd90e009fef5e.exe File opened (read-only) \??\B: 2d427458f0c4e9ba28d6d9f785c365213c0ac9e3527e3efa7dedd90e009fef5e.exe File opened (read-only) \??\E: 2d427458f0c4e9ba28d6d9f785c365213c0ac9e3527e3efa7dedd90e009fef5e.exe File opened (read-only) \??\K: 2d427458f0c4e9ba28d6d9f785c365213c0ac9e3527e3efa7dedd90e009fef5e.exe File opened (read-only) \??\X: 2d427458f0c4e9ba28d6d9f785c365213c0ac9e3527e3efa7dedd90e009fef5e.exe -
Checks processor information in registry 2 TTPs 3 IoCs
Processor information is often read in order to detect sandboxing environments.
Processes:
2d427458f0c4e9ba28d6d9f785c365213c0ac9e3527e3efa7dedd90e009fef5e.exedescription ioc process Key opened \REGISTRY\MACHINE\HARDWARE\DESCRIPTION\System\CentralProcessor\0 2d427458f0c4e9ba28d6d9f785c365213c0ac9e3527e3efa7dedd90e009fef5e.exe Key value queried \REGISTRY\MACHINE\HARDWARE\DESCRIPTION\System\CentralProcessor\0\ProcessorNameString 2d427458f0c4e9ba28d6d9f785c365213c0ac9e3527e3efa7dedd90e009fef5e.exe Key value queried \REGISTRY\MACHINE\HARDWARE\DESCRIPTION\System\CentralProcessor\0\Identifier 2d427458f0c4e9ba28d6d9f785c365213c0ac9e3527e3efa7dedd90e009fef5e.exe -
Suspicious behavior: EnumeratesProcesses 4 IoCs
Processes:
2d427458f0c4e9ba28d6d9f785c365213c0ac9e3527e3efa7dedd90e009fef5e.exepid process 2680 2d427458f0c4e9ba28d6d9f785c365213c0ac9e3527e3efa7dedd90e009fef5e.exe 2680 2d427458f0c4e9ba28d6d9f785c365213c0ac9e3527e3efa7dedd90e009fef5e.exe 2680 2d427458f0c4e9ba28d6d9f785c365213c0ac9e3527e3efa7dedd90e009fef5e.exe 2680 2d427458f0c4e9ba28d6d9f785c365213c0ac9e3527e3efa7dedd90e009fef5e.exe -
Suspicious use of WriteProcessMemory 64 IoCs
Processes:
2d427458f0c4e9ba28d6d9f785c365213c0ac9e3527e3efa7dedd90e009fef5e.exedescription pid process target process PID 2680 wrote to memory of 2272 2680 2d427458f0c4e9ba28d6d9f785c365213c0ac9e3527e3efa7dedd90e009fef5e.exe nslookup.exe PID 2680 wrote to memory of 2272 2680 2d427458f0c4e9ba28d6d9f785c365213c0ac9e3527e3efa7dedd90e009fef5e.exe nslookup.exe PID 2680 wrote to memory of 2272 2680 2d427458f0c4e9ba28d6d9f785c365213c0ac9e3527e3efa7dedd90e009fef5e.exe nslookup.exe PID 2680 wrote to memory of 3516 2680 2d427458f0c4e9ba28d6d9f785c365213c0ac9e3527e3efa7dedd90e009fef5e.exe nslookup.exe PID 2680 wrote to memory of 3516 2680 2d427458f0c4e9ba28d6d9f785c365213c0ac9e3527e3efa7dedd90e009fef5e.exe nslookup.exe PID 2680 wrote to memory of 3516 2680 2d427458f0c4e9ba28d6d9f785c365213c0ac9e3527e3efa7dedd90e009fef5e.exe nslookup.exe PID 2680 wrote to memory of 1320 2680 2d427458f0c4e9ba28d6d9f785c365213c0ac9e3527e3efa7dedd90e009fef5e.exe nslookup.exe PID 2680 wrote to memory of 1320 2680 2d427458f0c4e9ba28d6d9f785c365213c0ac9e3527e3efa7dedd90e009fef5e.exe nslookup.exe PID 2680 wrote to memory of 1320 2680 2d427458f0c4e9ba28d6d9f785c365213c0ac9e3527e3efa7dedd90e009fef5e.exe nslookup.exe PID 2680 wrote to memory of 3896 2680 2d427458f0c4e9ba28d6d9f785c365213c0ac9e3527e3efa7dedd90e009fef5e.exe nslookup.exe PID 2680 wrote to memory of 3896 2680 2d427458f0c4e9ba28d6d9f785c365213c0ac9e3527e3efa7dedd90e009fef5e.exe nslookup.exe PID 2680 wrote to memory of 3896 2680 2d427458f0c4e9ba28d6d9f785c365213c0ac9e3527e3efa7dedd90e009fef5e.exe nslookup.exe PID 2680 wrote to memory of 740 2680 2d427458f0c4e9ba28d6d9f785c365213c0ac9e3527e3efa7dedd90e009fef5e.exe nslookup.exe PID 2680 wrote to memory of 740 2680 2d427458f0c4e9ba28d6d9f785c365213c0ac9e3527e3efa7dedd90e009fef5e.exe nslookup.exe PID 2680 wrote to memory of 740 2680 2d427458f0c4e9ba28d6d9f785c365213c0ac9e3527e3efa7dedd90e009fef5e.exe nslookup.exe PID 2680 wrote to memory of 2268 2680 2d427458f0c4e9ba28d6d9f785c365213c0ac9e3527e3efa7dedd90e009fef5e.exe nslookup.exe PID 2680 wrote to memory of 2268 2680 2d427458f0c4e9ba28d6d9f785c365213c0ac9e3527e3efa7dedd90e009fef5e.exe nslookup.exe PID 2680 wrote to memory of 2268 2680 2d427458f0c4e9ba28d6d9f785c365213c0ac9e3527e3efa7dedd90e009fef5e.exe nslookup.exe PID 2680 wrote to memory of 3508 2680 2d427458f0c4e9ba28d6d9f785c365213c0ac9e3527e3efa7dedd90e009fef5e.exe nslookup.exe PID 2680 wrote to memory of 3508 2680 2d427458f0c4e9ba28d6d9f785c365213c0ac9e3527e3efa7dedd90e009fef5e.exe nslookup.exe PID 2680 wrote to memory of 3508 2680 2d427458f0c4e9ba28d6d9f785c365213c0ac9e3527e3efa7dedd90e009fef5e.exe nslookup.exe PID 2680 wrote to memory of 748 2680 2d427458f0c4e9ba28d6d9f785c365213c0ac9e3527e3efa7dedd90e009fef5e.exe nslookup.exe PID 2680 wrote to memory of 748 2680 2d427458f0c4e9ba28d6d9f785c365213c0ac9e3527e3efa7dedd90e009fef5e.exe nslookup.exe PID 2680 wrote to memory of 748 2680 2d427458f0c4e9ba28d6d9f785c365213c0ac9e3527e3efa7dedd90e009fef5e.exe nslookup.exe PID 2680 wrote to memory of 2928 2680 2d427458f0c4e9ba28d6d9f785c365213c0ac9e3527e3efa7dedd90e009fef5e.exe nslookup.exe PID 2680 wrote to memory of 2928 2680 2d427458f0c4e9ba28d6d9f785c365213c0ac9e3527e3efa7dedd90e009fef5e.exe nslookup.exe PID 2680 wrote to memory of 2928 2680 2d427458f0c4e9ba28d6d9f785c365213c0ac9e3527e3efa7dedd90e009fef5e.exe nslookup.exe PID 2680 wrote to memory of 1948 2680 2d427458f0c4e9ba28d6d9f785c365213c0ac9e3527e3efa7dedd90e009fef5e.exe nslookup.exe PID 2680 wrote to memory of 1948 2680 2d427458f0c4e9ba28d6d9f785c365213c0ac9e3527e3efa7dedd90e009fef5e.exe nslookup.exe PID 2680 wrote to memory of 1948 2680 2d427458f0c4e9ba28d6d9f785c365213c0ac9e3527e3efa7dedd90e009fef5e.exe nslookup.exe PID 2680 wrote to memory of 1280 2680 2d427458f0c4e9ba28d6d9f785c365213c0ac9e3527e3efa7dedd90e009fef5e.exe nslookup.exe PID 2680 wrote to memory of 1280 2680 2d427458f0c4e9ba28d6d9f785c365213c0ac9e3527e3efa7dedd90e009fef5e.exe nslookup.exe PID 2680 wrote to memory of 1280 2680 2d427458f0c4e9ba28d6d9f785c365213c0ac9e3527e3efa7dedd90e009fef5e.exe nslookup.exe PID 2680 wrote to memory of 2872 2680 2d427458f0c4e9ba28d6d9f785c365213c0ac9e3527e3efa7dedd90e009fef5e.exe nslookup.exe PID 2680 wrote to memory of 2872 2680 2d427458f0c4e9ba28d6d9f785c365213c0ac9e3527e3efa7dedd90e009fef5e.exe nslookup.exe PID 2680 wrote to memory of 2872 2680 2d427458f0c4e9ba28d6d9f785c365213c0ac9e3527e3efa7dedd90e009fef5e.exe nslookup.exe PID 2680 wrote to memory of 1120 2680 2d427458f0c4e9ba28d6d9f785c365213c0ac9e3527e3efa7dedd90e009fef5e.exe nslookup.exe PID 2680 wrote to memory of 1120 2680 2d427458f0c4e9ba28d6d9f785c365213c0ac9e3527e3efa7dedd90e009fef5e.exe nslookup.exe PID 2680 wrote to memory of 1120 2680 2d427458f0c4e9ba28d6d9f785c365213c0ac9e3527e3efa7dedd90e009fef5e.exe nslookup.exe PID 2680 wrote to memory of 680 2680 2d427458f0c4e9ba28d6d9f785c365213c0ac9e3527e3efa7dedd90e009fef5e.exe nslookup.exe PID 2680 wrote to memory of 680 2680 2d427458f0c4e9ba28d6d9f785c365213c0ac9e3527e3efa7dedd90e009fef5e.exe nslookup.exe PID 2680 wrote to memory of 680 2680 2d427458f0c4e9ba28d6d9f785c365213c0ac9e3527e3efa7dedd90e009fef5e.exe nslookup.exe PID 2680 wrote to memory of 992 2680 2d427458f0c4e9ba28d6d9f785c365213c0ac9e3527e3efa7dedd90e009fef5e.exe nslookup.exe PID 2680 wrote to memory of 992 2680 2d427458f0c4e9ba28d6d9f785c365213c0ac9e3527e3efa7dedd90e009fef5e.exe nslookup.exe PID 2680 wrote to memory of 992 2680 2d427458f0c4e9ba28d6d9f785c365213c0ac9e3527e3efa7dedd90e009fef5e.exe nslookup.exe PID 2680 wrote to memory of 3868 2680 2d427458f0c4e9ba28d6d9f785c365213c0ac9e3527e3efa7dedd90e009fef5e.exe nslookup.exe PID 2680 wrote to memory of 3868 2680 2d427458f0c4e9ba28d6d9f785c365213c0ac9e3527e3efa7dedd90e009fef5e.exe nslookup.exe PID 2680 wrote to memory of 3868 2680 2d427458f0c4e9ba28d6d9f785c365213c0ac9e3527e3efa7dedd90e009fef5e.exe nslookup.exe PID 2680 wrote to memory of 3988 2680 2d427458f0c4e9ba28d6d9f785c365213c0ac9e3527e3efa7dedd90e009fef5e.exe nslookup.exe PID 2680 wrote to memory of 3988 2680 2d427458f0c4e9ba28d6d9f785c365213c0ac9e3527e3efa7dedd90e009fef5e.exe nslookup.exe PID 2680 wrote to memory of 3988 2680 2d427458f0c4e9ba28d6d9f785c365213c0ac9e3527e3efa7dedd90e009fef5e.exe nslookup.exe PID 2680 wrote to memory of 1640 2680 2d427458f0c4e9ba28d6d9f785c365213c0ac9e3527e3efa7dedd90e009fef5e.exe nslookup.exe PID 2680 wrote to memory of 1640 2680 2d427458f0c4e9ba28d6d9f785c365213c0ac9e3527e3efa7dedd90e009fef5e.exe nslookup.exe PID 2680 wrote to memory of 1640 2680 2d427458f0c4e9ba28d6d9f785c365213c0ac9e3527e3efa7dedd90e009fef5e.exe nslookup.exe PID 2680 wrote to memory of 2780 2680 2d427458f0c4e9ba28d6d9f785c365213c0ac9e3527e3efa7dedd90e009fef5e.exe nslookup.exe PID 2680 wrote to memory of 2780 2680 2d427458f0c4e9ba28d6d9f785c365213c0ac9e3527e3efa7dedd90e009fef5e.exe nslookup.exe PID 2680 wrote to memory of 2780 2680 2d427458f0c4e9ba28d6d9f785c365213c0ac9e3527e3efa7dedd90e009fef5e.exe nslookup.exe PID 2680 wrote to memory of 2828 2680 2d427458f0c4e9ba28d6d9f785c365213c0ac9e3527e3efa7dedd90e009fef5e.exe nslookup.exe PID 2680 wrote to memory of 2828 2680 2d427458f0c4e9ba28d6d9f785c365213c0ac9e3527e3efa7dedd90e009fef5e.exe nslookup.exe PID 2680 wrote to memory of 2828 2680 2d427458f0c4e9ba28d6d9f785c365213c0ac9e3527e3efa7dedd90e009fef5e.exe nslookup.exe PID 2680 wrote to memory of 3996 2680 2d427458f0c4e9ba28d6d9f785c365213c0ac9e3527e3efa7dedd90e009fef5e.exe nslookup.exe PID 2680 wrote to memory of 3996 2680 2d427458f0c4e9ba28d6d9f785c365213c0ac9e3527e3efa7dedd90e009fef5e.exe nslookup.exe PID 2680 wrote to memory of 3996 2680 2d427458f0c4e9ba28d6d9f785c365213c0ac9e3527e3efa7dedd90e009fef5e.exe nslookup.exe PID 2680 wrote to memory of 2116 2680 2d427458f0c4e9ba28d6d9f785c365213c0ac9e3527e3efa7dedd90e009fef5e.exe nslookup.exe
Processes
-
C:\Users\Admin\AppData\Local\Temp\2d427458f0c4e9ba28d6d9f785c365213c0ac9e3527e3efa7dedd90e009fef5e.exe"C:\Users\Admin\AppData\Local\Temp\2d427458f0c4e9ba28d6d9f785c365213c0ac9e3527e3efa7dedd90e009fef5e.exe"1⤵
- Adds Run key to start application
- Enumerates connected drives
- Checks processor information in registry
- Suspicious behavior: EnumeratesProcesses
- Suspicious use of WriteProcessMemory
-
C:\Windows\SysWOW64\nslookup.exenslookup carder.bit ns1.wowservers.ru2⤵
-
C:\Windows\SysWOW64\nslookup.exenslookup ransomware.bit ns2.wowservers.ru2⤵
-
C:\Windows\SysWOW64\nslookup.exenslookup carder.bit ns2.wowservers.ru2⤵
-
C:\Windows\SysWOW64\nslookup.exenslookup ransomware.bit ns1.wowservers.ru2⤵
-
C:\Windows\SysWOW64\nslookup.exenslookup carder.bit ns1.wowservers.ru2⤵
-
C:\Windows\SysWOW64\nslookup.exenslookup ransomware.bit ns2.wowservers.ru2⤵
-
C:\Windows\SysWOW64\nslookup.exenslookup carder.bit ns2.wowservers.ru2⤵
-
C:\Windows\SysWOW64\nslookup.exenslookup ransomware.bit ns1.wowservers.ru2⤵
-
C:\Windows\SysWOW64\nslookup.exenslookup carder.bit ns1.wowservers.ru2⤵
-
C:\Windows\SysWOW64\nslookup.exenslookup ransomware.bit ns2.wowservers.ru2⤵
-
C:\Windows\SysWOW64\nslookup.exenslookup carder.bit ns2.wowservers.ru2⤵
-
C:\Windows\SysWOW64\nslookup.exenslookup ransomware.bit ns1.wowservers.ru2⤵
-
C:\Windows\SysWOW64\nslookup.exenslookup carder.bit ns1.wowservers.ru2⤵
-
C:\Windows\SysWOW64\nslookup.exenslookup ransomware.bit ns2.wowservers.ru2⤵
-
C:\Windows\SysWOW64\nslookup.exenslookup carder.bit ns2.wowservers.ru2⤵
-
C:\Windows\SysWOW64\nslookup.exenslookup ransomware.bit ns1.wowservers.ru2⤵
-
C:\Windows\SysWOW64\nslookup.exenslookup carder.bit ns1.wowservers.ru2⤵
-
C:\Windows\SysWOW64\nslookup.exenslookup ransomware.bit ns2.wowservers.ru2⤵
-
C:\Windows\SysWOW64\nslookup.exenslookup carder.bit ns2.wowservers.ru2⤵
-
C:\Windows\SysWOW64\nslookup.exenslookup ransomware.bit ns1.wowservers.ru2⤵
-
C:\Windows\SysWOW64\nslookup.exenslookup carder.bit ns1.wowservers.ru2⤵
-
C:\Windows\SysWOW64\nslookup.exenslookup ransomware.bit ns2.wowservers.ru2⤵
-
C:\Windows\SysWOW64\nslookup.exenslookup carder.bit ns2.wowservers.ru2⤵
-
C:\Windows\SysWOW64\nslookup.exenslookup ransomware.bit ns1.wowservers.ru2⤵
-
C:\Windows\SysWOW64\nslookup.exenslookup carder.bit ns1.wowservers.ru2⤵
-
C:\Windows\SysWOW64\nslookup.exenslookup ransomware.bit ns2.wowservers.ru2⤵
-
C:\Windows\SysWOW64\nslookup.exenslookup carder.bit ns2.wowservers.ru2⤵
-
C:\Windows\SysWOW64\nslookup.exenslookup ransomware.bit ns1.wowservers.ru2⤵
-
C:\Windows\SysWOW64\nslookup.exenslookup carder.bit ns1.wowservers.ru2⤵
-
C:\Windows\SysWOW64\nslookup.exenslookup ransomware.bit ns2.wowservers.ru2⤵
-
C:\Windows\SysWOW64\nslookup.exenslookup carder.bit ns2.wowservers.ru2⤵
-
C:\Windows\SysWOW64\nslookup.exenslookup ransomware.bit ns1.wowservers.ru2⤵
-
C:\Windows\SysWOW64\nslookup.exenslookup carder.bit ns1.wowservers.ru2⤵
-
C:\Windows\SysWOW64\nslookup.exenslookup ransomware.bit ns2.wowservers.ru2⤵
-
C:\Windows\SysWOW64\nslookup.exenslookup carder.bit ns2.wowservers.ru2⤵
-
C:\Windows\SysWOW64\nslookup.exenslookup ransomware.bit ns1.wowservers.ru2⤵
-
C:\Windows\SysWOW64\nslookup.exenslookup carder.bit ns1.wowservers.ru2⤵
-
C:\Windows\SysWOW64\nslookup.exenslookup ransomware.bit ns2.wowservers.ru2⤵
-
C:\Windows\SysWOW64\nslookup.exenslookup carder.bit ns2.wowservers.ru2⤵
-
C:\Windows\SysWOW64\nslookup.exenslookup ransomware.bit ns1.wowservers.ru2⤵
-
C:\Windows\SysWOW64\nslookup.exenslookup carder.bit ns1.wowservers.ru2⤵
-
C:\Windows\SysWOW64\nslookup.exenslookup ransomware.bit ns2.wowservers.ru2⤵
-
C:\Windows\SysWOW64\nslookup.exenslookup carder.bit ns2.wowservers.ru2⤵
-
C:\Windows\SysWOW64\nslookup.exenslookup ransomware.bit ns1.wowservers.ru2⤵
-
C:\Windows\SysWOW64\nslookup.exenslookup carder.bit ns1.wowservers.ru2⤵
-
C:\Windows\SysWOW64\nslookup.exenslookup ransomware.bit ns2.wowservers.ru2⤵
-
C:\Windows\SysWOW64\nslookup.exenslookup carder.bit ns2.wowservers.ru2⤵
-
C:\Windows\SysWOW64\nslookup.exenslookup ransomware.bit ns1.wowservers.ru2⤵
-
C:\Windows\SysWOW64\nslookup.exenslookup carder.bit ns1.wowservers.ru2⤵
-
C:\Windows\SysWOW64\nslookup.exenslookup ransomware.bit ns2.wowservers.ru2⤵
-
C:\Windows\SysWOW64\nslookup.exenslookup carder.bit ns2.wowservers.ru2⤵
-
C:\Windows\SysWOW64\nslookup.exenslookup ransomware.bit ns1.wowservers.ru2⤵
-
C:\Windows\SysWOW64\nslookup.exenslookup carder.bit ns1.wowservers.ru2⤵
-
C:\Windows\SysWOW64\nslookup.exenslookup ransomware.bit ns2.wowservers.ru2⤵
-
C:\Windows\SysWOW64\nslookup.exenslookup carder.bit ns2.wowservers.ru2⤵
-
C:\Windows\SysWOW64\nslookup.exenslookup ransomware.bit ns1.wowservers.ru2⤵
-
C:\Windows\SysWOW64\nslookup.exenslookup carder.bit ns1.wowservers.ru2⤵
-
C:\Windows\SysWOW64\nslookup.exenslookup ransomware.bit ns2.wowservers.ru2⤵
-
C:\Windows\SysWOW64\nslookup.exenslookup carder.bit ns2.wowservers.ru2⤵
-
C:\Windows\SysWOW64\nslookup.exenslookup ransomware.bit ns1.wowservers.ru2⤵
-
C:\Windows\SysWOW64\nslookup.exenslookup carder.bit ns1.wowservers.ru2⤵
-
C:\Windows\SysWOW64\nslookup.exenslookup ransomware.bit ns2.wowservers.ru2⤵
-
C:\Windows\SysWOW64\nslookup.exenslookup carder.bit ns2.wowservers.ru2⤵
-
C:\Windows\SysWOW64\nslookup.exenslookup ransomware.bit ns1.wowservers.ru2⤵
-
C:\Windows\SysWOW64\nslookup.exenslookup carder.bit ns1.wowservers.ru2⤵
-
C:\Windows\SysWOW64\nslookup.exenslookup ransomware.bit ns2.wowservers.ru2⤵
-
C:\Windows\SysWOW64\nslookup.exenslookup carder.bit ns2.wowservers.ru2⤵
-
C:\Windows\SysWOW64\nslookup.exenslookup ransomware.bit ns1.wowservers.ru2⤵
-
C:\Windows\SysWOW64\nslookup.exenslookup carder.bit ns1.wowservers.ru2⤵
-
C:\Windows\SysWOW64\nslookup.exenslookup ransomware.bit ns2.wowservers.ru2⤵
-
C:\Windows\SysWOW64\nslookup.exenslookup carder.bit ns2.wowservers.ru2⤵
-
C:\Windows\SysWOW64\nslookup.exenslookup ransomware.bit ns1.wowservers.ru2⤵
-
C:\Windows\SysWOW64\nslookup.exenslookup carder.bit ns1.wowservers.ru2⤵
-
C:\Windows\SysWOW64\nslookup.exenslookup ransomware.bit ns2.wowservers.ru2⤵
-
C:\Windows\SysWOW64\nslookup.exenslookup carder.bit ns2.wowservers.ru2⤵
-
C:\Windows\SysWOW64\nslookup.exenslookup ransomware.bit ns1.wowservers.ru2⤵
-
C:\Windows\SysWOW64\nslookup.exenslookup carder.bit ns1.wowservers.ru2⤵
-
C:\Windows\SysWOW64\nslookup.exenslookup ransomware.bit ns2.wowservers.ru2⤵
-
C:\Windows\SysWOW64\nslookup.exenslookup carder.bit ns2.wowservers.ru2⤵
-
C:\Windows\SysWOW64\nslookup.exenslookup ransomware.bit ns1.wowservers.ru2⤵
-
C:\Windows\SysWOW64\nslookup.exenslookup carder.bit ns1.wowservers.ru2⤵
-
C:\Windows\SysWOW64\nslookup.exenslookup ransomware.bit ns2.wowservers.ru2⤵
-
C:\Windows\SysWOW64\nslookup.exenslookup carder.bit ns2.wowservers.ru2⤵
-
C:\Windows\SysWOW64\nslookup.exenslookup ransomware.bit ns1.wowservers.ru2⤵
-
C:\Windows\SysWOW64\nslookup.exenslookup carder.bit ns1.wowservers.ru2⤵
-
C:\Windows\SysWOW64\nslookup.exenslookup ransomware.bit ns2.wowservers.ru2⤵
-
C:\Windows\SysWOW64\nslookup.exenslookup carder.bit ns2.wowservers.ru2⤵
-
C:\Windows\SysWOW64\nslookup.exenslookup ransomware.bit ns1.wowservers.ru2⤵
-
C:\Windows\SysWOW64\nslookup.exenslookup carder.bit ns1.wowservers.ru2⤵
-
C:\Windows\SysWOW64\nslookup.exenslookup ransomware.bit ns2.wowservers.ru2⤵
-
C:\Windows\SysWOW64\nslookup.exenslookup carder.bit ns2.wowservers.ru2⤵
-
C:\Windows\SysWOW64\nslookup.exenslookup ransomware.bit ns1.wowservers.ru2⤵
-
C:\Windows\SysWOW64\nslookup.exenslookup carder.bit ns1.wowservers.ru2⤵
-
C:\Windows\SysWOW64\nslookup.exenslookup ransomware.bit ns2.wowservers.ru2⤵
-
C:\Windows\SysWOW64\nslookup.exenslookup carder.bit ns2.wowservers.ru2⤵
-
C:\Windows\SysWOW64\nslookup.exenslookup ransomware.bit ns1.wowservers.ru2⤵
-
C:\Windows\SysWOW64\nslookup.exenslookup carder.bit ns1.wowservers.ru2⤵
-
C:\Windows\SysWOW64\nslookup.exenslookup ransomware.bit ns2.wowservers.ru2⤵
-
C:\Windows\SysWOW64\nslookup.exenslookup carder.bit ns2.wowservers.ru2⤵
-
C:\Windows\SysWOW64\nslookup.exenslookup ransomware.bit ns1.wowservers.ru2⤵
-
C:\Windows\SysWOW64\nslookup.exenslookup carder.bit ns1.wowservers.ru2⤵
-
C:\Windows\SysWOW64\nslookup.exenslookup ransomware.bit ns2.wowservers.ru2⤵
-
C:\Windows\SysWOW64\nslookup.exenslookup carder.bit ns2.wowservers.ru2⤵
-
C:\Windows\SysWOW64\nslookup.exenslookup ransomware.bit ns1.wowservers.ru2⤵
-
C:\Windows\SysWOW64\nslookup.exenslookup carder.bit ns1.wowservers.ru2⤵
-
C:\Windows\SysWOW64\nslookup.exenslookup ransomware.bit ns2.wowservers.ru2⤵
-
C:\Windows\SysWOW64\nslookup.exenslookup carder.bit ns2.wowservers.ru2⤵
-
C:\Windows\SysWOW64\nslookup.exenslookup ransomware.bit ns1.wowservers.ru2⤵
-
C:\Windows\SysWOW64\nslookup.exenslookup carder.bit ns1.wowservers.ru2⤵
-
C:\Windows\SysWOW64\nslookup.exenslookup ransomware.bit ns2.wowservers.ru2⤵
-
C:\Windows\SysWOW64\nslookup.exenslookup carder.bit ns2.wowservers.ru2⤵
-
C:\Windows\SysWOW64\nslookup.exenslookup ransomware.bit ns1.wowservers.ru2⤵
-
C:\Windows\SysWOW64\nslookup.exenslookup carder.bit ns1.wowservers.ru2⤵
-
C:\Windows\SysWOW64\nslookup.exenslookup ransomware.bit ns2.wowservers.ru2⤵
-
C:\Windows\SysWOW64\nslookup.exenslookup carder.bit ns2.wowservers.ru2⤵
-
C:\Windows\SysWOW64\nslookup.exenslookup ransomware.bit ns1.wowservers.ru2⤵
-
C:\Windows\SysWOW64\nslookup.exenslookup carder.bit ns1.wowservers.ru2⤵
-
C:\Windows\SysWOW64\nslookup.exenslookup ransomware.bit ns2.wowservers.ru2⤵
-
C:\Windows\SysWOW64\nslookup.exenslookup carder.bit ns2.wowservers.ru2⤵
-
C:\Windows\SysWOW64\nslookup.exenslookup ransomware.bit ns1.wowservers.ru2⤵
-
C:\Windows\SysWOW64\nslookup.exenslookup carder.bit ns1.wowservers.ru2⤵
-
C:\Windows\SysWOW64\nslookup.exenslookup ransomware.bit ns2.wowservers.ru2⤵
-
C:\Windows\SysWOW64\nslookup.exenslookup carder.bit ns2.wowservers.ru2⤵
-
C:\Windows\SysWOW64\nslookup.exenslookup ransomware.bit ns1.wowservers.ru2⤵
-
C:\Windows\SysWOW64\nslookup.exenslookup carder.bit ns1.wowservers.ru2⤵
Network
MITRE ATT&CK Matrix ATT&CK v6
Replay Monitor
Loading Replay Monitor...
Downloads
-
memory/364-146-0x0000000000000000-mapping.dmp
-
memory/416-172-0x0000000000000000-mapping.dmp
-
memory/680-129-0x0000000000000000-mapping.dmp
-
memory/740-120-0x0000000000000000-mapping.dmp
-
memory/748-123-0x0000000000000000-mapping.dmp
-
memory/932-170-0x0000000000000000-mapping.dmp
-
memory/992-130-0x0000000000000000-mapping.dmp
-
memory/1120-128-0x0000000000000000-mapping.dmp
-
memory/1192-177-0x0000000000000000-mapping.dmp
-
memory/1204-153-0x0000000000000000-mapping.dmp
-
memory/1276-162-0x0000000000000000-mapping.dmp
-
memory/1280-126-0x0000000000000000-mapping.dmp
-
memory/1320-118-0x0000000000000000-mapping.dmp
-
memory/1496-140-0x0000000000000000-mapping.dmp
-
memory/1604-145-0x0000000000000000-mapping.dmp
-
memory/1640-133-0x0000000000000000-mapping.dmp
-
memory/1660-156-0x0000000000000000-mapping.dmp
-
memory/1664-173-0x0000000000000000-mapping.dmp
-
memory/1772-163-0x0000000000000000-mapping.dmp
-
memory/1792-169-0x0000000000000000-mapping.dmp
-
memory/1804-147-0x0000000000000000-mapping.dmp
-
memory/1896-157-0x0000000000000000-mapping.dmp
-
memory/1948-125-0x0000000000000000-mapping.dmp
-
memory/2116-137-0x0000000000000000-mapping.dmp
-
memory/2176-167-0x0000000000000000-mapping.dmp
-
memory/2192-176-0x0000000000000000-mapping.dmp
-
memory/2228-160-0x0000000000000000-mapping.dmp
-
memory/2268-121-0x0000000000000000-mapping.dmp
-
memory/2272-116-0x0000000000000000-mapping.dmp
-
memory/2316-143-0x0000000000000000-mapping.dmp
-
memory/2532-164-0x0000000000000000-mapping.dmp
-
memory/2536-165-0x0000000000000000-mapping.dmp
-
memory/2660-148-0x0000000000000000-mapping.dmp
-
memory/2676-178-0x0000000000000000-mapping.dmp
-
memory/2680-114-0x0000000000400000-0x000000000238C000-memory.dmpFilesize
31.5MB
-
memory/2680-115-0x0000000002390000-0x00000000024DA000-memory.dmpFilesize
1.3MB
-
memory/2780-134-0x0000000000000000-mapping.dmp
-
memory/2792-155-0x0000000000000000-mapping.dmp
-
memory/2828-135-0x0000000000000000-mapping.dmp
-
memory/2844-149-0x0000000000000000-mapping.dmp
-
memory/2872-127-0x0000000000000000-mapping.dmp
-
memory/2928-124-0x0000000000000000-mapping.dmp
-
memory/3004-152-0x0000000000000000-mapping.dmp
-
memory/3032-151-0x0000000000000000-mapping.dmp
-
memory/3128-154-0x0000000000000000-mapping.dmp
-
memory/3156-144-0x0000000000000000-mapping.dmp
-
memory/3184-142-0x0000000000000000-mapping.dmp
-
memory/3276-161-0x0000000000000000-mapping.dmp
-
memory/3508-122-0x0000000000000000-mapping.dmp
-
memory/3516-117-0x0000000000000000-mapping.dmp
-
memory/3676-171-0x0000000000000000-mapping.dmp
-
memory/3724-168-0x0000000000000000-mapping.dmp
-
memory/3788-150-0x0000000000000000-mapping.dmp
-
memory/3792-158-0x0000000000000000-mapping.dmp
-
memory/3828-166-0x0000000000000000-mapping.dmp
-
memory/3864-175-0x0000000000000000-mapping.dmp
-
memory/3868-131-0x0000000000000000-mapping.dmp
-
memory/3888-139-0x0000000000000000-mapping.dmp
-
memory/3896-119-0x0000000000000000-mapping.dmp
-
memory/3976-141-0x0000000000000000-mapping.dmp
-
memory/3980-174-0x0000000000000000-mapping.dmp
-
memory/3988-132-0x0000000000000000-mapping.dmp
-
memory/3996-136-0x0000000000000000-mapping.dmp
-
memory/4008-179-0x0000000000000000-mapping.dmp
-
memory/4032-138-0x0000000000000000-mapping.dmp
-
memory/4092-159-0x0000000000000000-mapping.dmp