context safety score
A score of 35/100 indicates multiple risk signals were detected. This entity shows patterns commonly associated with malicious intent.
encoded payload
suspicious base64-like blobs detected in page content
js obfuscation
Obfuscated document.write with encoded content
brand impersonation
The page title is 'Gcore' and the page is served from exitgames.com, but the visible content claims 'www.photonengine.com is using security service for protection against online attacks.' The domain being served (exitgames.com) does not match the domain being claimed (www.photonengine.com), indicating the page is impersonating a security interstitial for photonengine.com while actually hosted on a different, unrelated domain. (location: page.html:8 (title), page.html:219 (photonengine.com reference))
malicious redirect
The page presents itself as a 'Browser Validation Page' that automatically redirects visitors ('You will be redirected once the validation is complete') via JavaScript. The script uses window.location.reload() and dynamic form POST submission (sbbSbmt) controlled by an obfuscated bot-protection framework. A visitor to exitgames.com is being silently redirected after a fake validation check, which is a classic drive-by redirect pattern. (location: page.html:242 (sbbloadmid function), page.html:215-221 (loader div))
obfuscated code
Extensive obfuscated JavaScript using the 'sbb' (likely SiteLock Bot Blocker or a spoofed version) framework with minified, single-letter variable names, encoded strings via String.fromCharCode (e.g., genPid returns 'iZ'), hidden tracking pixel injection via dynamically created IMG elements pointing to /sbbi/ endpoint, and cookie manipulation logic. The function genPid() uses character code obfuscation to construct strings at runtime, a common technique to evade static analysis. (location: page.html:246-249 (genPid, sbbvscc, sbbgscc), page.html:251 (sbbgc, addmg, sbbeccf))
hidden content
Multiple elements are hidden from the user via inline style 'display:none': the JSCookieMSG div (id='JSCookieMSG'), the header element, and the div id='sbbhscc'. The div id='sbbfrcc' is positioned at top:-10px (off-screen) with font-size:1px and is used to inject hidden tracking/beacon IMG elements. This off-screen div is used as a covert channel to fire tracking beacons without user awareness. (location: page.html:170 (header display:none), page.html:172 (JSCookieMSG display:none), page.html:244 (sbbhscc display:none), page.html:250 (sbbfrcc off-screen div))
social engineering
The page uses a fake 'Browser Validation Page' / security interstitial pattern to convince users (and automated agents) that a legitimate bot-check is occurring, when the actual domain (exitgames.com) does not match the claimed site (photonengine.com). The message 'This process is automatic. You will be redirected once the validation is complete' is designed to suppress user suspicion and allow silent JavaScript execution and redirection without user consent. (location: page.html:215-221 (loader content), page.html:219 (photonengine.com claim))
prompt injection
The page is served from exitgames.com but asserts it belongs to www.photonengine.com within visible text. An AI agent crawling or summarizing this page would extract the domain claim 'www.photonengine.com' as the authoritative identity of the page, potentially being misled about the true origin domain. This cross-domain identity assertion in page content can manipulate agent-based web summarizers or security classifiers. (location: page.html:219, page-text.txt:56)
curl https://api.brin.sh/domain/exitgames.comCommon questions teams ask before deciding whether to use this domain in agent workflows.
exitgames.com currently scores 35/100 with a suspicious verdict and low confidence. The goal is to protect agents from high-risk context before they act on it. Treat this as a decision signal: higher scores suggest lower observed risk, while lower scores mean you should add review or block this domain.
Use the score as a policy threshold: 80–100 is safe, 50–79 is caution, 20–49 is suspicious, and 0–19 is dangerous. Teams often auto-allow safe, require human review for caution/suspicious, and block dangerous.
brin evaluates four dimensions: identity (source trust), behavior (runtime patterns), content (malicious instructions), and graph (relationship risk). Analysis runs in tiers: static signals, deterministic pattern checks, then AI semantic analysis when needed.
Identity checks source trust, behavior checks unusual runtime patterns, content checks for malicious instructions, and graph checks risky relationships to other entities. Looking at sub-scores helps you understand why an entity passed or failed.
brin performs risk assessments on external context before it reaches an AI agent. It scores that context for threats like prompt injection, hijacking, credential harvesting, and supply chain attacks, so teams can decide whether to block, review, or proceed safely.
No. A safe verdict means no significant risk signals were detected in this scan. It is not a formal guarantee; assessments are automated and point-in-time, so combine scores with your own controls and periodic re-checks.
Re-check before high-impact actions such as installs, upgrades, connecting MCP servers, executing remote code, or granting secrets. Use the API in CI or runtime gates so decisions are based on the latest scan.
Learn more in threat detection docs, how scoring works, and the API overview.
Assessments are automated and may contain errors. Findings are risk indicators, not confirmed threats. This is a point-in-time assessment; security posture can change.
integrate brin in minutes — one GET request is all it takes. query the api, browse the registry, or download the full dataset.