context safety score
A score of 43/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
js obfuscation
JavaScript uses Function constructor for runtime code generation
brand impersonation
The page at venturebeat.com is serving a 'Vercel Security Checkpoint' interstitial page. venturebeat.com is a well-known tech news publication unaffiliated with Vercel. Displaying a Vercel-branded checkpoint on a non-Vercel domain impersonates Vercel's brand and infrastructure to establish false legitimacy, potentially as a precursor to credential harvesting or redirecting users. (location: page.html:<title>, page-text.txt: footer 'Vercel Security Checkpoint')
obfuscated code
The page contains heavily obfuscated JavaScript using numeric string array lookups, self-executing rotating-array anti-tamper loops, and encoded string tables (e.g., arrays like ['749010VZHSDX','279243CGmpdw',...] with computed index arithmetic). This obfuscation pattern is characteristic of malicious scripts that hide their true behavior from static analysis and security scanners. (location: page.html: <script type='module'> block, lines 2)
malicious redirect
The page is a JavaScript-gated interstitial ('We're verifying your browser') that hides all content behind a #root div with display:none until the obfuscated script runs. This technique is commonly used to fingerprint visitors and redirect them conditionally — showing legitimate content to crawlers/bots while redirecting human visitors to phishing or malware pages. The actual destination after 'verification' is not determinable from static analysis of the obfuscated script. (location: page.html: <div id='root' style display:none>, obfuscated script block)
social engineering
The fake browser-verification prompt ('We’re verifying your browser') combined with a spinner and 'Enable JavaScript to continue' message is a classic social engineering lure designed to build user trust and induce compliance (enabling JS, waiting, clicking links) before delivering a malicious payload or redirect. (location: page.html: <p id='header-text'>, page-text.txt line 1)
hidden content
The entire page body content is hidden via CSS (display:none on #root) and only revealed by the obfuscated JavaScript after it executes. This prevents static content scanners and non-JS crawlers from seeing what is ultimately rendered to users, concealing the true purpose of the page. (location: page.html: <div id='root' class='container' style='display:none'>)
curl https://api.brin.sh/domain/venturebeat.comCommon questions teams ask before deciding whether to use this domain in agent workflows.
venturebeat.com currently scores 43/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.