Analysis

  • max time kernel
    341s
  • max time network
    354s
  • platform
    windows10-2004_x64
  • resource
    win10v2004-20221111-en
  • resource tags

    arch:x64arch:x86image:win10v2004-20221111-enlocale:en-usos:windows10-2004-x64system
  • submitted
    24-11-2022 00:20

General

  • Target

    25fb21634f150c2abb2c490194ac63c7456614950dfe59c919e0618a67b02e17.exe

  • Size

    176KB

  • MD5

    1adbb031674677b2525a3a79b630dfe0

  • SHA1

    c072eca7b6bbcb43ee99369c19f0fbb4a9be67e5

  • SHA256

    25fb21634f150c2abb2c490194ac63c7456614950dfe59c919e0618a67b02e17

  • SHA512

    aa99c685515cb454df622cc1f9ed9e5fe918dd5985d69b81b838454c12424e418b6968174faa6c13223124422df4664c99eb0ce425abdad2bc509001bae71ad0

  • SSDEEP

    3072:OxE/8zlh4GWtPuCaAYmG5bcFuKnvmb7/D26inavm4QLzHpXP6D8R8FOjcKvDHmBR:GU8zAGWtPuCaVmG5bnKnvmb7/D26caea

Score
10/10

Malware Config

Signatures

  • Modifies visiblity of hidden/system files in Explorer 2 TTPs 2 IoCs
  • Executes dropped EXE 1 IoCs
  • Checks computer location settings 2 TTPs 1 IoCs

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

  • Adds Run key to start application 2 TTPs 4 IoCs
  • Enumerates physical storage devices 1 TTPs

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

  • Program crash 4 IoCs
  • Suspicious use of SetWindowsHookEx 2 IoCs
  • Suspicious use of WriteProcessMemory 9 IoCs

Processes

  • C:\Users\Admin\AppData\Local\Temp\25fb21634f150c2abb2c490194ac63c7456614950dfe59c919e0618a67b02e17.exe
    "C:\Users\Admin\AppData\Local\Temp\25fb21634f150c2abb2c490194ac63c7456614950dfe59c919e0618a67b02e17.exe"
    1⤵
    • Modifies visiblity of hidden/system files in Explorer
    • Checks computer location settings
    • Adds Run key to start application
    • Suspicious use of SetWindowsHookEx
    • Suspicious use of WriteProcessMemory
    PID:4460
    • C:\Users\Admin\ziaedec.exe
      "C:\Users\Admin\ziaedec.exe"
      2⤵
      • Modifies visiblity of hidden/system files in Explorer
      • Executes dropped EXE
      • Adds Run key to start application
      • Suspicious use of SetWindowsHookEx
      • Suspicious use of WriteProcessMemory
      PID:4848
      • C:\Windows\SysWOW64\WerFault.exe
        C:\Windows\SysWOW64\WerFault.exe -u -p 4848 -s 668
        3⤵
        • Program crash
        PID:4496
      • C:\Windows\SysWOW64\WerFault.exe
        C:\Windows\SysWOW64\WerFault.exe -u -p 4848 -s 668
        3⤵
        • Program crash
        PID:2652
    • C:\Windows\SysWOW64\WerFault.exe
      C:\Windows\SysWOW64\WerFault.exe -u -p 4460 -s 928
      2⤵
      • Program crash
      PID:4584
    • C:\Windows\SysWOW64\WerFault.exe
      C:\Windows\SysWOW64\WerFault.exe -u -p 4460 -s 928
      2⤵
      • Program crash
      PID:2076
  • C:\Windows\SysWOW64\WerFault.exe
    C:\Windows\SysWOW64\WerFault.exe -pss -s 408 -p 4460 -ip 4460
    1⤵
      PID:4960
    • C:\Windows\SysWOW64\WerFault.exe
      C:\Windows\SysWOW64\WerFault.exe -pss -s 464 -p 4848 -ip 4848
      1⤵
        PID:4184

      Network

      MITRE ATT&CK Enterprise v6

      Replay Monitor

      Loading Replay Monitor...

      Downloads

      • C:\Users\Admin\ziaedec.exe

        Filesize

        176KB

        MD5

        a917d347d7982af07716177bec5f4973

        SHA1

        4c63d41717a30e6fece7e4e2653cb6e215c413f2

        SHA256

        ba04d712cb409c3a060b4c8503dd104ecd4c0ec9bb9d1dab51e27d86aab90d93

        SHA512

        8c1187186e264e5b1afde0f9a277955086cf5504c9ea3021cd539c37f0dab43d899da5f4e68eeedd180207e7f13f0fd039b88a8c889133d9c17d7a6098ca3b40

      • C:\Users\Admin\ziaedec.exe

        Filesize

        176KB

        MD5

        a917d347d7982af07716177bec5f4973

        SHA1

        4c63d41717a30e6fece7e4e2653cb6e215c413f2

        SHA256

        ba04d712cb409c3a060b4c8503dd104ecd4c0ec9bb9d1dab51e27d86aab90d93

        SHA512

        8c1187186e264e5b1afde0f9a277955086cf5504c9ea3021cd539c37f0dab43d899da5f4e68eeedd180207e7f13f0fd039b88a8c889133d9c17d7a6098ca3b40

      • memory/4496-140-0x0000000000000000-mapping.dmp

      • memory/4584-139-0x0000000000000000-mapping.dmp

      • memory/4848-134-0x0000000000000000-mapping.dmp