CyberKit

User Account Control Bypass

Also called UAC Bypass.

Elevating from a normal user to admin without a consent prompt.

What it is

Techniques that abuse auto-elevating processes, trusted directories, or registry hijacks to gain administrative rights on Windows without triggering the User Account Control consent prompt. They turn a medium-integrity process into a high-integrity one quietly.

Why it matters

Bypassing UAC lets an attacker reach full local admin with no user interaction, unlocking credential theft, persistence, and tampering. Detecting it usually means watching for known auto-elevation chains and unexpected high-integrity child processes.

In practice

A standard-user implant launches a trusted auto-elevating utility that loads its payload at high integrity, with no prompt shown to the user.

What to look for

  • Auto-elevating binaries such as fodhelper or eventvwr spawning unexpected children.
  • Registry writes under HKCU Software Classes right before an elevated process starts.
  • A high-integrity process with a medium-integrity parent and no consent prompt.

Common mistake

Calling UAC a security boundary. Microsoft does not treat it as one, so assume a local admin user can cross it.

Practice it nearby

CyberKit has no tool for this term itself. These are the closest places to practice it.

In the field

Well-known tools where this shows up on the job. They are listed to show the landscape, not as a recommendation.

  • Atomic Red Team Open source

    Small, scripted tests mapped to ATT&CK techniques, used to check whether a detection fires.

  • ATT&CK Navigator Open source

    Lays techniques out on the ATT&CK matrix so teams can mark coverage, gaps and threat profiles.

  • Microsoft Defender for Endpoint Commercial

    Tags its alerts with the ATT&CK techniques it observed on the host.

  • Sysmon Free

    Supplies the host telemetry that most technique detections are written against. Our notes.

Read next

Sources