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
cloaking
Page loads content in transparent or zero-size iframe overlay
malicious redirect
The hotReplaceConfig in the page's inline JavaScript defines production CDN routing rules that redirect asset requests based on visitor hostname. Specifically, visits matching 'm.linhty.xyz' are redirected to 'static-act.piojm.tech' — both are unrecognized third-party domains with no clear affiliation to BIGO. This conditional redirect logic for static assets loaded from unknown domains could be used to serve tampered JavaScript, images, or other resources to targeted users. (location: page.html line 174 / page-text.txt line 136 — hotReplaceConfig prod.config: {visit:'m.linhty.xyz', target:'https://static-act.piojm.tech/live/assets/www_bigo_tv/client/'})
malicious redirect
The structured-data JSON-LD block in the page <head> references the logo image from 'https://static-web.hzmk.site' rather than the canonical BIGO domain (bigolive.tv or bigo.tv). The domain 'hzmk.site' is an unrecognized third-party host and appears in a structured-data context, suggesting it may be used as a covert asset-hosting or tracking endpoint inconsistent with the site's declared identity. (location: page.html line 15 — structured-data script: logo URL 'https://static-web.hzmk.site/as/bigo-static/www.bigo.tv/img/logo_icon_112x112.png')
hidden content
Several navigation elements are rendered with 'display:none' in the HTML, including the 'Muslim' nav link, the 'Recharge' button, and the login first-visit onboarding panel. While individually these can be UI state patterns, the combination of hidden interactive elements (login prompts, recharge links) hidden from view but present in the DOM is consistent with deceptive UI patterns or content selectively exposed to certain user segments. (location: page.html lines 46-51 — style='display:none;' on Muslim nav item, Recharge link, and first-in login panel)
social engineering
The download dialog uses urgency and reward framing ('A gift from Bigo Live is delivered - Go') to pressure users into downloading the mobile app. This is a social engineering dark pattern designed to manipulate user behavior through fabricated reward notifications. (location: page.html line 169 / page-hidden.txt line 52 — download-dialog inner text: 'A gift from Bigo Live is delivered - Go')
curl https://api.brin.sh/domain/bigo.tvCommon questions teams ask before deciding whether to use this domain in agent workflows.
bigo.tv 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.