Analysis

  • max time kernel
    144s
  • max time network
    169s
  • platform
    windows10-2004_x64
  • resource
    win10v2004-20231215-en
  • resource tags

    arch:x64arch:x86image:win10v2004-20231215-enlocale:en-usos:windows10-2004-x64system
  • submitted
    05-01-2024 05:40

General

  • Target

    2024-01-01_3004525c1952c89dcdfe3b7143cd1ff4_virlock.exe

  • Size

    110KB

  • MD5

    3004525c1952c89dcdfe3b7143cd1ff4

  • SHA1

    4d110ecb75b5c8e7fe0bfc9ce3bb247935b126dd

  • SHA256

    4aff22dbbb4dd3e6ef3d4fbfa6c676a8e2d66bf67981663ca750bc6deae6f429

  • SHA512

    cbd3a88e3ea763b9bed4bb5f9bde129ec7fbc4712a5ad1a1a3392bb6e575aa00ba2e00fc03ae26084a8b8d9fb368aecc420ee55e7b4eeeb2dda8bff30765eed2

  • SSDEEP

    1536:x4VUq1+lIMTbGU0SZWvZyaNaTq30nm5+wf3F++tAE9hPToQBboWEJUgp1SIgCM:x+V8+gZm1aq0nfw+A9hPTDi32Ig

Score
3/10

Malware Config

Signatures

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

Processes

  • C:\Users\Admin\AppData\Local\Temp\2024-01-01_3004525c1952c89dcdfe3b7143cd1ff4_virlock.exe
    "C:\Users\Admin\AppData\Local\Temp\2024-01-01_3004525c1952c89dcdfe3b7143cd1ff4_virlock.exe"
    1⤵
    • Suspicious use of WriteProcessMemory
    PID:3992
    • C:\Windows\SysWOW64\WerFault.exe
      C:\Windows\SysWOW64\WerFault.exe -u -p 3992 -s 224
      2⤵
      • Program crash
      PID:1856
    • C:\Windows\SysWOW64\WerFault.exe
      C:\Windows\SysWOW64\WerFault.exe -u -p 3992 -s 224
      2⤵
      • Program crash
      PID:4784
  • C:\Windows\SysWOW64\WerFault.exe
    C:\Windows\SysWOW64\WerFault.exe -pss -s 424 -p 3992 -ip 3992
    1⤵
      PID:3420

    Network

    MITRE ATT&CK Matrix

    Replay Monitor

    Loading Replay Monitor...

    Downloads

    • memory/3992-0-0x0000000000400000-0x000000000041D000-memory.dmp

      Filesize

      116KB

    • memory/3992-1-0x0000000000400000-0x000000000041D000-memory.dmp

      Filesize

      116KB