context safety score
A score of 35/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
social engineering
Unlicensed online gambling platform targeting Vietnamese users with aggressive promotional language including '100% deposit bonus', '1000 tỷ reward', and fabricated legitimacy claims (Isle of Man / Cagayan license unverifiable). Designed to harvest financial credentials and real-money deposits. (location: page.html: meta description, og:description, schema.org Article headline)
credential harvesting
Login (/Login) and registration (/Register) endpoints present on a gambling site with no verifiable regulatory standing. All JS logic is loaded from an external third-party CDN host (q7sm4r.katawee.net), meaning credential-handling code is fully controlled off-domain and cannot be audited from the page source. (location: page.html: script src=https://q7sm4r.katawee.net/system-requirement/Web.PortalNew/UK254-01/357a870883/main.bundle.js and vendor.bundle.js)
obfuscated code
All application logic — including form handling, authentication, and payment flows — is loaded as opaque pre-bundled JavaScript from an external host (q7sm4r.katawee.net) with a path pattern suggesting multi-tenant hosting infrastructure (UK254-01, hash 357a870883). Content cannot be inspected; malicious behavior including keylogging or credential exfiltration cannot be ruled out. (location: page.html lines 207-208: vendor.bundle.js and main.bundle.js from q7sm4r.katawee.net)
hidden content
The visible page text (page-text.txt) contains only the JsLoadingOverlay bootstrap call — the entire page content is rendered client-side via an opaque AngularJS/ui-router SPA (<ui-view>) loaded from off-domain bundles. No human-readable content is present in the HTML body, making static analysis of the actual rendered site impossible and allowing dynamic injection of arbitrary content after page load. (location: page.html body: <div id='app'><ui-view></ui-view></div>; page-text.txt line 1)
brand impersonation
The domain shbet800.com uses a numeric suffix ('800') appended to the brand name 'SHBET', a common typosquatting/satellite-domain pattern used to impersonate a primary brand. The schema.org publisher name is listed as 'XUXIAN' — inconsistent with the SHBET branding — suggesting the site is operated by an undisclosed third party misrepresenting itself as the official SHBET platform. (location: page.html line 200: schema.org Article publisher name='XUXIAN'; domain shbet800.com vs brand SHBET)
malicious redirect
Favicon is loaded from a separate unrelated domain (q7sm4r.katawee.net) and the OG image from a Cloudflare Pages subdomain (shbetlibrary.pages.dev). External asset loading from multiple unrelated third-party origins (katawee.net, postimg.cc, shb32.com, shbetlibrary.pages.dev) expands the attack surface for supply-chain redirects or resource substitution. (location: page.html: link rel=icon href=https://q7sm4r.katawee.net/...; og:image=https://shbetlibrary.pages.dev/shbet.jpg; schema image=https://shb32.com/...)
curl https://api.brin.sh/domain/shbet800.comCommon questions teams ask before deciding whether to use this domain in agent workflows.
shbet800.com currently scores 35/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.