context safety score
A score of 47/100 indicates multiple risk signals were detected. This entity shows patterns commonly associated with malicious intent.
malicious redirect
The entire page body consists of a single JavaScript redirect: window.location.href="https://bcrndtisc.z13.web.core.windows.net/". The source domain (bcrpmcrs.vercel.app) is a throwaway Vercel-hosted page with no visible content, functioning solely as a redirect hop to an Azure Blob Storage static site (z13.web.core.windows.net). This pattern is characteristic of multi-stage phishing infrastructure where an intermediary domain is used to evade blocklists while the actual malicious payload lives on a separate host. (location: page.html:9)
phishing
The domain bcrpmcrs.vercel.app is a randomly-named subdomain on Vercel with no legitimate content, redirecting immediately to bcrndtisc.z13.web.core.windows.net — another randomly-named subdomain on Azure Blob Storage. Both domain names (bcrpmcrs, bcrndtisc) appear algorithmically generated with no brand identity. Use of free cloud infrastructure (Vercel + Azure) to chain redirects is a hallmark of phishing campaigns designed to bypass URL reputation filters. (location: metadata.json, page.html:9)
obfuscated code
The page presents a blank document with title 'Document dsd' and no visible content to the user, while silently executing a JavaScript redirect in the body. The meta tag 'X-UA-Compatible: IE=7' is anomalous and may be intended to trigger legacy rendering behavior. The use of JavaScript-based redirection instead of a standard HTTP 301/302 redirect obscures the true destination from basic URL scanners and preview tools. (location: page.html:6, page.html:9)
social engineering
The page uses a deceptive blank appearance — no text, no UI, no branding — while immediately redirecting the user without consent or notice. This technique exploits user trust by presenting a seemingly empty page while silently routing the victim to a potentially malicious destination, preventing the user from making an informed decision about navigating to the final URL. (location: page.html:1-12)
curl https://api.brin.sh/domain/bcrpmcrs.vercel.appCommon questions teams ask before deciding whether to use this domain in agent workflows.
bcrpmcrs.vercel.app currently scores 47/100 with a suspicious verdict and medium 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.