Analysis

  • max time kernel
    151s
  • max time network
    134s
  • platform
    windows10_x64
  • resource
    win10-en-20211208
  • submitted
    13-01-2022 22:28

General

  • Target

    096504811c78492132ac12b84ad2a6ee435ac882bd0a59bed69a1b10775edf37.xlsm

  • Size

    83KB

  • MD5

    5683076d4912043d209e4456df72457c

  • SHA1

    2176256f3f12b3b3252334f58c656123a9d95178

  • SHA256

    096504811c78492132ac12b84ad2a6ee435ac882bd0a59bed69a1b10775edf37

  • SHA512

    ecec970884e861525a48fec9d50cf2d159e4aa81c382dce7a1903201e427f7ff4e1f3a909268c39e95f43f9f01e62f6721987d17664929e34c3df3df2e5e29ba

Score
10/10

Malware Config

Extracted

Language
xlm4.0
Source
URLs
xlm40.dropper

http://robotically.xyz/wp-content/XtKkx/

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\096504811c78492132ac12b84ad2a6ee435ac882bd0a59bed69a1b10775edf37.xlsm"
    1⤵
    • Checks processor information in registry
    • Enumerates system info in registry
    • Suspicious behavior: AddClipboardFormatListener
    • Suspicious use of SetWindowsHookEx
    • Suspicious use of WriteProcessMemory
    PID:4092
    • C:\Windows\SysWow64\rundll32.exe
      C:\Windows\SysWow64\rundll32.exe ..\wxeu.ocx,D"&"l"&"lR"&"egister"&"Serve"&"r
      2⤵
      • Process spawned unexpected child process
      • Loads dropped DLL
      • Suspicious use of WriteProcessMemory
      PID:2392
      • C:\Windows\SysWOW64\rundll32.exe
        C:\Windows\SysWOW64\rundll32.exe "C:\Users\Admin\wxeu.ocx",DllRegisterServer
        3⤵
        • Loads dropped DLL
        • Drops file in System32 directory
        • Suspicious use of WriteProcessMemory
        PID:3064
        • C:\Windows\SysWOW64\rundll32.exe
          C:\Windows\SysWOW64\rundll32.exe "C:\Windows\SysWOW64\Dtapzjpori\fujcdterjgtqlrp.pxw",hdTbPDqrhxMg
          4⤵
          • Suspicious use of WriteProcessMemory
          PID:3228
          • C:\Windows\SysWOW64\rundll32.exe
            C:\Windows\SysWOW64\rundll32.exe "C:\Windows\System32\Dtapzjpori\fujcdterjgtqlrp.pxw",DllRegisterServer
            5⤵
            • Blocklisted process makes network request
            • Suspicious behavior: EnumeratesProcesses
            PID:8

Network

MITRE ATT&CK Enterprise v6

Replay Monitor

Loading Replay Monitor...

Downloads

  • memory/4092-118-0x00007FF969B20000-0x00007FF969B30000-memory.dmp

    Filesize

    64KB

  • memory/4092-127-0x00007FF969B20000-0x00007FF969B30000-memory.dmp

    Filesize

    64KB

  • memory/4092-121-0x0000029824260000-0x0000029824262000-memory.dmp

    Filesize

    8KB

  • memory/4092-120-0x0000029824260000-0x0000029824262000-memory.dmp

    Filesize

    8KB

  • memory/4092-119-0x0000029824260000-0x0000029824262000-memory.dmp

    Filesize

    8KB

  • memory/4092-115-0x00007FF969B20000-0x00007FF969B30000-memory.dmp

    Filesize

    64KB

  • memory/4092-117-0x00007FF969B20000-0x00007FF969B30000-memory.dmp

    Filesize

    64KB

  • memory/4092-116-0x00007FF969B20000-0x00007FF969B30000-memory.dmp

    Filesize

    64KB