Windows 7 deprecation

Windows 7 will be removed from tria.ge on 2025-03-31

Analysis

  • max time kernel
    91s
  • max time network
    150s
  • platform
    windows10-2004_x64
  • resource
    win10v2004-20220812-en
  • resource tags

    arch:x64arch:x86image:win10v2004-20220812-enlocale:en-usos:windows10-2004-x64system
  • submitted
    29/09/2022, 14:49

General

  • Target

    47483d0595f7eb01236b2d68240d80a0712368e0ebbebad938f744546c5a989c.exe

  • Size

    1.8MB

  • MD5

    e27dbc7153904f186e97799eee0c28df

  • SHA1

    cd196da7b28c5d3aa921c461c892d9505bdaf31e

  • SHA256

    47483d0595f7eb01236b2d68240d80a0712368e0ebbebad938f744546c5a989c

  • SHA512

    778159eba87f446a6eb48faeaf02b08d9d8516d5baf5dd022b8f2705c4e444ff6e53a1b7c5a30df64a93e2738ef86a02e087628932d9b3892c1ac21a6d2111b7

  • SSDEEP

    49152:AiSzCD+K95aLs7zeqLTVtXtHFIDP8EehiM8qZA:AiSzCD+K95aUeqFtXtHwEEehig

Score
9/10

Malware Config

Signatures

  • Identifies VirtualBox via ACPI registry values (likely anti-VM) 2 TTPs 2 IoCs
  • Executes dropped EXE 1 IoCs
  • Checks BIOS information in registry 2 TTPs 4 IoCs

    BIOS information is often read in order to detect sandboxing environments.

  • Checks whether UAC is enabled 1 TTPs 2 IoCs
  • Suspicious use of NtSetInformationThreadHideFromDebugger 4 IoCs
  • Creates scheduled task(s) 1 TTPs 2 IoCs

    Schtasks is often used by malware for persistence or to perform post-infection execution.

  • Suspicious behavior: EnumeratesProcesses 8 IoCs
  • Suspicious use of WriteProcessMemory 6 IoCs

Processes

  • C:\Users\Admin\AppData\Local\Temp\47483d0595f7eb01236b2d68240d80a0712368e0ebbebad938f744546c5a989c.exe
    "C:\Users\Admin\AppData\Local\Temp\47483d0595f7eb01236b2d68240d80a0712368e0ebbebad938f744546c5a989c.exe"
    1⤵
    • Identifies VirtualBox via ACPI registry values (likely anti-VM)
    • Checks BIOS information in registry
    • Checks whether UAC is enabled
    • Suspicious use of NtSetInformationThreadHideFromDebugger
    • Suspicious behavior: EnumeratesProcesses
    • Suspicious use of WriteProcessMemory
    PID:1192
    • C:\Windows\SysWOW64\schtasks.exe
      /C /create /F /sc minute /mo 1 /tn "Telemetry Logging" /tr "C:\Users\Admin\AppData\Roaming\Microsoft\Protect\oobeldr.exe"
      2⤵
      • Creates scheduled task(s)
      PID:2824
  • C:\Users\Admin\AppData\Roaming\Microsoft\Protect\oobeldr.exe
    C:\Users\Admin\AppData\Roaming\Microsoft\Protect\oobeldr.exe
    1⤵
    • Identifies VirtualBox via ACPI registry values (likely anti-VM)
    • Executes dropped EXE
    • Checks BIOS information in registry
    • Checks whether UAC is enabled
    • Suspicious use of NtSetInformationThreadHideFromDebugger
    • Suspicious behavior: EnumeratesProcesses
    • Suspicious use of WriteProcessMemory
    PID:2100
    • C:\Windows\SysWOW64\schtasks.exe
      /C /create /F /sc minute /mo 1 /tn "Telemetry Logging" /tr "C:\Users\Admin\AppData\Roaming\Microsoft\Protect\oobeldr.exe"
      2⤵
      • Creates scheduled task(s)
      PID:3136

Network

