Microsoft Edge Add-ons Verified domain

Secure Exam Proctor

2205b4bc-3151-5ca2-9e79-f17984803587 | Store v1.5.26163.72
53/ 100
MEDIUM risk
No change since v1.5.26163.69
AI review verdict
Needs follow up

From the RiskyPlugins AI security review of the observed evidence. The review covers version 1.5.26163.62, not the analysed version 1.5.26163.72.

Analysis record

Analysed
Yesterday 21 November 2026
Version
v1.5.26163.72
Artifact
SHA256 8c6e0488…6045a6
Detail
Partial list

Is Secure Exam Proctor safe?

Secure Exam Proctor declares no special permissions or host permissions, and no network endpoint is named. The listing describes an exam-accessibility tool, while NET-FETCH-assets/L5h2.js-1 shows that one bundled script can make web requests.

The harder part to assess is hidden code. OBFUSCATION-large_base64 and OBFUSCATION-fromcharcode_bulk in assets/Js2Q.js:0 mean the file contains data or code assembled at runtime. If that content handled exam data, logged users, or sent requests, the current scan does not show the decoded behavior. OBFUSCATION-invisible_unicode_payload in webassets/z17p.svg:0 also needs inspection.

No finding identifies a harmful website, credential collector, proxy function, search-page change, or known malware. The scanner tripped on encoded asset files and fetch calls without naming their destinations. The publisher field is empty, so decoding assets/Js2Q.js:0 and checking the requests from assets/L5h2.js:1:0 are needed to settle whether those files serve the stated exam function.

Evidence ledger

Ranked by severity · findings with a source location link to the code viewer

Showing 1,000 of 1,168 findings.
Showing 25 of 328 · highest severity first

YARA Rule Matches

17 rules
SeverityRuleHitsFilesMetadata
LOWSQLInjection 13
assets/drops/a46500a59e22ede7463a72111501c7be.jsassets/drops/50119de9eb543fc2f23401270c89d8c6.jsassets/drops/ce83ebdf2ac0da64977296979a6d15ca.js +10 more
-
LOWUntrustedContentShouldNotBeIncluded 18
assets/Js2Q.jsassets/drops/bcn896c8ea8f49559f1cf987771fcf3f.jsassets/drops/ce83ebdf2ac0da64977296979a6d15ca.js +15 more
-
LOWNoUseWeakRandom 29
assets/dew/7a8afd8e5d66423d88f69953dda76bc1.jsassets/drops/3ff2e003b123227bf10979b8f846369d.jsassets/drops/d28ca3edd49f49b3b8c1e6af621bd855.js +26 more
-
LOWpostinstall file download 70
assets/helpers/a210s.jswebassets/CGHH.jsassets/drops/eb9ea8f55dbb3ae09ca2a5e348ab21ec.js +67 more
-
LOWUsingIntrusivePermissionsWithGeolocation 4
assets/drops/d0442756f0d7ebded8edaa697b82d611.jsassets/drops/50119de9eb543fc2f23401270c89d8c6.jsassets/drops/c94f2203d07a3a6506e266b1e52b7343.js +1 more
-
LOWLocalStorageShouldNotBeUsed 24
assets/drops/657482036c4b025b68a7982a8e6eafcd.jsassets/drops/3fa4b2fcd005802fb61419276142cdc9.jsassets/Js2Q.js +21 more
-
LOWUsingCommandLineArguments 9
assets/drops/3ff2e003b123227bf10979b8f846369d.jsassets/drops/7153146608c0852aeb9006b607e0d39d.jsassets/drops/ce83ebdf2ac0da64977296979a6d15ca.js +6 more
-
LOWpostinstall obfuscation 72
assets/drops/5f6d2043e4244c08afb3b59c928a7cad.jsassets/Zxms.jsassets/drops/c94f2203d07a3a6506e266b1e52b7343.js +69 more
-
LOWpostinstall system command 74
assets/helpers/cd43b.jsassets/Zfsz.jsassets/drops/c5e5541622a147e4b5b279d034d44975.js +71 more
-
LOWpostinstall network communication 68
assets/drops/c94f2203d07a3a6506e266b1e52b7343.jsassets/drops/b18e4fdc91e84f5c94ca5c00f6bfa290.jsassets/drops/ab3f47d24766d27145ee435544b6696d.js +65 more
-
LOWOriginsNotVerified 25
assets/drops/5f6d2043e4244c08afb3b59c928a7cad.jsassets/drops/657482036c4b025b68a7982a8e6eafcd.jsassets/drops/eb9ea8f55dbb3ae09ca2a5e348ab21ec.js +22 more
-
LOWpostinstall file manipulation 81
assets/Zxms.jsassets/drops/c94f2203d07a3a6506e266b1e52b7343.jsassets/drops/b18e4fdc91e84f5c94ca5c00f6bfa290.js +78 more
-
LOWpostinstall registry modification 31
assets/drops/50119de9eb543fc2f23401270c89d8c6.jsassets/drops/ce83ebdf2ac0da64977296979a6d15ca.jsassets/drops/4da9eda8d98ad7ade0a573a2ad2026c0.js +28 more
-
LOWpostinstall crypto operations 43
assets/offscr.jswebassets/t00t.svgwebassets/q17m.svg +40 more
-
LOWWarpStrings 26
assets/drops/ce83ebdf2ac0da64977296979a6d15ca.jsassets/drops/4da9eda8d98ad7ade0a573a2ad2026c0.jsassets/drops/a46500a59e22ede7463a72111501c7be.js +23 more
-
LOWpostinstall persistence mechanism 57
assets/Zfsz.jsassets/drops/c5e5541622a147e4b5b279d034d44975.jsassets/helpers/a190s.js +54 more
-
LOWcredential env files 28
assets/drops/bcn896c8ea8f49559f1cf987771fcf3f.jsassets/drops/d0442756f0d7ebded8edaa697b82d611.jswebassets/q17m.svg +25 more
-

