arrow_back
search
close

HackTool.Win32.AutoKMS.B

April 15, 2024
 Analysis by: John Rainier Navato
 ALIASES:

HackTool.Win32.KMSAuto.by (KASPERSKY)

 PLATFORM:

Windows

 OVERALL RISK RATING:
 DAMAGE POTENTIAL:
 DISTRIBUTION POTENTIAL:
 REPORTED INFECTION:
 INFORMATION EXPOSURE:

  • Threat Type: Hacking Tool

  • Destructiveness: No

  • Encrypted:

  • In the wild: Yes

  OVERVIEW

This Hacking Tool arrives on a system as a file dropped by other malware or as a file downloaded unknowingly by users when visiting malicious sites.

It does not have any propagation routine.

It does not have any backdoor routine.

It does not have any information-stealing capability.

  TECHNICAL DETAILS

File Size:

35,448 bytes

File Type:

EXE

Memory Resident:

No

Initial Samples Received Date:

26 Mar 2024

Payload:

Listen ports

Arrival Details

This Hacking Tool arrives on a system as a file dropped by other malware or as a file downloaded unknowingly by users when visiting malicious sites.

Installation

This Hacking Tool drops the following files:

  • {HackTool File Path}\{Hacktool File Name}.log → if -Log parameter is used

Propagation

This Hacking Tool does not have any propagation routine.

Backdoor Routine

This Hacking Tool does not have any backdoor routine.

Rootkit Capabilities

This Hacking Tool does not have rootkit capabilities.

Information Theft

This Hacking Tool does not have any information-stealing capability.

Other Details

This Hacking Tool does the following:

  • It is used as a server capable of activating the following software:
    • Office 2010
    • Office 2013
    • Office 2016
    • Windows 10
    • Windows 8
    • Windows 8.1
    • Windows 7
    • Windows Vista
    • Windows Server 2015
    • Windows Server 2012
    • Windows Server 2008
  • It listens on the following port for clients requesting to activate the said software:
    • tcp://{BLOCKED}.{BLOCKED}.{BLOCKED}.{BLOCKED}:1688

NOTES:

It accepts the following parameters:

  • -Port {Port Value} → Used to replace default KMS Port, ranges from 1 to 65535
  • -PWin {PID} → Windows PID
  • -PO14 {PID} →Used to replace default Office 2010 Product ID
  • -PO15 {PID} → Used to replace default Office 2013 Product ID
  • -PO16 {PID} → Used to replace default Office 2016 Product ID
  • -AI {Interval} → Used to replace default activation interval, ranges from 15 to 43200 minutes
  • -RI {Interval} → Used to replace default renewal interval, ranges from 15 to 43200 minutes
  • -Debug → Used to show detailed info of its activity.
  • -Log → Used to enable logging of its activity on a log file.
  • -Hwid {HWID} → Used to replace default machine hardware hash
  • -? or /? → Used to show usage guide for itself

It does not exploit any vulnerability.

  SOLUTION

Minimum Scan Engine:

9.800

SSAPI PATTERN File:

2.713.00

SSAPI PATTERN Date:

28 Mar 2024

Step 1

Before doing any scans, Windows 7, Windows 8, Windows 8.1, and Windows 10 users must disable System Restore to allow full scanning of their computers.

Step 2

Note that not all files, folders, and registry keys and entries are installed on your computer during this malware's/spyware's/grayware's execution. This may be due to incomplete installation or other operating system conditions. If you do not find the same files/folders/registry information, please proceed to the next step.

Step 3

Search and delete this file

[ Learn More ]
There may be some files that are hidden. Please make sure you check the Search Hidden Files and Folders checkbox in the "More advanced options" option to include all hidden files and folders in the search result.  
  • {HackTool File Path}\{Hacktool File Name}.log

Step 4

Scan your computer with your Trend Micro product to delete files detected as HackTool.Win32.AutoKMS.B. If the detected files have already been cleaned, deleted, or quarantined by your Trend Micro product, no further step is required. You may opt to simply delete the quarantined files. Please check the following Trend Micro Support pages for more information:


Did this description help? Tell us how we did.