context safety score
A score of 36/100 indicates multiple risk signals were detected. This entity shows patterns commonly associated with malicious intent.
malicious redirect
script/meta redirect patterns detected in page source
malicious redirect
A global click-hijacking script intercepts every click on the page (document.addEventListener('click', showAd, true)) and forces a new tab to open to https://ey43.com/4/10158502 before the intended navigation occurs. e.preventDefault() and e.stopImmediatePropagation() suppress the real click action. This is an aggressive ad-fraud / malicious redirect mechanism that can be used to send users to malware or phishing pages. (location: page.html:1877-1924 (script block), page-text.txt:1133-1178)
malicious redirect
A prominent banner button uses window.location.href to redirect users to https://videy.design, a different domain from videy-stream.online. The site presents itself as a 'new website' replacement, steering users away from the current domain. This cross-domain redirect via onclick is a common pattern in brand-migration phishing and traffic-hijacking. (location: page.html:632-634 (donation-banner button))
social engineering
The site uses leet-speak and character-substitution obfuscation in video titles (e.g., 'NYU5YU BI4R SEH4T', 'NGELUNJAK MINTA DIMA5UK1N', 'T4nte sxi', 'Crt d1mvk4', 'Ay4ng lagi ange', 'Udah ga ku4t', 'M4cn tutul') to disguise explicit/pornographic content from automated content filters and AI classifiers while still communicating the meaning to human users. This is deliberate obfuscation to evade detection. (location: page.html:957, 1433, 1467, 1291, 1513, 1721, 1004 (video titles throughout))
hidden content
HTML, CSS, and script elements are injected after the closing </html> tag (lines 1927–2118). This includes the floating report form, styles, and scripts placed outside the valid document structure. Content outside </html> may bypass certain HTML parsers and security scanners, functioning as a form of hidden/out-of-band injection. (location: page.html:1927-2118 (post-</html> content))
social engineering
The site operates as an Indonesian-language adult video streaming platform (videy-stream.online) impersonating a legitimate streaming service ('Videy') with professional UI, pagination showing 31 pages, and thousands of view counts. The 18 U.S.C. 2257 compliance link is included as a legitimacy signal while the site appears to distribute non-consensual or illicit content under obfuscated titles. (location: page.html:617-619 (logo), page.html:2101 (2257 compliance link))
credential harvesting
A floating popup form collects user name, email address, and content URL via a Formspree endpoint (https://formspree.io/f/manrjaak). While presented as a 'Report Content' form, it harvests PII (name + email) from users who interact with it. The form submits to a third-party service outside operator control, and the collected data destination is opaque. (location: page.html:1933-1938 (form action formspree.io/f/manrjaak))
curl https://api.brin.sh/domain/videy-stream.onlineCommon questions teams ask before deciding whether to use this domain in agent workflows.
videy-stream.online currently scores 36/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.