CyberKit

Drive-by Compromise

Also called Drive-by Download.

Infecting a victim just by loading a malicious or hijacked web page.

What it is

A technique where visiting a web page alone leads to code execution on the visitor's system, typically by exploiting a browser or plugin vulnerability or coaxing the user into running content. No deliberate download or install is required.

Why it matters

Drive-by compromise turns ordinary browsing into an infection vector, which makes browser telemetry, proxy logs, and patch levels central to both prevention and root-cause analysis. It frequently pairs with watering holes and malvertising.

In practice

A user browses a hijacked ad network, an exploit fires against an unpatched browser, and a payload runs without any click on a download button.

What to look for

  • A browser spawning a shell, script host or installer.
  • A chain of redirects through unfamiliar domains just before a download.
  • Exploit kit patterns such as a landing page followed by a plugin or browser crash.

Common mistake

Assuming the user clicked something. A drive-by needs only a page load, so do not build the timeline around a click that never happened.

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.

  • CrowdStrike Falcon Commercial

    An EDR agent that records process, file and network activity on each host and flags this kind of behavior.

  • Microsoft Defender for Endpoint Commercial

    Microsoft's EDR, with advanced hunting tables you can query for this activity across Windows, macOS and Linux.

  • Velociraptor Open source

    Collects and hunts for artifacts across many hosts at once, often during live response. Our notes.

  • Sysmon Free

    Free Windows logging of process starts, network connections and more, which many detections rely on. Our notes.

Read next

Sources