Analysis

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

    arch:x64arch:x86image:win10v2004-20240508-enlocale:en-usos:windows10-2004-x64system
  • submitted
    11-05-2024 08:05

General

  • Target

    50c24050cc83700989bbb281afd290df47f864702e0a957f1db1800a2c34b25c.exe

  • Size

    1.1MB

  • MD5

    b769c82e7f0aeb48129c514b6ee3eefc

  • SHA1

    19bd8f4cbd6422003331d9d2de11e3a7f973b0a3

  • SHA256

    50c24050cc83700989bbb281afd290df47f864702e0a957f1db1800a2c34b25c

  • SHA512

    97e5b8baf06b6f210cd8e9e8388963ea77b145b0192cb8af8ae7d5b088f0bdba7cedcd5100bdff61d64cb0a85bfbd69115a15e50ce4d0b7c4c43b8586098033d

  • SSDEEP

    24576:tqDEvCTbMWu7rQYlBQcBiT6rprG8aGKSeHIqatQGNQp:tTvC/MTQYxsWR7aGKSeumGy

Score
3/10

Malware Config

Signatures

  • Program crash 1 IoCs
  • Suspicious behavior: MapViewOfSection 1 IoCs
  • Suspicious use of FindShellTrayWindow 4 IoCs
  • Suspicious use of SendNotifyMessage 4 IoCs
  • Suspicious use of WriteProcessMemory 9 IoCs

Processes

  • C:\Users\Admin\AppData\Local\Temp\50c24050cc83700989bbb281afd290df47f864702e0a957f1db1800a2c34b25c.exe
    "C:\Users\Admin\AppData\Local\Temp\50c24050cc83700989bbb281afd290df47f864702e0a957f1db1800a2c34b25c.exe"
    1⤵
    • Suspicious behavior: MapViewOfSection
    • Suspicious use of FindShellTrayWindow
    • Suspicious use of SendNotifyMessage
    • Suspicious use of WriteProcessMemory
    PID:1588
    • C:\Windows\Microsoft.NET\Framework\v4.0.30319\RegSvcs.exe
      "C:\Users\Admin\AppData\Local\Temp\50c24050cc83700989bbb281afd290df47f864702e0a957f1db1800a2c34b25c.exe"
      2⤵
        PID:3516
      • C:\Users\Admin\AppData\Local\Temp\50c24050cc83700989bbb281afd290df47f864702e0a957f1db1800a2c34b25c.exe
        "C:\Users\Admin\AppData\Local\Temp\50c24050cc83700989bbb281afd290df47f864702e0a957f1db1800a2c34b25c.exe"
        2⤵
        • Suspicious use of FindShellTrayWindow
        • Suspicious use of SendNotifyMessage
        • Suspicious use of WriteProcessMemory
        PID:3828
        • C:\Windows\Microsoft.NET\Framework\v4.0.30319\RegSvcs.exe
          "C:\Users\Admin\AppData\Local\Temp\50c24050cc83700989bbb281afd290df47f864702e0a957f1db1800a2c34b25c.exe"
          3⤵
            PID:3776
          • C:\Windows\SysWOW64\WerFault.exe
            C:\Windows\SysWOW64\WerFault.exe -u -p 3828 -s 692
            3⤵
            • Program crash
            PID:2312
      • C:\Windows\SysWOW64\WerFault.exe
        C:\Windows\SysWOW64\WerFault.exe -pss -s 412 -p 3828 -ip 3828
        1⤵
          PID:432

        Network

        MITRE ATT&CK Matrix

        Replay Monitor

        Loading Replay Monitor...

        Downloads

        • C:\Users\Admin\AppData\Local\Temp\nonagglutinant

          Filesize

          28KB

          MD5

          e57eea256683665468bb7fb55f13684d

          SHA1

          083f109a55fe7dd473ac50a1bec85bb608e978b9

          SHA256

          47e48ca5d550c9a4907096eda37d5e648cc0fbdd1b375b9c7c996ab26b41d4b4

          SHA512

          cc20948a5643d8ca466589360d24ea7dff50989ed95880954dd50983e73f362caca1d67eda7908ad62e34520154373ff597a70ce245e4a6259f7ee61eb8e52f8

        • memory/1588-10-0x0000000003D00000-0x0000000003D04000-memory.dmp

          Filesize

          16KB