Analysis

  • max time kernel
    150s
  • max time network
    139s
  • platform
    windows10-2004_x64
  • resource
    win10v2004-20220901-en
  • resource tags

    arch:x64arch:x86image:win10v2004-20220901-enlocale:en-usos:windows10-2004-x64system
  • submitted
    07-12-2022 18:19

General

  • Target

    Ref.lnk

  • Size

    1KB

  • MD5

    3b15d9136dea320ca9439e9bcbd9cf07

  • SHA1

    723642ab63a9deb3de4f321f084b810ba3e35785

  • SHA256

    bdc4330217f2bf929d3a6e26961da921c138cbd6c0a71b03ddf5bbd30fe5a8e9

  • SHA512

    a569731a3f1e0bb791da7443991703d975f596ff9868c838c26555ef2b53d759a00a68961daa58d25d86d5f1a8b719f424e5566924df9f93566b0fbb0ed8d75e

Malware Config

Extracted

Family

qakbot

Version

404.46

Botnet

obama226

Campaign

1670237875

C2

76.100.159.250:443

66.191.69.18:995

186.64.67.9:443

50.90.249.161:443

109.150.179.158:2222

92.149.205.238:2222

86.165.15.180:2222

41.44.19.36:995

78.17.157.5:443

173.18.126.3:443

75.99.125.235:2222

172.90.139.138:2222

27.99.45.237:2222

91.68.227.219:443

12.172.173.82:993

103.144.201.62:2078

12.172.173.82:990

173.239.94.212:443

91.169.12.198:32100

24.64.114.59:2222

Attributes
  • salt

    SoNuce]ugdiB3c[doMuce2s81*uXmcvP

Signatures

  • Qakbot/Qbot

    Qbot or Qakbot is a sophisticated worm with banking capabilities.

  • Checks computer location settings 2 TTPs 1 IoCs

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

  • Enumerates physical storage devices 1 TTPs

    Attempts to interact with connected storage/optical drive(s). Likely ransomware behaviour.

  • Suspicious behavior: EnumeratesProcesses 64 IoCs
  • Suspicious behavior: MapViewOfSection 1 IoCs
  • Suspicious use of WriteProcessMemory 16 IoCs

Processes

  • C:\Windows\system32\cmd.exe
    cmd /c C:\Users\Admin\AppData\Local\Temp\Ref.lnk
    1⤵
    • Checks computer location settings
    • Suspicious use of WriteProcessMemory
    PID:4896
    • C:\Windows\System32\cmd.exe
      "C:\Windows\System32\cmd.exe" /c buyer\persecutes.cmd
      2⤵
      • Suspicious use of WriteProcessMemory
      PID:4864
      • C:\Windows\system32\cmd.exe
        C:\Windows\system32\cmd.exe /K buyer\actualities.cmd system rundl
        3⤵
        • Suspicious use of WriteProcessMemory
        PID:4760
        • C:\Windows\system32\replace.exe
          replace C:\Windows\\system32\\rundlr32.exe C:\Users\Admin\AppData\Local\Temp /A
          4⤵
            PID:1576
          • C:\Windows\system32\rundll32.exe
            rundll32 buyer\\mobbed.tmp,DrawThemeIcon
            4⤵
            • Suspicious use of WriteProcessMemory
            PID:3668
            • C:\Windows\SysWOW64\rundll32.exe
              rundll32 buyer\\mobbed.tmp,DrawThemeIcon
              5⤵
              • Suspicious behavior: EnumeratesProcesses
              • Suspicious behavior: MapViewOfSection
              • Suspicious use of WriteProcessMemory
              PID:3184
              • C:\Windows\SysWOW64\wermgr.exe
                C:\Windows\SysWOW64\wermgr.exe
                6⤵
                • Suspicious behavior: EnumeratesProcesses
                PID:4656

    Network

    MITRE ATT&CK Matrix ATT&CK v6

    Discovery

    Query Registry

    1
    T1012

    System Information Discovery

    2
    T1082

    Replay Monitor

    Loading Replay Monitor...

    Downloads

    • memory/1576-134-0x0000000000000000-mapping.dmp
    • memory/3184-136-0x0000000000000000-mapping.dmp
    • memory/3184-137-0x0000000000E30000-0x0000000000E58000-memory.dmp
      Filesize

      160KB

    • memory/3184-138-0x0000000000E60000-0x0000000000E8A000-memory.dmp
      Filesize

      168KB

    • memory/3184-140-0x0000000000E60000-0x0000000000E8A000-memory.dmp
      Filesize

      168KB

    • memory/3668-135-0x0000000000000000-mapping.dmp
    • memory/4656-139-0x0000000000000000-mapping.dmp
    • memory/4656-141-0x0000000000CC0000-0x0000000000CEA000-memory.dmp
      Filesize

      168KB

    • memory/4656-142-0x0000000000CC0000-0x0000000000CEA000-memory.dmp
      Filesize

      168KB

    • memory/4760-133-0x0000000000000000-mapping.dmp
    • memory/4864-132-0x0000000000000000-mapping.dmp