General

  • Target

    2HAX8_DeadPayload.exe

  • Size

    500KB

  • Sample

    241031-kx6xwawqgj

  • MD5

    b315d6de4d0834723914982447aab54f

  • SHA1

    f1b3b51e74e1f24faecf0524e7bbffe54feffe2e

  • SHA256

    75636b480a5d5c94fde4c189286ea07a3c12194de8ee8bb18cd462d3ae019f2b

  • SHA512

    b9afa7e84d33513e2255b24842847a9c25fc041b0d8e361836b4c2fd3787fba5b9a06c7633f1bb9b61ca56c650ddccd992a533b64f71105b6c36b69c648382ee

  • SSDEEP

    12288:s3DTkV1ilKya0FOUuQ0gH+kmtbF6W05EJXp107sdzO:mkGTy

Malware Config

Extracted

Family

xworm

Version

5.0

Mutex

QgVg78qW15uIsQ4H

Attributes
  • Install_directory

    %Public%

  • install_file

    ohh.exe

  • pastebin_url

    https://pastebin.com/raw/J09JweeH

aes.plain

Targets

    • Target

      2HAX8_DeadPayload.exe

    • Size

      500KB

    • MD5

      b315d6de4d0834723914982447aab54f

    • SHA1

      f1b3b51e74e1f24faecf0524e7bbffe54feffe2e

    • SHA256

      75636b480a5d5c94fde4c189286ea07a3c12194de8ee8bb18cd462d3ae019f2b

    • SHA512

      b9afa7e84d33513e2255b24842847a9c25fc041b0d8e361836b4c2fd3787fba5b9a06c7633f1bb9b61ca56c650ddccd992a533b64f71105b6c36b69c648382ee

    • SSDEEP

      12288:s3DTkV1ilKya0FOUuQ0gH+kmtbF6W05EJXp107sdzO:mkGTy

    • Detect Xworm Payload

    • Modifies security service

    • Suspicious use of NtCreateUserProcessOtherParentProcess

    • Xworm

      Xworm is a remote access trojan written in C#.

    • Xworm family

    • Sets service image path in registry

    • Checks BIOS information in registry

      BIOS information is often read in order to detect sandboxing environments.

    • Checks computer location settings

      Looks up country code configured in the registry, likely geofence.

    • Executes dropped EXE

    • Indicator Removal: Clear Windows Event Logs

      Clear Windows Event Logs to hide the activity of an intrusion.

    • Command and Scripting Interpreter: PowerShell

      Using powershell.exe command.

    • Enumerates connected drives

      Attempts to read the root path of hard drives other than the default C: drive.

    • Writes to the Master Boot Record (MBR)

      Bootkits write to the MBR to gain persistence at a level below the operating system.

    • Drops file in System32 directory

    • Suspicious use of SetThreadContext

MITRE ATT&CK Enterprise v15

Tasks