Windows 7 deprecation

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

Analysis

  • max time kernel
    84s
  • max time network
    126s
  • platform
    windows10-2004_x64
  • resource
    win10v2004-20220901-en
  • resource tags

    arch:x64arch:x86image:win10v2004-20220901-enlocale:en-usos:windows10-2004-x64system
  • submitted
    17/09/2022, 21:37

General

  • Target

    6230ea90a0e229223796cc79715e39c3fa29e6be888b1ded9144780be61c8e5c.exe

  • Size

    1.8MB

  • MD5

    5fab6ef6bad8849edb6a3e92dc84e4b4

  • SHA1

    e2ef66e264b9b02f062a7558aef572b73a958f6e

  • SHA256

    6230ea90a0e229223796cc79715e39c3fa29e6be888b1ded9144780be61c8e5c

  • SHA512

    c6eb065055222effec8333664ee5a67a52961d713b664aa1dd4348cc6d26e8a084b770d2c32ce27a0836a2855fcf41da4d65324b79155c628d74b569e310ff4f

  • 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\6230ea90a0e229223796cc79715e39c3fa29e6be888b1ded9144780be61c8e5c.exe
    "C:\Users\Admin\AppData\Local\Temp\6230ea90a0e229223796cc79715e39c3fa29e6be888b1ded9144780be61c8e5c.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:2332
    • 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:1096
  • 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:1236
    • 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:1960

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

    5fab6ef6bad8849edb6a3e92dc84e4b4

    SHA1

    e2ef66e264b9b02f062a7558aef572b73a958f6e

    SHA256

    6230ea90a0e229223796cc79715e39c3fa29e6be888b1ded9144780be61c8e5c

    SHA512

    c6eb065055222effec8333664ee5a67a52961d713b664aa1dd4348cc6d26e8a084b770d2c32ce27a0836a2855fcf41da4d65324b79155c628d74b569e310ff4f

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

    Filesize

    1.8MB

    MD5

    5fab6ef6bad8849edb6a3e92dc84e4b4

    SHA1

    e2ef66e264b9b02f062a7558aef572b73a958f6e

    SHA256

    6230ea90a0e229223796cc79715e39c3fa29e6be888b1ded9144780be61c8e5c

    SHA512

    c6eb065055222effec8333664ee5a67a52961d713b664aa1dd4348cc6d26e8a084b770d2c32ce27a0836a2855fcf41da4d65324b79155c628d74b569e310ff4f

  • memory/1236-151-0x0000000000FA0000-0x0000000000FE4000-memory.dmp

    Filesize

    272KB

  • memory/1236-145-0x0000000000330000-0x000000000064F000-memory.dmp

    Filesize

    3.1MB

  • memory/1236-150-0x0000000077C70000-0x0000000077E13000-memory.dmp

    Filesize

    1.6MB

  • memory/1236-149-0x0000000000330000-0x000000000064F000-memory.dmp

    Filesize

    3.1MB

  • memory/1236-147-0x0000000000331000-0x0000000000333000-memory.dmp

    Filesize

    8KB

  • memory/1236-152-0x0000000000330000-0x000000000064F000-memory.dmp

    Filesize

    3.1MB

  • memory/1236-153-0x0000000000330000-0x000000000064F000-memory.dmp

    Filesize

    3.1MB

  • memory/1236-142-0x0000000000330000-0x000000000064F000-memory.dmp

    Filesize

    3.1MB

  • memory/1236-143-0x0000000000FA0000-0x0000000000FE4000-memory.dmp

    Filesize

    272KB

  • memory/1236-144-0x0000000000330000-0x000000000064F000-memory.dmp

    Filesize

    3.1MB

  • memory/2332-139-0x0000000077C70000-0x0000000077E13000-memory.dmp

    Filesize

    1.6MB

  • memory/2332-132-0x00000000009F0000-0x0000000000D0F000-memory.dmp

    Filesize

    3.1MB

  • memory/2332-138-0x00000000009F0000-0x0000000000D0F000-memory.dmp

    Filesize

    3.1MB

  • memory/2332-137-0x0000000002E80000-0x0000000002EC4000-memory.dmp

    Filesize

    272KB

  • memory/2332-135-0x00000000009F1000-0x00000000009F3000-memory.dmp

    Filesize

    8KB

  • memory/2332-134-0x00000000009F1000-0x00000000009F3000-memory.dmp

    Filesize

    8KB

  • memory/2332-133-0x00000000009F0000-0x0000000000D0F000-memory.dmp

    Filesize

    3.1MB