Analysis

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

    arch:x64arch:x86image:win10v2004-20240508-enlocale:en-usos:windows10-2004-x64system
  • submitted
    31/05/2024, 02:43

General

  • Target

    LatencyChanger.dll

  • Size

    455KB

  • MD5

    1a56bd3db9987dddd7693535699b4536

  • SHA1

    22b498330b54a4fe25f93ab693e8885ef2c29fb4

  • SHA256

    3aeca5ff03545789e5378583a91d10d0bf407a3a3673a5626663ab700c37876c

  • SHA512

    af058899539916d771c381a31915a3df408a47d848cf64ecb41b33c2e30c9dbcf5963c2c6cd79fadb1482a5f5662f013c29d457bb78a825b9804726db72b0ac1

  • SSDEEP

    6144:rCIQmjW6ZjClnaE8q7fvGH3ZDvYBgu/4zatCN31kmcNMtJSBmCApp6z5EB8nBzW:ZjW6jCl5JfaDvYDwzCC8n6AmCSshBz

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\LatencyChanger.dll,#1
    1⤵
    • Suspicious use of WriteProcessMemory
    PID:3660
    • C:\Windows\SysWOW64\rundll32.exe
      rundll32.exe C:\Users\Admin\AppData\Local\Temp\LatencyChanger.dll,#1
      2⤵
        PID:2424
        • C:\Windows\SysWOW64\WerFault.exe
          C:\Windows\SysWOW64\WerFault.exe -u -p 2424 -s 640
          3⤵
          • Program crash
          PID:448
    • C:\Windows\SysWOW64\WerFault.exe
      C:\Windows\SysWOW64\WerFault.exe -pss -s 416 -p 2424 -ip 2424
      1⤵
        PID:3276

      Network

      MITRE ATT&CK Matrix

      Replay Monitor

      Loading Replay Monitor...

      Downloads

      • memory/2424-2-0x0000000000400000-0x0000000000479000-memory.dmp

        Filesize

        484KB