context safety score
A score of 49/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
obfuscated code
Inline script reads all browser cookies via decodeURIComponent(document.cookie), extracts values prefixed 'adcapban', then dynamically injects an external script from the third-party domain static-cdn.xyz, passing cookie data as query parameters. String.fromCharCode(38) is used to obfuscate the '&' character in the URL, a common obfuscation technique to evade static scanners. This pattern appears twice (lines 317 and 2808/2820). (location: page.html:317, page.html:2808, page.html:2820 — inline <script> blocks inside .fullbanner sections)
credential harvesting
The obfuscated ad script reads document.cookie and transmits cookie contents to an external third-party server at https://static-cdn.xyz/ser.php with the psc parameter containing harvested cookie data. Any session tokens, authentication cookies, or tracking identifiers stored in cookies are exfiltrated to this external domain on every page load. (location: page.html:317 — <script> inside <div id='AADIV128'>, and page.html:2808/2820 — <div id='AADIV129'>)
malicious redirect
The script at https://static-cdn.xyz/ser.php is dynamically appended to document.head, giving it full page control. Static-cdn.xyz is a generic, unbranded CDN-style domain with no transparent ownership — a common pattern for malvertising networks that can serve redirects, popunders, or drive-by download payloads depending on user profile. (location: page.html:317 — s.src set to https://static-cdn.xyz/ser.php with dynamic parameters)
hidden content
A Cloudflare challenge/bot-detection script at the very end of the page (line 5832) creates a hidden 1x1 pixel invisible iframe (position:absolute, top:0, left:0, visibility:hidden) and injects a script into it. While this is a known Cloudflare Bot Management pattern, the hidden iframe technique can also be used to load hidden content or perform covert actions not visible to the user. (location: page.html:5832 — final inline <script> before </body>)
hidden content
The keywords meta tag includes competitor brand names and alternate domain names (movie.ge, moviege, imovie.ge, jimuvi, muviji, gemovies) that do not belong to ge.movie. This is SEO keyword stuffing using third-party brand identifiers to hijack search traffic, which can be considered brand impersonation for traffic diversion purposes. (location: page.html:15 — <meta name='keywords'> tag)
curl https://api.brin.sh/domain/ge.movieCommon questions teams ask before deciding whether to use this domain in agent workflows.
ge.movie currently scores 49/100 with a suspicious verdict and medium 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.