MITRE ATT&CK Enterprise v6

Replay Monitor

Loading Replay Monitor...

Downloads

  • C:\Users\Admin\AppData\Roaming\Microsoft\Protect\oobeldr.exe

    Filesize

    1.8MB

    MD5

    e27dbc7153904f186e97799eee0c28df

    SHA1

    cd196da7b28c5d3aa921c461c892d9505bdaf31e

    SHA256

    47483d0595f7eb01236b2d68240d80a0712368e0ebbebad938f744546c5a989c

    SHA512

    778159eba87f446a6eb48faeaf02b08d9d8516d5baf5dd022b8f2705c4e444ff6e53a1b7c5a30df64a93e2738ef86a02e087628932d9b3892c1ac21a6d2111b7

  • C:\Users\Admin\AppData\Roaming\Microsoft\Protect\oobeldr.exe

    Filesize

    1.8MB

    MD5

    e27dbc7153904f186e97799eee0c28df

    SHA1

    cd196da7b28c5d3aa921c461c892d9505bdaf31e

    SHA256

    47483d0595f7eb01236b2d68240d80a0712368e0ebbebad938f744546c5a989c

    SHA512

    778159eba87f446a6eb48faeaf02b08d9d8516d5baf5dd022b8f2705c4e444ff6e53a1b7c5a30df64a93e2738ef86a02e087628932d9b3892c1ac21a6d2111b7

  • memory/1192-133-0x0000000000D71000-0x0000000000D73000-memory.dmp

    Filesize

    8KB

  • memory/1192-134-0x0000000000D71000-0x0000000000D73000-memory.dmp

    Filesize

    8KB

  • memory/1192-132-0x0000000000D70000-0x000000000108F000-memory.dmp

    Filesize

    3.1MB

  • memory/1192-136-0x0000000000D70000-0x000000000108F000-memory.dmp

    Filesize

    3.1MB

  • memory/1192-137-0x0000000002B90000-0x0000000002BD4000-memory.dmp

    Filesize

    272KB

  • memory/1192-138-0x0000000000D70000-0x000000000108F000-memory.dmp

    Filesize

    3.1MB

  • memory/1192-139-0x0000000077A20000-0x0000000077BC3000-memory.dmp

    Filesize

    1.6MB

  • memory/1192-140-0x0000000000D70000-0x000000000108F000-memory.dmp

    Filesize

    3.1MB

  • memory/1192-141-0x0000000077A20000-0x0000000077BC3000-memory.dmp

    Filesize

    1.6MB

  • memory/2100-144-0x0000000000980000-0x0000000000C9F000-memory.dmp

    Filesize

    3.1MB

  • memory/2100-151-0x0000000000980000-0x0000000000C9F000-memory.dmp

    Filesize

    3.1MB

  • memory/2100-145-0x00000000008F0000-0x0000000000934000-memory.dmp

    Filesize

    272KB

  • memory/2100-146-0x0000000000980000-0x0000000000C9F000-memory.dmp

    Filesize

    3.1MB

  • memory/2100-147-0x0000000000980000-0x0000000000C9F000-memory.dmp

    Filesize

    3.1MB

  • memory/2100-149-0x0000000000981000-0x0000000000983000-memory.dmp

    Filesize

    8KB

  • memory/2100-157-0x0000000000980000-0x0000000000C9F000-memory.dmp

    Filesize

    3.1MB

  • memory/2100-156-0x0000000000980000-0x0000000000C9F000-memory.dmp

    Filesize

    3.1MB

  • memory/2100-152-0x0000000077A20000-0x0000000077BC3000-memory.dmp

    Filesize

    1.6MB

  • memory/2100-153-0x0000000000980000-0x0000000000C9F000-memory.dmp

    Filesize

    3.1MB

  • memory/2100-154-0x00000000008F0000-0x0000000000934000-memory.dmp

    Filesize

    272KB

  • memory/2100-155-0x0000000000980000-0x0000000000C9F000-memory.dmp

    Filesize

    3.1MB