Analysis

  • max time kernel
    150s
  • max time network
    149s
  • platform
    windows10_x64
  • resource
    win10v20210410
  • submitted
    27-07-2021 08:47

General

  • Target

    Invoice_115952(1).xlsm

  • Size

    328KB

  • MD5

    4dfc77e45068635df70a32fd5bcdeb01

  • SHA1

    01e6f96db1fc9adfb6ef49beed0abaf6a12eab3a

  • SHA256

    cdc866753e7d7865e67e31047a60468f6c7eb80290df4c4e16d3697eb8db12b6

  • SHA512

    ab835a2bfe72e82dafd3abb27521484c901f94114c493bcd47b7e295a6ccffb67cb2aeab9ee892d6b9dee46e17cf77b57080ed173d9e17dd893cb4ef72607ce0

Malware Config

Extracted

Family

dridex

Botnet

22202

C2

45.79.33.48:443

139.162.202.74:5007

68.183.216.174:7443

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 FindShellTrayWindow 2 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\Invoice_115952(1).xlsm"
    1⤵
    • Checks processor information in registry
    • Enumerates system info in registry
    • Suspicious behavior: AddClipboardFormatListener
    • Suspicious use of FindShellTrayWindow
    • Suspicious use of SetWindowsHookEx
    • Suspicious use of WriteProcessMemory
    PID:3944
    • C:\Windows\SYSTEM32\mshta.exe
      mshta C:\ProgramData//theListDataTypeCounter.sct
      2⤵
      • Process spawned unexpected child process
      • Blocklisted process makes network request
      • Suspicious use of WriteProcessMemory
      PID:3760
      • C:\Windows\SYSTEM32\rundll32.exe
        rundll32.exe C:\ProgramData\qTransparent.dll,AddLookaside
        3⤵
        • Suspicious use of WriteProcessMemory
        PID:2144
        • C:\Windows\SysWOW64\rundll32.exe
          rundll32.exe C:\ProgramData\qTransparent.dll,AddLookaside
          4⤵
          • Loads dropped DLL
          • Checks whether UAC is enabled
          PID:3964

Network

MITRE ATT&CK Matrix ATT&CK v6

Discovery

System Information Discovery

3
T1082

Query Registry

2
T1012

Replay Monitor

Loading Replay Monitor...

Downloads

  • C:\ProgramData\qTransparent.dll
    MD5

    67071ed11a700b61671279a7992a6c78

    SHA1

    2d40f919a8068b2144720a9f335916faca889eec

    SHA256

    4b120f29271c702c4825fcf99295dc96eb975f4176291010af948b552ab5739f

    SHA512

    1950ad3e7f6d5d7f4d6269693a85b32d953e2107bc308f56c07d2a0a26dc2e1ee4606de14fd365296d6332d0fa9395316b21bc5c10d1653a8447665f4b3e6961

  • C:\ProgramData\theListDataTypeCounter.sct
    MD5

    cc6c35ff269c0955f69338abc3e34caa

    SHA1

    f0be5b47ed1d39e3566b15c0f827e5c934d93989

    SHA256

    2e00bea733bbb04645ba8ac06fa5e3f1dd0dc206ca86d9eb5915a1fc86781fc9

    SHA512

    f77955b116f085dbfc8f61568e3a3307599f98a1b2e349742bb62970f65f1443ddf00c231ee6751a63c3253e8ec2edbd5fafec5a9932e0cd46dca581843b105c

  • \ProgramData\qTransparent.dll
    MD5

    67071ed11a700b61671279a7992a6c78

    SHA1

    2d40f919a8068b2144720a9f335916faca889eec

    SHA256

    4b120f29271c702c4825fcf99295dc96eb975f4176291010af948b552ab5739f

    SHA512

    1950ad3e7f6d5d7f4d6269693a85b32d953e2107bc308f56c07d2a0a26dc2e1ee4606de14fd365296d6332d0fa9395316b21bc5c10d1653a8447665f4b3e6961

  • memory/2144-271-0x0000000000000000-mapping.dmp
  • memory/3760-261-0x0000000000000000-mapping.dmp
  • memory/3944-121-0x00007FFDF5C60000-0x00007FFDF5C70000-memory.dmp
    Filesize

    64KB

  • memory/3944-103671-0x00007FFDF5C60000-0x00007FFDF5C70000-memory.dmp
    Filesize

    64KB

  • memory/3944-123-0x00000207F68C0000-0x00000207F87B5000-memory.dmp
    Filesize

    31.0MB

  • memory/3944-114-0x00007FF715280000-0x00007FF718836000-memory.dmp
    Filesize

    53.7MB

  • memory/3944-118-0x00007FFDF5C60000-0x00007FFDF5C70000-memory.dmp
    Filesize

    64KB

  • memory/3944-117-0x00007FFDF5C60000-0x00007FFDF5C70000-memory.dmp
    Filesize

    64KB

  • memory/3944-116-0x00007FFDF5C60000-0x00007FFDF5C70000-memory.dmp
    Filesize

    64KB

  • memory/3944-122-0x00007FFE15FE0000-0x00007FFE170CE000-memory.dmp
    Filesize

    16.9MB

  • memory/3944-115-0x00007FFDF5C60000-0x00007FFDF5C70000-memory.dmp
    Filesize

    64KB

  • memory/3944-103673-0x00007FFDF5C60000-0x00007FFDF5C70000-memory.dmp
    Filesize

    64KB

  • memory/3944-103669-0x00007FFDF5C60000-0x00007FFDF5C70000-memory.dmp
    Filesize

    64KB

  • memory/3944-103667-0x00007FFDF5C60000-0x00007FFDF5C70000-memory.dmp
    Filesize

    64KB

  • memory/3964-273-0x0000000000000000-mapping.dmp
  • memory/3964-277-0x00000000004F0000-0x00000000004F6000-memory.dmp
    Filesize

    24KB

  • memory/3964-275-0x0000000073DE0000-0x0000000073E10000-memory.dmp
    Filesize

    192KB