Windows 7 deprecation

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

Analysis

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

    arch:x64arch:x86image:win10v2004-20220812-enlocale:en-usos:windows10-2004-x64system
  • submitted
    13/09/2022, 08:07

General

  • Target

    ab5d945f0df0849eb41dbde76e3bc7e87f7fed10b0a5bbfa39f6973e6340a79d.exe

  • Size

    1.8MB

  • MD5

    16c48b6dc49a4e8d275c549df911b520

  • SHA1

    1a56cec1493a8e20c497d04d7e406a8fe8cab9f1

  • SHA256

    ab5d945f0df0849eb41dbde76e3bc7e87f7fed10b0a5bbfa39f6973e6340a79d

  • SHA512

    04c3c8a28725dbf747dd9ece995201cbc102b705e78edeecafb7d017c889de2d1f383f3bde1a8f8ccda72a2e19fcb13e8ddb50189ca50b2aec64337611ee3650

  • 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\ab5d945f0df0849eb41dbde76e3bc7e87f7fed10b0a5bbfa39f6973e6340a79d.exe
    "C:\Users\Admin\AppData\Local\Temp\ab5d945f0df0849eb41dbde76e3bc7e87f7fed10b0a5bbfa39f6973e6340a79d.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:5012
    • 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:4916
  • 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:1916
    • 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:2072

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

    16c48b6dc49a4e8d275c549df911b520

    SHA1

    1a56cec1493a8e20c497d04d7e406a8fe8cab9f1

    SHA256

    ab5d945f0df0849eb41dbde76e3bc7e87f7fed10b0a5bbfa39f6973e6340a79d

    SHA512

    04c3c8a28725dbf747dd9ece995201cbc102b705e78edeecafb7d017c889de2d1f383f3bde1a8f8ccda72a2e19fcb13e8ddb50189ca50b2aec64337611ee3650

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

    Filesize

    1.8MB

    MD5

    16c48b6dc49a4e8d275c549df911b520

    SHA1

    1a56cec1493a8e20c497d04d7e406a8fe8cab9f1

    SHA256

    ab5d945f0df0849eb41dbde76e3bc7e87f7fed10b0a5bbfa39f6973e6340a79d

    SHA512

    04c3c8a28725dbf747dd9ece995201cbc102b705e78edeecafb7d017c889de2d1f383f3bde1a8f8ccda72a2e19fcb13e8ddb50189ca50b2aec64337611ee3650

  • memory/1916-151-0x00000000000C0000-0x00000000003DF000-memory.dmp

    Filesize

    3.1MB

  • memory/1916-148-0x00000000000C1000-0x00000000000C3000-memory.dmp

    Filesize

    8KB

  • memory/1916-156-0x00000000000C0000-0x00000000003DF000-memory.dmp

    Filesize

    3.1MB

  • memory/1916-155-0x00000000000C0000-0x00000000003DF000-memory.dmp

    Filesize

    3.1MB

  • memory/1916-154-0x0000000000A20000-0x0000000000A64000-memory.dmp

    Filesize

    272KB

  • memory/1916-144-0x00000000000C0000-0x00000000003DF000-memory.dmp

    Filesize

    3.1MB

  • memory/1916-153-0x00000000000C0000-0x00000000003DF000-memory.dmp

    Filesize

    3.1MB

  • memory/1916-152-0x0000000077E30000-0x0000000077FD3000-memory.dmp

    Filesize

    1.6MB

  • memory/1916-146-0x0000000000A20000-0x0000000000A64000-memory.dmp

    Filesize

    272KB

  • memory/1916-150-0x00000000000C0000-0x00000000003DF000-memory.dmp

    Filesize

    3.1MB

  • memory/1916-145-0x00000000000C0000-0x00000000003DF000-memory.dmp

    Filesize

    3.1MB

  • memory/5012-139-0x0000000000D70000-0x000000000108F000-memory.dmp

    Filesize

    3.1MB

  • memory/5012-134-0x0000000000D70000-0x000000000108F000-memory.dmp

    Filesize

    3.1MB

  • memory/5012-135-0x0000000000D70000-0x000000000108F000-memory.dmp

    Filesize

    3.1MB

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

    Filesize

    3.1MB

  • memory/5012-133-0x00000000009B0000-0x00000000009F4000-memory.dmp

    Filesize

    272KB

  • memory/5012-141-0x0000000077E30000-0x0000000077FD3000-memory.dmp

    Filesize

    1.6MB

  • memory/5012-140-0x00000000009B0000-0x00000000009F4000-memory.dmp

    Filesize

    272KB

  • memory/5012-137-0x0000000000D71000-0x0000000000D73000-memory.dmp

    Filesize

    8KB

  • memory/5012-136-0x0000000000D71000-0x0000000000D73000-memory.dmp

    Filesize

    8KB