Honorlock Chrome Extension: Technical Analysis of Permissions, AI Room Scans & Limitations
Deep security audit of Honorlock's browser extension. Understand manifest permissions, secondary device tracking, AI room scans, and what it cannot see.
Honorlock is widely utilized by educational institutions and certification bodies. Examining its technical architecture and patent claims dispels marketing myths and highlights its real-world capabilities.
Honorlock Extension Manifest Permissions Audit
Inspecting Honorlock's manifest.json reveals requests for:
desktopCapture: Prompts the candidate to share their screen via WebRTC.system.display: Identifies connected display monitors.webRequest: Intercepts network queries within the Google Chrome browser.
How Honorlock Claims to Detect Secondary Mobile Phones
Honorlock holds patents on "Multi-Device Detection". They seed test questions on public search results and ad networks. If a phone on your local Wi-Fi accesses those honeypots, the shared public IP triggers a flag. Keeping secondary devices on private 5G cellular data insulates you completely.
Webcam Room Scans: Boundaries of the AI Vision Engine
During a room scan, the candidate pans their webcam around the room. The AI vision engine searches for extra monitors, human faces, and notes taped to walls.
Technical Blind Spots: Operating Outside the Chrome Sandbox
Because Honorlock operates as a standard browser extension, it cannot access kernel processes or read OS window server compositing flags. Chameleon remains completely private to Honorlock's desktop capture feed.