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 on vidstrm.mom but presents a login/signup form that submits credentials directly to vidoy.com (action="https://vidoy.com/signin" and action="https://vidoy.com/signup"). The site impersonates Vidoy by using Vidoy's branding, CSS, and assets while collecting credentials on a different domain, a classic cross-domain credential harvesting phishing setup. (location: page.html:71, page.html:97)
credential harvesting
Sign-in form posts username and password fields via HTTP POST to https://vidoy.com/signin from a different origin domain (vidstrm.mom). Sign-up form similarly posts username, email, and password to https://vidoy.com/signup. User credentials entered on vidstrm.mom are transmitted to a third-party domain. (location: page.html:71-83, page.html:97-117)
brand impersonation
The site (vidstrm.mom) uses Vidoy.com's exact branding including SVG logo, CSS stylesheets loaded directly from vidoy.com (bootstrap.vidoy.css, style.vidoy.css), and footer copyright '© 2012 - 2025 Vidoy.com'. The page title is 'Vidoy' and all visual identity belongs to vidoy.com while the actual serving domain is vidstrm.mom. (location: page.html:7, page.html:28-29, page.html:165)
malicious redirect
All anchor clicks on the page trigger a full-screen overlay (#overlay) that persists for 5 seconds before fading out. This overlay intercept mechanism can be used to delay user awareness of redirects or to mask navigation to malicious destinations. (location: page.html:169-189)
social engineering
The page presents a convincing replica of the legitimate Vidoy.com login interface on an unrelated .mom TLD domain (vidstrm.mom), designed to deceive users into believing they are on the official site and voluntarily submitting their credentials. (location: page.html:66-123)
hidden content
A full-screen overlay div (#overlay) is present in the DOM with display:none and z-index:9999999. It is programmatically shown on every link click, temporarily obscuring the entire page. While used here as a loading screen, the pattern can hide malicious content or redirect activity from users and automated scanners. (location: page.html:33-37, page.html:30 (CSS #overlay definition))
curl https://api.brin.sh/domain/vidstrm.momCommon questions teams ask before deciding whether to use this domain in agent workflows.
vidstrm.mom 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.