Publisher Evidence

Limited evidence

Proctorio

Publisher identity, store signals, distribution reach, and warning signals used for context. Treat this as supporting evidence, not a clean bill of health.

Edge does not expose the same publisher verification data as IDE stores, so this score is deliberately conservative.

42
Publisher domain
proctorio.com
Observed
Store verification signal
Limited signal
Limited
Extension portfolio
4
Portfolio

12 evidence rows available.

Finding Categories

3
Network

YARA Rules Matched

17 rules(672 hits)
SQLInjection UntrustedContentShouldNotBeIncluded NoUseWeakRandom postinstall file download UsingIntrusivePermissionsWithGeolocation LocalStorageShouldNotBeUsed UsingCommandLineArguments postinstall obfuscation postinstall system command postinstall network communication OriginsNotVerified postinstall file manipulation postinstall registry modification postinstall crypto operations WarpStrings postinstall persistence mechanism +1 more

AI Security Report

AI Security Review

Evidence context: threat category none; evidence quality moderate.

What the scan found

The package declares no special permissions or host permissions, and no network destination is identified. Three fetch detections, NET-FETCH-assets/L5h2.js-1, NET-FETCH-assets/helpers/a211s.js-1, and NET-FETCH-webassets/7e8cae6bb6672f9c89db0afe6c660be7.js-1, show that code in those files uses web-fetching functionality. Fetch calls are normal in an exam tool that loads service content, but these findings provide no URL, request body, or response handling. They therefore do not establish contact with a tracking, advertising, credential, or command-and-control service.

The main concern is source readability. OBFUSCATION-large_base64 and OBFUSCATION-fromcharcode_bulk both match assets/Js2Q.js:0. Bulk String.fromCharCode construction and a large Base64 block can reconstruct code or data at runtime, which blocks a reviewer from seeing the final content directly. The same OBFUSCATION-fromcharcode_bulk rule also matches several hashed scripts under assets/drops/, including assets/drops/3ff2e003b123227bf10979b8f846369d.js:0 and assets/drops/ce83ebdf2ac0da64977296979a6d15ca.js:0. These paths look like generated assets, though the findings do not reveal their decoded contents.

OBFUSCATION-invisible_unicode_payload in webassets/z17p.svg:0 adds uncertainty. An SVG file can contain encoded content or text data, and this rule provides no decoded payload, script execution path, or destination. The unnamed developer compounds the verification gap because the listing gives users no publisher identity to compare against the code in assets/Js2Q.js:0 or webassets/z17p.svg:0.

There is no listed finding that names a malware family, credential collection routine, browser-search replacement, proxy relay, or suspicious domain. The fetch findings in assets/L5h2.js:1:0 and webassets/7e8cae6bb6672f9c89db0afe6c660be7.js:1:0 lack endpoint details, so they cannot support a claim that user data is sent anywhere. The many low-level scanner matches are also not described as malicious behavior, and the supplied material ties the concrete concerns to encoded JavaScript rather than to a known harmful action.

A skeptic would reasonably treat the hidden code in assets/Js2Q.js:0, the hashed scripts in assets/drops/, and the SVG match in webassets/z17p.svg:0 as a reason to avoid trust. That concern remains valid. Yet encoded assets alone do not prove harmful intent, especially without a decoded payload, a suspicious destination, elevated permissions, or a malware signature. Deobfuscating assets/Js2Q.js:0, extracting the contents of webassets/z17p.svg:0, and observing requests from the three fetch-marked files would resolve the open question.

Key Reasons

  • assets/Js2Q.js:0 triggers both OBFUSCATION-large_base64 and OBFUSCATION-fromcharcode_bulk, leaving executable content unreadable.
  • webassets/z17p.svg:0 triggers OBFUSCATION-invisible_unicode_payload without a decoded explanation.
  • NET-FETCH-assets/L5h2.js-1 and related fetch findings show network-capable code but disclose no destination.
  • The extension declares no permissions or host permissions, and no malware signature or suspicious endpoint is identified.
  • The developer name is empty, preventing publisher-based verification.

False Positive Considerations

  • Low-severity code-smell matches are broad JavaScript detections rather than identified harmful behavior.
  • The network detections name fetch-capable files but provide no destination or transmitted data.
  • Hashed files under assets/drops/ can be generated bundled assets, although their encoded content still needs inspection.

Reviewed 2026-11-01 · version 1.5.26163.62; recommended action: runtime analysis; model confidence 65%.

Edge version history

Risk trend by version

16 analyzed versions. Each point is the latest successful scan for that version; failed zero-score scans are hidden. Dates: First seen by Risky Plugins.

Selected
53
Change since first
+5
Change from previous
No change
Versions:
First analyzed version
1.5.26037.49
First seen Apr 24, 2026
Risk range
47 to 64
Across analyzed versions
Latest analyzed version
1.5.26163.72
First seen Nov 21, 2026
Selected version
medium
Version
v1.5.26163.72
First seen Yesterday
Risk score
53
Findings
1168
Change vs previous
No change

Pick any point on the chart, then open the Source tab to read that version's code.

Source Code Viewer

Source Code Not Available

Source code is not available for this version of the extension.

Frequently Asked Questions