Is Secure Exam Proctor safe?
Proctorio is medium risk.
Secure Exam Proctor conceals all server domain names and API paths inside integer byte arrays throughout its code.
The extension stores more than 30 strings — including its server hostnames, API route segments, and a hardcoded AES-CBC decryption key — as Uint8Array integer sequences that must be decoded at runtime rather than appearing as readable text. This pattern covers every network-facing constant: the proctorauth.com API base, the proctor.io WebSocket host, and the telemetry.proctorcollect.com endpoint. Standard review tools that scan for domain names in source code will not surface these destinations without first running the decode step.
Who publishes itProctorio Inc. - 1 other listing from the same operator, none carrying a finding
Proctorio Inc. - 1 other listing from the same operator, none carrying a finding
Same store account
1 other listing published from this account, 442 users between them, none of them carrying a finding.
Shared hosts - 1 hostname
Hostnames hardcoded in this extension that few other listings call. That can mean one operator behind both, and it can equally mean a small shared vendor, so it is context rather than a conclusion. Hosts that many listings call are left out: they are services, not connections.
Proctorio findings
Removes page protections (CSP, frame headers) from every https page
The extension adds a rule that removes Content-Security-Policy and X-Frame-Options from all https page and frame replies, on any site, not just exam sites.
Based on code review, not seen running.
What actually happens
You start an exam session or open an assignment page.
The extension turns on a rule that strips security headers from every HTTPS page.
The rule is registered while the session runs.
The code that does this
Rule definition and the message handler that installs it
Rule 148 definition (lines 18461-18484)
assets/Js2Q.jsonThirdPartyHeadersReceived: { id: 148, rule: function() { return { id: this.id, priority: 1, action: { type: "modifyHeaders", responseHeaders: [{ header: "X-Frame-Options", operation: "remove" }, { header: "Frame-Options", operation: "remove" }, { header: "Content-Security-Policy", operation: "remove" }] }, condition: { urlFilter: "|https://*", resourceTypes: ["main_frame", "sub_frame"] } } }}Handler that installs the rule (line 23765)
assets/Js2Q.jsif (148 == l[0]) return ma.xf.updateDynamicRules({ removeRuleIds: [Qy.onThirdPartyHeadersReceived.id], addRules: [Qy.onThirdPartyHeadersReceived.rule()]}).then(() => { h([1])}).catch(t => { h([0])})What the rule removes
- Content-Security-Policyoperation: remove
Removes the page's own limits on which scripts and sources it may load.
- X-Frame-Optionsoperation: remove
Removes the header that stops other sites framing the page.
- Frame-Optionsoperation: remove
Removes a non-standard variant of the framing header.
What was and was not observed
The rule definition and its installation calls were verified in the shipped source. The test harness did not attach to the extension, so removal of headers from live responses was not observed.
Server domains and API paths stored inside byte arrays
The extension builds server domains, API paths, and crypto IDs at runtime from byte arrays, not text.
A hardcoded AES-CBC fallback key decodes from a Uint8Array via TextDecoder.
A PoC decoded 108 such patterns, unsearchable as plaintext.
What actually happens
You install the extension and it begins a proctored session.
The extension assembles server addresses and API paths from integer byte arrays; they are not written anywhere as readable text in the source code.
A static analysis tool or curious developer searching the source for 'proctorauth.com/scm/session/create' will find nothing; the string is constructed at call time.
Why you can't catch this in DevTools
This is how the 'proctorauth.com/scm/' base path appears in the shipped source. Without running the code, the destination server is not visible to a human reader.
proctorauth.com/scm/The code that does this
How session/create and session/end endpoints are constructed at runtime
session/create — readable form
// Wo() returns 'proctorauth.com/scm/'// 'session/create' is decoded inline from [115,101,115,115,105,111,110,47,99,114,101,97,116,101]const endpoint = `https://${subdomain}${isStaging ? '-staging' : ''}.proctorauth.com/scm/session/create`;const response = await fetch(endpoint, { method: 'POST', body: formData, headers: authHeaders }, 60000, 1);session/end — readable form
// 'session/end' is decoded inline from [115,101,115,115,105,111,110,47,101,110,100]const endpoint = `https://${subdomain}${isStaging ? '-staging' : ''}.proctorauth.com/scm/session/end`;await fetch(endpoint, { method: 'POST', body: formData, headers: authHeaders }, 60000, 1);AES-CBC fallback key — readable form
// Primary path: decrypt WebSocket payload with session key from servertry { return JSON.parse(atob(await decryptAES(parts[1], sessionKey, parts[0])));} catch (e) { // Fallback: decrypt with hardcoded 32-byte key 'AF1sUGvsvUsbjx5nr04OTzZ9CFYULUXw' const fallbackKey = new Uint8Array([65,70,49,115,85,71,118,115,118,85,115,98,106,120,53,110,114,48,52,79,84,122,90,57,67,70,89,85,76,85,88,119]); return JSON.parse(atob(await decryptAES(parts[1], fallbackKey, parts[0])));}Destinations constructed from encoded strings in the shipped source
- proctorauth.com
Primary backend. Session lifecycle endpoints (session/create, session/end) POST to <subdomain>.proctorauth.com/scm/.
- cdn.proctorauth.com
Content delivery origin for the extension's proctor assets.
- proctor.io
Primary product domain. WebSocket endpoints (gbl4845ws.proctor.io, gbl0317ws.proctor.io) constructed from encoded strings for real-time proctoring traffic.
- us1.gabbath.com
Session URL encoded in Js2Q.js: 'https://us1.gabbath.com/session?deviceid=&userid='. Purpose unclear from static analysis alone.
- telemetry.proctorcollect.com
Telemetry endpoint. Domain appears both as plaintext and was identified in related static analysis.
Reproduce it yourself
Scans the extension's main service worker (Js2Q.js) for all Uint8Array byte sequences and decodes them to plaintext, revealing domain names, API paths, cryptographic identifiers, and the hardcoded AES-CBC fallback key. Run it against a local copy of the extension.
- Node.js 18+ (for TextDecoder built-in)
- The extracted extension directory containing assets/Js2Q.js
/** * Decode Uint8Array-encoded strings from Secure Exam Proctor (fpmapakogndmenjcfoajifaaonnkpkei) * Claim 6701 reproducer — CWE-506 (Embedded Malicious Code / string obfuscation) * * Usage: * node secure-exam-proctor-decode-strings.js /path/to/extracted/assets/Js2Q.js */const fs = require('fs');const path = require('path');const jsPath = process.argv[2] || path.join(__dirname, 'assets/Js2Q.js');if (!fs.existsSync(jsPath)) { console.error('File not found:', jsPath); process.exit(1);}const js = fs.readFileSync(jsPath, 'utf8');const decoder = new TextDecoder();const regex = /new Uint8Array\(\[([^\]]+)\]\)/g;let m;const results = [];while ((m = regex.exec(js)) !== null) { const bytes = m[1].split(',').map(Number); try { const decoded = decoder.decode(new Uint8Array(bytes)); results.push({ pos: m.index, length: bytes.length, text: decoded }); } catch (e) { /* ignore non-UTF-8 */ }}console.log(`Total new Uint8Array([...]) patterns in file: ${results.length}`);console.log('\nAll decoded strings:\n');results.forEach(({ pos, length, text }) => { console.log(` offset ${pos.toString().padStart(7)} [${length} bytes]: ${JSON.stringify(text)}`);});// Highlight the hardcoded AES-CBC fallback keyconst KEY_BYTES = [65,70,49,115,85,71,118,115,118,85,115,98,106,120,53,110,114,48,52,79,84,122,90,57,67,70,89,85,76,85,88,119];const key = decoder.decode(new Uint8Array(KEY_BYTES));console.log('\n=== Hardcoded AES-CBC fallback decryption key ===');console.log(` Value: ${JSON.stringify(key)}`);console.log(` Length: ${key.length} bytes`);console.log(' Location: catch-block at ~offset 375114 in Js2Q.js');console.log(' Used when: server-supplied session key fails to decrypt WebSocket payload');- 1Download the extension and unzip the .crx.
- 2Run: node secure-exam-proctor-decode-strings.js /path/to/extracted/assets/Js2Q.js.
- 3Review the output: Uint8Array patterns decode, including the hardcoded AES-CBC fallback key.
Secure Exam Proctor stores its domains, paths and a key as byte arrays, not text
The extension's service worker builds domain names, API paths and a fallback decryption key from integer byte arrays at runtime.
The strings do not appear as plain text in the source.
Confirmed by code review; runtime not observed.
What actually happens
The service worker needs a host name, path or key.
It decodes the value from a byte array instead of reading a text string.
Plain-text searches for these hosts in the source return nothing.
Why you can't catch this in DevTools
Integer arrays in the source decode to the hosts and paths the extension uses.
cdn.proctorauth.comThe code that does this
Host name built from bytes
Host helper (line 8675)
assets/Js2Q.jsfunction ec() { const t = new Uint8Array([99, 100, 110, 46, 112, 114, 111, 99, 116, 111, 114, 97, 117, 116, 104, 46, 99, 111, 109]); return (new TextDecoder).decode(t)}Hosts recovered from the byte arrays
- proctor.io
Vendor domain decoded by a helper in the service worker.
- cdn.proctorauth.com
Vendor CDN host decoded by a helper in the service worker.
- proctorauth.com/scm/
Vendor path prefix decoded by a helper in the service worker.
What was and was not observed
A decoder script recovered 77 distinct strings from the shipped source, including a hardcoded fallback key. Network behaviour at runtime was not observed because the test harness did not attach to the extension.
What Proctorio can do
Permissions this extension asks for, as declared in version 1.5.26163.72. Asking for a permission is not a finding on its own - it is what the extension can do if it chooses to.
Read and change your data on every site you visit
ws://*/* and 2 more
Schedule its own background tasks
alarms
See the address and title of every tab you have open
tabs
Run its own code inside the pages you visit
scripting
Store data in your browser
storage
Store an unlimited amount of data in your browser
unlimitedStorage
Write to your clipboard
clipboardWrite
Watch every request your browser makes
webRequest
Block and redirect the requests your browser makes
declarativeNetRequest
See every page you navigate to, as you navigate to it
webNavigation
See, disable and uninstall your other extensions, including your security ones
management
Clear your browsing history, cache and cookies
browsingData
Read and change cookies, including the ones that keep you signed in
cookies
Speak text aloud
tts
Read your physical location
geolocation
Show you desktop notifications
notifications
Capture the contents of your screen, window or a tab
desktopCapture
Route all of your browsing through a server of its choosing
proxy
Read information about your CPU
system.cpu
Read how much memory your computer has
system.memory
Read information about your storage devices
system.storage
Read information about your displays
system.display
Start, monitor and manage your downloads
downloads
Keep your screen or computer awake
power
Capture the video and audio of a tab
tabCapture
Change your browser's privacy and security settings
privacy
Run hidden pages in the background
offscreen
Show a panel beside the page
sidePanel
Proctorio version history
1.5.25325.55
Mar 4, 2026
+13 more
1.5.26163.62
Oct 29, 2026
1.5.26163.69
Nov 16, 2026
1.5.26163.72
Nov 19, 2026
Chrome Web Store listing
- Versions
- 1.5.26163.72 latest of 17 seen since March 4, 2026
- Store rating
- 1.1 from 5,558 ratings
- Last updated
- July 28, 2026
- Size
- 20.25 MiB
- Privacy policy
- proctorio.com
