Analysis

  • max time kernel
    151s
  • max time network
    139s
  • platform
    windows10_x64
  • resource
    win10-en-20211208
  • submitted
    12-01-2022 02:14

General

  • Target

    cce90115dbb29f91192ea44a98616dbd6b6f4a74e76c8eefe004edba731635b7.xlsm

  • Size

    83KB

  • MD5

    3a34a8f95b92bec1e9aefb1235d27dfd

  • SHA1

    5aa96c293a519112b6453657c103add288a84cdf

  • SHA256

    cce90115dbb29f91192ea44a98616dbd6b6f4a74e76c8eefe004edba731635b7

  • SHA512

    dcaaac4a8cbcb8c2472bf015c3da35a3864424f809453fe3340e94e88d9ddeeb2a94321b4edf1ca07637b9ea593546a7b0d66626a588df4ace084afc1ce4fc48

Score
10/10

Malware Config

Extracted

Language
xlm4.0
Source
URLs
xlm40.dropper

http://www.be-pu.com/4.hana/Y1XWpb1zWMRD/

Signatures

  • Process spawned unexpected child process 1 IoCs

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

  • Blocklisted process makes network request 2 IoCs
  • Downloads MZ/PE file
  • Loads dropped DLL 2 IoCs
  • Drops file in System32 directory 1 IoCs
  • Enumerates physical storage devices 1 TTPs

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

  • 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 behavior: EnumeratesProcesses 2 IoCs
  • Suspicious use of SetWindowsHookEx 12 IoCs
  • Suspicious use of WriteProcessMemory 12 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\cce90115dbb29f91192ea44a98616dbd6b6f4a74e76c8eefe004edba731635b7.xlsm"
    1⤵
    • Checks processor information in registry
    • Enumerates system info in registry
    • Suspicious behavior: AddClipboardFormatListener
    • Suspicious use of SetWindowsHookEx
    • Suspicious use of WriteProcessMemory
    PID:2520
    • C:\Windows\SysWow64\rundll32.exe
      C:\Windows\SysWow64\rundll32.exe ..\adi.ocx,D"&"l"&"lR"&"egister"&"Serve"&"r
      2⤵
      • Process spawned unexpected child process
      • Loads dropped DLL
      • Suspicious use of WriteProcessMemory
      PID:1952
      • C:\Windows\SysWOW64\rundll32.exe
        C:\Windows\SysWOW64\rundll32.exe "C:\Users\Admin\adi.ocx",DllRegisterServer
        3⤵
        • Loads dropped DLL
        • Drops file in System32 directory
        • Suspicious use of WriteProcessMemory
        PID:1696
        • C:\Windows\SysWOW64\rundll32.exe
          C:\Windows\SysWOW64\rundll32.exe "C:\Windows\SysWOW64\Yzkcm\igdd.ppg",cUden
          4⤵
          • Suspicious use of WriteProcessMemory
          PID:3384
          • C:\Windows\SysWOW64\rundll32.exe
            C:\Windows\SysWOW64\rundll32.exe "C:\Windows\System32\Yzkcm\igdd.ppg",DllRegisterServer
            5⤵
            • Blocklisted process makes network request
            • Suspicious behavior: EnumeratesProcesses
            PID:1428

Network

MITRE ATT&CK Enterprise v6

Replay Monitor

Loading Replay Monitor...

Downloads

  • C:\Users\Admin\adi.ocx

    MD5

    9c9e8e270fcd7c391bee9b701717aa4d

    SHA1

    fd3a432cd35a16d40b29a2b8582082a2491007fb

    SHA256

    04c64efdba60d0f7439ddd9042c8ff545b95327eda2afc0827b6b273135afdd2

    SHA512

    5ef0ceccef14f4ab07f4e8b2214b2ae56425b2de989fcbe781141edad59b5203a9efeb92e2abc66106d1121a0ea01c2db27f640f63fcfb28dbcaa87e652c5aa5

  • \Users\Admin\adi.ocx

    MD5

    9c9e8e270fcd7c391bee9b701717aa4d

    SHA1

    fd3a432cd35a16d40b29a2b8582082a2491007fb

    SHA256

    04c64efdba60d0f7439ddd9042c8ff545b95327eda2afc0827b6b273135afdd2

    SHA512

    5ef0ceccef14f4ab07f4e8b2214b2ae56425b2de989fcbe781141edad59b5203a9efeb92e2abc66106d1121a0ea01c2db27f640f63fcfb28dbcaa87e652c5aa5

  • \Users\Admin\adi.ocx

    MD5

    9c9e8e270fcd7c391bee9b701717aa4d

    SHA1

    fd3a432cd35a16d40b29a2b8582082a2491007fb

    SHA256

    04c64efdba60d0f7439ddd9042c8ff545b95327eda2afc0827b6b273135afdd2

    SHA512

    5ef0ceccef14f4ab07f4e8b2214b2ae56425b2de989fcbe781141edad59b5203a9efeb92e2abc66106d1121a0ea01c2db27f640f63fcfb28dbcaa87e652c5aa5

  • memory/1428-303-0x0000000000000000-mapping.dmp

  • memory/1696-283-0x0000000000000000-mapping.dmp

  • memory/1952-276-0x0000000000000000-mapping.dmp

  • memory/2520-119-0x00007FF7E0830000-0x00007FF7E0840000-memory.dmp

    Filesize

    64KB

  • memory/2520-122-0x0000019DCF490000-0x0000019DCF492000-memory.dmp

    Filesize

    8KB

  • memory/2520-128-0x00007FF7DCCC0000-0x00007FF7DCCD0000-memory.dmp

    Filesize

    64KB

  • memory/2520-129-0x00007FF7DCCC0000-0x00007FF7DCCD0000-memory.dmp

    Filesize

    64KB

  • memory/2520-143-0x0000019DCF490000-0x0000019DCF492000-memory.dmp

    Filesize

    8KB

  • memory/2520-120-0x0000019DCF490000-0x0000019DCF492000-memory.dmp

    Filesize

    8KB

  • memory/2520-121-0x0000019DCF490000-0x0000019DCF492000-memory.dmp

    Filesize

    8KB

  • memory/2520-115-0x00007FF7E0830000-0x00007FF7E0840000-memory.dmp

    Filesize

    64KB

  • memory/2520-118-0x00007FF7E0830000-0x00007FF7E0840000-memory.dmp

    Filesize

    64KB

  • memory/2520-117-0x00007FF7E0830000-0x00007FF7E0840000-memory.dmp

    Filesize

    64KB

  • memory/2520-116-0x00007FF7E0830000-0x00007FF7E0840000-memory.dmp

    Filesize

    64KB

  • memory/3384-298-0x0000000000000000-mapping.dmp