Analysis

  • max time kernel
    150s
  • max time network
    149s
  • platform
    windows10_x64
  • resource
    win10v20210410
  • submitted
    21-07-2021 18:40

General

  • Target

    f70c0885e76e57f37399d54b10f183ad.xls

  • Size

    313KB

  • MD5

    f70c0885e76e57f37399d54b10f183ad

  • SHA1

    20548e3304d242789766edfe7c8c7d4e9ccd5b25

  • SHA256

    b11c33ee5fd193e6548d14c2bde4865d30d6d5fd25135bc258cfd8595ae3695c

  • SHA512

    5724457de05561b7e54380c3e3157f0f102084699c04340969394b03f6767e0d99a5e3f2a03871483ae7a3a2822e46a923ac85f433fdbfc64a56e6d93a763f6b

Malware Config

Extracted

Family

dridex

Botnet

22202

C2

178.238.236.59:443

104.245.52.73:5007

81.0.236.93:13786

rc4.plain
rc4.plain

Signatures

  • Dridex

    Dridex(known as Bugat/Cridex) is a form of malware that specializes in stealing bank credentials.

  • Process spawned unexpected child process 1 IoCs

    This typically indicates the parent process was compromised via an exploit or macro.

  • Dridex Loader 1 IoCs

    Detects Dridex both x86 and x64 loader in memory.

  • Blocklisted process makes network request 1 IoCs
  • Downloads MZ/PE file
  • Loads dropped DLL 1 IoCs
  • Checks whether UAC is enabled 1 TTPs 1 IoCs
  • Checks processor information in registry 2 TTPs 3 IoCs

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

  • Enumerates system info in registry 2 TTPs 3 IoCs
  • Suspicious behavior: AddClipboardFormatListener 1 IoCs
  • Suspicious use of SetWindowsHookEx 14 IoCs
  • Suspicious use of WriteProcessMemory 7 IoCs

Processes

  • C:\Program Files\Microsoft Office\Root\Office16\EXCEL.EXE
    "C:\Program Files\Microsoft Office\Root\Office16\EXCEL.EXE" "C:\Users\Admin\AppData\Local\Temp\f70c0885e76e57f37399d54b10f183ad.xls"
    1⤵
    • Checks processor information in registry
    • Enumerates system info in registry
    • Suspicious behavior: AddClipboardFormatListener
    • Suspicious use of SetWindowsHookEx
    • Suspicious use of WriteProcessMemory
    PID:3680
    • C:\Windows\SYSTEM32\mshta.exe
      mshta C:\ProgramData//klCylinderCol.sct
      2⤵
      • Process spawned unexpected child process
      • Blocklisted process makes network request
      • Suspicious use of WriteProcessMemory
      PID:1212
      • C:\Windows\SYSTEM32\rundll32.exe
        rundll32.exe C:\ProgramData\qSmartTagControlButton.dll,SetRealTimeUsage
        3⤵
        • Suspicious use of WriteProcessMemory
        PID:3456
        • C:\Windows\SysWOW64\rundll32.exe
          rundll32.exe C:\ProgramData\qSmartTagControlButton.dll,SetRealTimeUsage
          4⤵
          • Loads dropped DLL
          • Checks whether UAC is enabled
          PID:3348

Network

MITRE ATT&CK Enterprise v6

Replay Monitor

Loading Replay Monitor...

Downloads

  • C:\ProgramData\klCylinderCol.sct

    MD5

    6266b66d75cc153152d30f7a63452911

    SHA1

    baea6e86c331aca229b4a30377d2f5ddaa7f147f

    SHA256

    17c2979a15186f40d2108a415e89e4ca08a125db3b04a85aecd4f149e1f66fa2

    SHA512

    50d2728a86b53c4007be65f1dcc5397a09eb3089f92da24b7bcce273cabc9ac8936662ae4f728799af554a36e199a64550e3003bfbb14439b870b58f47c0e086

  • C:\ProgramData\qSmartTagControlButton.dll

    MD5

    145c6b9290b6cf598f4995a8a70da916

    SHA1

    11186a014fadd68d32a7cd76615c088c1adde213

    SHA256

    770cb2aa5ea76f90e27bc72110b531fa3985ab4352d25362926971285408f148

    SHA512

    849e06ac1b43183b6477c780eab57c15d8e533b14090e3b4c34bfbf26bbee2f54228f3bedab6b799b320acce72ac45bcf074ee8e04962c325d4ab385b7209087

  • \ProgramData\qSmartTagControlButton.dll

    MD5

    145c6b9290b6cf598f4995a8a70da916

    SHA1

    11186a014fadd68d32a7cd76615c088c1adde213

    SHA256

    770cb2aa5ea76f90e27bc72110b531fa3985ab4352d25362926971285408f148

    SHA512

    849e06ac1b43183b6477c780eab57c15d8e533b14090e3b4c34bfbf26bbee2f54228f3bedab6b799b320acce72ac45bcf074ee8e04962c325d4ab385b7209087

  • memory/1212-278-0x0000000000000000-mapping.dmp

  • memory/3348-294-0x0000000000550000-0x0000000000556000-memory.dmp

    Filesize

    24KB

  • memory/3348-292-0x00000000736A0000-0x00000000736D1000-memory.dmp

    Filesize

    196KB

  • memory/3348-290-0x0000000000000000-mapping.dmp

  • memory/3456-288-0x0000000000000000-mapping.dmp

  • memory/3680-123-0x00007FF878B80000-0x00007FF87AA75000-memory.dmp

    Filesize

    31.0MB

  • memory/3680-121-0x00007FF87AA80000-0x00007FF87BB6E000-memory.dmp

    Filesize

    16.9MB

  • memory/3680-114-0x00007FF711840000-0x00007FF714DF6000-memory.dmp

    Filesize

    53.7MB

  • memory/3680-122-0x00007FF85A170000-0x00007FF85A180000-memory.dmp

    Filesize

    64KB

  • memory/3680-118-0x00007FF85A170000-0x00007FF85A180000-memory.dmp

    Filesize

    64KB

  • memory/3680-117-0x00007FF85A170000-0x00007FF85A180000-memory.dmp

    Filesize

    64KB

  • memory/3680-116-0x00007FF85A170000-0x00007FF85A180000-memory.dmp

    Filesize

    64KB

  • memory/3680-115-0x00007FF85A170000-0x00007FF85A180000-memory.dmp

    Filesize

    64KB

  • memory/3680-102439-0x00007FF85A170000-0x00007FF85A180000-memory.dmp

    Filesize

    64KB

  • memory/3680-102443-0x00007FF85A170000-0x00007FF85A180000-memory.dmp

    Filesize

    64KB

  • memory/3680-102441-0x00007FF85A170000-0x00007FF85A180000-memory.dmp

    Filesize

    64KB

  • memory/3680-102445-0x00007FF85A170000-0x00007FF85A180000-memory.dmp

    Filesize

    64KB