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 forcibly opens https://ey43.com/4/10158502 in a new tab before the intended link is followed. The handler calls e.preventDefault() and e.stopImmediatePropagation(), suppressing legitimate navigation and sending users to a third-party ad/malware network on any interaction. (location: page.html:1877-1924 (inline <script> block); page-text.txt:1133-1178)
social engineering
The site prominently displays a banner urging users to visit a new domain: 'WELCOME WEBSITE NEW — New website, Let’s Go!!!' with a button that redirects to https://videy.design. This pattern is used to migrate an audience from an established domain to a fresh one, circumventing blocklists and browser history associated with the original domain. (location: page.html:625-637; page-text.txt:14-21)
social engineering
Video titles throughout the site use leet-speak substitutions (e.g., 'NYU5YU BI4R SEH4T', 'T4nte sxi', 'Crt d1mvk4', 'NGELUNJAK MINTA DIMA5UK1N', 'M4cn tutul', 'Ay4ng lagi ange', 'Udah ga ku4t', 'Crt dimuka 4d1c') to evade automated content filters while still conveying explicit adult/sexual content to human readers. This obfuscation technique is characteristic of sites deliberately evading moderation systems. (location: page.html:854, 901, 1194, 1331, 1365, 1411, 1620, 1671; page-text.txt:218, 263, 518, 638, 668, 713, 893, 938)
hidden content
HTML markup including <div>, <style>, and <script> elements appear after the closing </html> tag (lines 1927–2118). This out-of-band content includes a floating popup form, additional CSS, and a JavaScript block that manipulates the DOM. Placing code outside the proper document structure is a known technique to evade some HTML-only scanners that stop parsing at </html>. (location: page.html:1927-2118)
credential harvesting
A 'Report Content' popup form collects user name, email address, and a content URL, submitting via POST to https://formspree.io/f/manrjaak. While Formspree is a legitimate form-backend service, using it on an illicit adult content platform allows collection of real user email addresses and identities under the guise of a compliance/reporting feature, with no verifiable privacy guarantee. (location: page.html:1933-1938; page-text.txt:1187-1194)
brand impersonation
The site branding uses the name 'Videy' and logo closely mimicking the legitimate video hosting service videy.co, while operating from the domain videystream.asia and redirecting users to videy.design. This impersonates an established brand to attract users familiar with the original service. (location: page.html:618; metadata.json: domain=videystream.asia; page.html:632 (redirect to videy.design))
curl https://api.brin.sh/domain/videystream.asiaCommon questions teams ask before deciding whether to use this domain in agent workflows.
videystream.asia 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.