How gucci-on-fleek/lockdown-browser works
1. Repository purpose
- This is a Windows-only proof-of-concept that lets the Respondus LockDown Browser run inside Windows Sandbox by altering the browser’s environment and intercepting one Windows API call.
- The architecture is split between build-time tooling on the host and runtime components inside the sandbox.
2. Top-level subsystem layout
- src/ contains the actual bypass code and sandbox configuration files.
- runtime_directory/ is the launch/runtime payload that gets copied into the sandbox and used to start the browser.
- Detours/ is an external submodule used to hook a Windows DLL function.
- build.ps1 assembles everything into a runnable package.
3. Host-side build pipeline
- build.ps1 is the orchestration entrypoint for compiling the hook and preparing the runtime bundle.
- The build depends on Visual Studio C++ toolchain and the Windows SDK.
- The host never runs the target browser directly; it prepares files that will later execute inside the sandbox boundary.
4. Sandbox boundary
- The core isolation boundary is Windows Sandbox, which acts as the execution environment for the browser.
- The repo’s design assumes the browser runs only inside that ephemeral VM-like container, so no persistent state is retained between sessions.
- Two .wsb launch configurations exist: one standard and one that also passes microphone/camera devices through.
5. Runtime launcher layer
- runtime_directory/sandbox_run.ps1 is the main sandbox-side bootstrap script.
- It performs environment preparation before starting the browser, including removing or obscuring artifacts that the browser uses for virtualization checks.
- This script is the primary coordination point between the sandbox config and the browser launch.
6. Environment suppression logic
- One bypass mechanism is registry cleanup under HKLM:\HARDWARE\DESCRIPTION, which removes BIOS-related indicators the browser checks.
- Another is handling process detection of VmComputeAgent.exe by deleting the image file so the browser’s process inspection sees nothing meaningful.
- These actions happen inside the sandbox and are meant to change what the browser can observe about its environment.
7. API hook subsystem
- src/GetSystemMetrics-Hook.cpp implements a small DLL hook for GetSystemMetrics(SM_REMOTESESSION).
- This is used to stop the browser from detecting an RDP-like / remote-session condition.
- The hook is injected with help from Microsoft Detours, which supplies the detouring framework and is vendored as a submodule.
8. Browser launch path
- The actual Respondus browser executable is not included in the repo; the user must supply it in runtime_directory/.
- The sandbox launcher and runtime scripts assume that binary is present and then start it after the environment patches and hook injection are in place.
- This creates a simple flow: sandbox starts → bootstrap script prepares environment → hook is applied → browser launches.
9. Installer and packaging
- runtime_directory/setup.iss indicates an installer-style packaging step for staging the runtime directory contents.
- The repo is structured to produce a self-contained sandbox payload rather than a traditional installable application on the host.
- runtime_directory/ is effectively the deployment artifact boundary.
10. Documentation and operational modes
- Readme.md documents the supported launch variants, troubleshooting, and the distinction between the release/master/dev branches.
- docs/Example_1.webm is a demo artifact only; it does not affect runtime architecture.
- The repo’s architecture is intentionally minimal: one build script, one hook DLL, one sandbox bootstrap script, and one sandbox configuration layer.
11. External dependencies that materially shape the design
- Windows Sandbox is the execution platform and is central to the threat model.
- Microsoft Detours is the enabling technology for DLL/API interception.
- Respondus LockDown Browser is the external target binary the whole pipeline is built around.
12. High-level data/control flow
- Source code and scripts are built on the host.
- The resulting runtime files are placed into a shared sandbox directory.
- Windows Sandbox boots using a .wsb file, runs the PowerShell bootstrap, applies the hook, and launches the supplied browser executable.
- The browser runs isolated from the host, while the hook and environment changes influence the browser only within the sandbox boundary.
Main entry points: build.ps1 Build script · sandbox_run.ps1 Bootstrap · Readme.md Readme · GetSystemMetrics-Hook.cpp Metrics hook
Components 16
Host build
Build-time tooling and assembly on the Windows host.
- Build script · Assembles the hook DLL and runtime payload into a runnable package.
build.ps1 - VS toolchain · Visual Studio C++ compiler and Windows SDK required to compile the hook.
Sandbox runtime
Files and scripts that execute inside Windows Sandbox.
- Runtime bundle · Deployment boundary copied into the sandbox and used to launch the target browser.
runtime_directory - Sandbox config · Standard Windows Sandbox launch configuration.
src/Sandbox.xml - A/V config · Windows Sandbox launch configuration that passes microphone and camera devices.
src/Sandbox-with-Microphone-Camera.xml - Bootstrap · Prepares the sandbox environment and starts the browser inside the sandbox.
runtime_directory/sandbox_run.ps1 - Env cleanup · Removes or obscures environment artifacts used for virtualization and VM checks.
- Registry cleanup · Cleans BIOS-related indicators under HKLM:\HARDWARE\DESCRIPTION.
- VmComputeAgent · Deletes the image file so process inspection sees no useful VM agent artifact.
- Metrics hook · Intercepts GetSystemMetrics(SM_REMOTESESSION) to suppress remote-session detection.
src/GetSystemMetrics-Hook.cpp - Installer script · Packaging script for staging the runtime directory contents.
runtime_directory/setup.iss
External target
Supplied browser and platform dependencies the repo is built around.
Docs
Documentation and demo material.
- Readme · Documents launch variants, troubleshooting, and branch usage.
Readme.md - Demo video · Example recording used for illustration only.
docs/Example_1.webm
Connections 19
- Build script → VS toolchain: requires · Compilation depends on the Visual Studio C++ toolchain and Windows SDK.
- Build script → Metrics hook: builds · Produces the hook DLL from source.
- Build script → Runtime bundle: assembles · Stages the runtime payload for sandbox execution.
- Build script → Detours: links · Uses Detours to support API interception.
- Installer script → Runtime bundle: packages · Stages runtime directory contents for deployment.
- Sandbox config → Windows Sandbox: boots · Launches the standard sandbox session.
- A/V config → Windows Sandbox: boots · Launches the sandbox session with microphone/camera passthrough.
- Windows Sandbox → Bootstrap: runs · Starts the bootstrap script inside the sandbox boundary.
- Bootstrap → Env cleanup: prepares · Coordinates environment changes before browser launch.
- Env cleanup → Registry cleanup: cleans · Removes BIOS indicators from registry keys.
- Env cleanup → VmComputeAgent: obscures · Deletes the VmComputeAgent image artifact.
- Bootstrap → Metrics hook: loads · Ensures the hook is applied before launch.
- Metrics hook → Detours: uses · Relies on Detours to install the GetSystemMetrics hook.
- Bootstrap → Browser: launches · Starts the supplied browser executable after preparation.
- Browser → Windows Sandbox: contained by · Runs only inside Windows Sandbox.
- Readme → Sandbox config: documents · Explains the standard launch mode.
- Readme → A/V config: documents · Explains the audio/video passthrough launch mode.
- Readme → Build script: documents · Covers build and packaging workflow.
- Demo video → Readme: illustrates · Provides an example of the workflow in action.