Analysis

  • max time kernel
    148s
  • max time network
    152s
  • platform
    windows10-2004_x64
  • resource
    win10v2004-20240508-en
  • resource tags

    arch:x64arch:x86image:win10v2004-20240508-enlocale:en-usos:windows10-2004-x64system
  • submitted
    24-05-2024 16:07

General

  • Target

    libassuan-0.dll

  • Size

    77KB

  • MD5

    baf6dcfd5eb06852939681f5209e9cdb

  • SHA1

    36c6eb5e401d2c21fcbcb7bf833a41422e668469

  • SHA256

    fc7a9a77d6bccb993185ebc71e8d223e698132f761aec65ab7590a7f028fb90b

  • SHA512

    4bab1bad23df95c520dc40f6ccf9f11974aa895f0cfe7c9fb320caad5a2237aca695d23d0a06195325c4c3e19dc75d5aec7ee34a36bd7839a9c79bf3bdf95853

  • SSDEEP

    1536:Atznsf5Dko+qtyNMoj6LXaq+FjCrBCBxYfJjvlbN+AL:AFgk0eMm62dcrBCvYfJlbNZ

Score
3/10

Malware Config

Signatures

  • Program crash 1 IoCs
  • Suspicious use of WriteProcessMemory 3 IoCs

Processes

  • C:\Windows\system32\rundll32.exe
    rundll32.exe C:\Users\Admin\AppData\Local\Temp\libassuan-0.dll,#1
    1⤵
    • Suspicious use of WriteProcessMemory
    PID:3036
    • C:\Windows\SysWOW64\rundll32.exe
      rundll32.exe C:\Users\Admin\AppData\Local\Temp\libassuan-0.dll,#1
      2⤵
        PID:5032
        • C:\Windows\SysWOW64\WerFault.exe
          C:\Windows\SysWOW64\WerFault.exe -u -p 5032 -s 628
          3⤵
          • Program crash
          PID:3988
    • C:\Windows\SysWOW64\WerFault.exe
      C:\Windows\SysWOW64\WerFault.exe -pss -s 184 -p 5032 -ip 5032
      1⤵
        PID:1136

      Network

      MITRE ATT&CK Matrix

      Replay Monitor

      Loading Replay Monitor...

      Downloads

      • memory/5032-1-0x000000006B480000-0x000000006B4AF000-memory.dmp
        Filesize

        188KB

      • memory/5032-0-0x0000000065A80000-0x0000000065A99000-memory.dmp
        Filesize

        100KB