context safety score
A score of 32/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
brand impersonation
The domain vrv.co serves a full Crunchyroll premium acquisition page. VRV was a now-defunct streaming service; the domain is being used to present Crunchyroll branding, assets, og:site_name, fonts, and subscription flows — effectively impersonating Crunchyroll from a non-crunchyroll domain. (location: page.html:13-27, metadata.json (domain: vrv.co))
malicious redirect
The page loaded at vrv.co silently serves the Crunchyroll premium sign-up/billing acquisition app (baseSiteUrl: https://www.crunchyroll.com/premium, authorizedRoutes include /billing-plans, /billing/*, /plans). Users arriving at vrv.co are funneled into a Crunchyroll billing flow without being on the legitimate crunchyroll.com domain. (location: page.html:25 (window.etp config), metadata.json (url: https://vrv.co))
credential harvesting
The page embeds a full Crunchyroll account authentication and billing acquisition SPA (accountAuthClientId: kmj7imhjt_q90lcbzzsj, Firebase auth domain: cr-con-premium.firebaseapp.com, SSO base: https://sso.crunchyroll.com) served from a non-crunchyroll domain. Users may submit credentials or payment info while on vrv.co believing it is legitimate. (location: page.html:25 (window.etp config — cxApiParams, baseSsoUrl, firebase))
hidden content
A 1x1 invisible iframe is dynamically injected (height=1, width=1, position absolute, visibility hidden) and used to execute a Cloudflare challenge script. While likely a bot-detection mechanism, the hidden iframe pattern with dynamic script injection is a recognized technique for covert content execution that warrants flagging. (location: page.html:32)
phishing
The overall page constitutes a phishing risk: vrv.co loads Crunchyroll's premium subscription and billing UI, exposing users to a credential and payment capture flow under a domain that is not crunchyroll.com. Users who do not notice the domain mismatch may enter account credentials or billing details believing they are on the official site. (location: page.html (full page), metadata.json (domain: vrv.co))
curl https://api.brin.sh/domain/vrv.coCommon questions teams ask before deciding whether to use this domain in agent workflows.
vrv.co currently scores 32/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.