Windows 7 deprecation

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

Analysis

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

    arch:x64arch:x86image:win10v2004-20220812-enlocale:en-usos:windows10-2004-x64system
  • submitted
    18/09/2022, 05:44

General

  • Target

    db7a7c02c22154620f35881e0f55e936567deaddc98feae2de11443280e1b894.exe

  • Size

    1.8MB

  • MD5

    1055cacb496519b2beca1c0f53638ef3

  • SHA1

    2c5325ff7b4f6621deb457bd94e732166e9e88cf

  • SHA256

    db7a7c02c22154620f35881e0f55e936567deaddc98feae2de11443280e1b894

  • SHA512

    2e45543fc62f925137136f1323b5b4b22d4167bf2a839fbc09dd2d554f50fcc01efa3c0aa43ca1e7b364770a671b4d9ec8f3f49dbadc76b8468ac557dd209ca4

  • 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\db7a7c02c22154620f35881e0f55e936567deaddc98feae2de11443280e1b894.exe
    "C:\Users\Admin\AppData\Local\Temp\db7a7c02c22154620f35881e0f55e936567deaddc98feae2de11443280e1b894.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:2476
  • 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:4772
    • 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:2440

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

    1055cacb496519b2beca1c0f53638ef3

    SHA1

    2c5325ff7b4f6621deb457bd94e732166e9e88cf

    SHA256

    db7a7c02c22154620f35881e0f55e936567deaddc98feae2de11443280e1b894

    SHA512

    2e45543fc62f925137136f1323b5b4b22d4167bf2a839fbc09dd2d554f50fcc01efa3c0aa43ca1e7b364770a671b4d9ec8f3f49dbadc76b8468ac557dd209ca4

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

    Filesize

    1.8MB

    MD5

    1055cacb496519b2beca1c0f53638ef3

    SHA1

    2c5325ff7b4f6621deb457bd94e732166e9e88cf

    SHA256

    db7a7c02c22154620f35881e0f55e936567deaddc98feae2de11443280e1b894

    SHA512

    2e45543fc62f925137136f1323b5b4b22d4167bf2a839fbc09dd2d554f50fcc01efa3c0aa43ca1e7b364770a671b4d9ec8f3f49dbadc76b8468ac557dd209ca4

  • memory/4772-155-0x0000000000D80000-0x000000000109F000-memory.dmp

    Filesize

    3.1MB

  • memory/4772-154-0x0000000000710000-0x0000000000754000-memory.dmp

    Filesize

    272KB

  • memory/4772-153-0x0000000000D80000-0x000000000109F000-memory.dmp

    Filesize

    3.1MB

  • memory/4772-152-0x0000000077BF0000-0x0000000077D93000-memory.dmp

    Filesize

    1.6MB

  • memory/4772-151-0x0000000000D80000-0x000000000109F000-memory.dmp

    Filesize

    3.1MB

  • memory/4772-149-0x0000000000D81000-0x0000000000D83000-memory.dmp

    Filesize

    8KB

  • memory/4772-147-0x0000000000710000-0x0000000000754000-memory.dmp

    Filesize

    272KB

  • memory/4772-146-0x0000000000D80000-0x000000000109F000-memory.dmp

    Filesize

    3.1MB

  • memory/5012-137-0x0000000000C71000-0x0000000000C73000-memory.dmp

    Filesize

    8KB

  • memory/5012-143-0x0000000077BF0000-0x0000000077D93000-memory.dmp

    Filesize

    1.6MB

  • memory/5012-142-0x0000000001010000-0x0000000001054000-memory.dmp

    Filesize

    272KB

  • memory/5012-141-0x0000000000C70000-0x0000000000F8F000-memory.dmp

    Filesize

    3.1MB

  • memory/5012-140-0x0000000077BF0000-0x0000000077D93000-memory.dmp

    Filesize

    1.6MB

  • memory/5012-139-0x0000000000C70000-0x0000000000F8F000-memory.dmp

    Filesize

    3.1MB

  • memory/5012-132-0x0000000000C70000-0x0000000000F8F000-memory.dmp

    Filesize

    3.1MB

  • memory/5012-136-0x0000000000C71000-0x0000000000C73000-memory.dmp

    Filesize

    8KB

  • memory/5012-135-0x0000000000C70000-0x0000000000F8F000-memory.dmp

    Filesize

    3.1MB

  • memory/5012-134-0x0000000001010000-0x0000000001054000-memory.dmp

    Filesize

    272KB

  • memory/5012-133-0x0000000000C70000-0x0000000000F8F000-memory.dmp

    Filesize

    3.1MB