context safety score
A score of 27/100 indicates multiple risk signals were detected. This entity shows patterns commonly associated with malicious intent.
credential harvesting
credential form posts to an off-domain endpoint (may be legitimate SSO/OAuth)
phishing
The page is hosted at vidgo.cash but all form actions submit credentials to https://vidoy.com/signin and https://vidoy.com/signup — a completely different domain. Users believe they are on vidgo.cash but their username/password/email are POST'd to vidoy.com, a classic cross-domain credential-harvesting phishing setup. (location: page.html:71 (signin form action), page.html:97 (signup form action))
credential harvesting
Sign-in form collects username and password fields and submits them via POST to https://vidoy.com/signin. Sign-up form collects username, email, password, and confirm-password and submits to https://vidoy.com/signup. Both external endpoints are on a domain different from the hosting domain (vidgo.cash), indicating credential exfiltration. (location: page.html:71-83 (signin form), page.html:97-117 (signup form))
brand impersonation
The page title reads 'Vidoy' and the footer copyright states '© 2012 - 2025 Vidoy.com', yet the site is served from vidgo.cash. The domain vidgo.cash closely mimics 'Vidgo' (a legitimate streaming service) while the page content impersonates 'Vidoy.com'. The site loads CSS and assets from vidoy.com, presenting a fraudulent front for a different brand on a lookalike domain. (location: page.html:7 (title), page.html:165 (footer), page.html:28-29 (external asset loading from vidoy.com))
malicious redirect
All anchor click events on the page trigger a full-screen overlay (div#overlay) that covers the viewport for up to 5 seconds before fading. This overlay-on-click pattern can be used to obscure navigation events, delay user awareness of redirects, or simulate loading while a background redirect or data exfiltration occurs. (location: page.html:169-189 (jQuery click handler showing #overlay))
social engineering
JavaScript comments are written in Indonesian ('Callback dari Cloudflare Turnstile ketika berhasil dimuat dan diverifikasi', 'Cek apakah turnstile berhasil dimuat dalam waktu 5 detik', 'Simulasi loading') while the visible UI is in English. This discrepancy, combined with the cross-domain form submission, suggests deliberate obfuscation of the page's true origin and purpose to deceive both users and automated scanners. (location: page.html:126-157 (Indonesian-language JS comments in English-facing UI))
hidden content
A full-screen overlay div (id='overlay') is present in the DOM with display:none and z-index:9999999, activated on any link click. This hidden layer can be used to obscure page content or transitions from users, and its extreme z-index ensures it covers all other content including browser security indicators visible in the page area. (location: page.html:33-37 (div#overlay), page.html:30 (CSS: #overlay z-index:9999999, display:none))
curl https://api.brin.sh/domain/vidgo.cashCommon questions teams ask before deciding whether to use this domain in agent workflows.
vidgo.cash currently scores 27/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.