Home / malwarePDF  

DDoS:Win32/Nitol.K


First posted on 16 October 2015.
Source: Microsoft

Aliases :

There are no other names known for DDoS:Win32/Nitol.K.

Explanation :

Threat behavior

Installation
This threat can create files on your PC, including:

  • %SystemRoot%\system.exe
  • \perfc009.dat
  • \perfh009.dat


The malware uses code injection to make it harder to detect and remove. It can inject code into running processes.



Payload
Uses your PC in DDoS attacks

This threat can use your PC to conduct distributed denial of service (DDoS) attacks.

During an attack, your Internet connection might run slower than usual.



Connects to a remote host

We have seen this threat connect to a remote host, including:
  • klss.basec.cc using port 7088
Malware can connect to a remote host to do any of the following:
  • Check for an Internet connection
  • Download and run files (including updates or other malware)
  • Report a new infection to its author
  • Receive configuration or other data
  • Receive instructions from a malicious hacker
  • Search for your PC location
  • Upload information taken from your PC
  • Validate a digital certificate


Additional information

Creates a mutex

This threat can create one or more mutexes on your PC. For example:

  • \...\Installing
  • G{B5665124-2B19-40e2-A7BC-B44321E72C4B}
  • G{D19BAF17-7C87-467E-8D63-6C4B1C836373}
  • LOADPERF_MUTEX


It might use this mutex as an infection marker to prevent more than one copy of the threat running on your PC.



This malware description was published using automated analysis of file SHA1 00abf5f71553aeedaf744e0260e539afcdfa10b1.

Symptoms

The following can indicate that you have this threat on your PC:

  • You see a file similar to:
    • %SystemRoot%\system.exe
    • \perfc009.dat
    • \perfh009.dat
  • You see registry modifications such as:
    • In subkey: HKLM\System\CurrentControlSet\Control\Session Manager
      Sets value: "PendingFileRenameOperations"
      With data: "c:\users\admini~1\appdata\local\temp\bfa9c"

    • In subkey: HKLM\SYSTEM\CurrentControlSet\Services\Pqrstu Bcdefghi Klm
      Sets value: "Description"
      With data: "pqrstu bcdefghi klmnopqr tuab"

    • In subkey: HKLM\SYSTEM\CurrentControlSet\Services\WmiApRpl\Performance
      Sets value: "First Counter"
      With data: "0x00001e2a"

    • In subkey: HKLM\SYSTEM\CurrentControlSet\Services\WmiApRpl\Performance
      Sets value: "First Help"
      With data: "0x00001e2b"

    • In subkey: HKLM\SYSTEM\CurrentControlSet\Services\WmiApRpl\Performance
      Sets value: "Last Counter"
      With data: "0x00001ed0"

    • In subkey: HKLM\SYSTEM\CurrentControlSet\Services\WmiApRpl\Performance
      Sets value: "Last Help"
      With data: "0x00001ed1"

    • In subkey: HKLM\SYSTEM\CurrentControlSet\Services\WmiApRpl\Performance
      Sets value: "Object List"
      With data: "7722 7728 7738 7748 7768 7812 7822 7860 7866 7882"

    • In subkey: HKLM\SYSTEM\CurrentControlSet\Services\WmiApRpl\Performance
      Sets value: "PerfIniFile"
      With data: "wmiaprpl.ini"

  • You see the following mutex:
    • \...\Installing
    • G{B5665124-2B19-40e2-A7BC-B44321E72C4B}
    • G{D19BAF17-7C87-467E-8D63-6C4B1C836373}
    • LOADPERF_MUTEX

Last update 16 October 2015

 

TOP