context safety score
A score of 24/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 page hosted on badak178regist.com fully impersonates a Google CAPTCHA verification page, including Google branding, Google reCAPTCHA Enterprise widget (data-sitekey), Google Terms of Service links, and verbatim Google 'unusual traffic' messaging. The domain has no affiliation with Google. (location: page.html:3-34, page-text.txt:19-27)
phishing
The page mimics Google's bot-detection CAPTCHA flow on a third-party domain (badak178regist.com) to deceive users and AI agents into believing they are interacting with a legitimate Google service. The page title is set to 'https://www.google.com/search?q=badak178/' to further spoof the origin. (location: page.html:3, page.html:30)
malicious redirect
The CAPTCHA form posts to a relative 'index' action and contains a hidden 'continue' field pointing to 'https://www.google.com/search?q=badak178/'. Upon CAPTCHA completion, the submitCallback auto-submits the form, likely redirecting through the attacker's server before forwarding to Google, enabling session interception or tracking. (location: page.html:7, page.html:14, page.html:17)
prompt injection
The page title is crafted as a full URL ('https://www.google.com/search?q=badak178/') rather than a human-readable title. This is a known prompt injection technique targeting AI agents and scrapers that use page titles as context, causing them to misidentify the page origin as google.com. (location: page.html:3)
social engineering
The page uses authoritative Google language ('Our systems have detected unusual traffic', 'in violation of the Terms of Service') to pressure users into solving a CAPTCHA and submitting form data to an attacker-controlled endpoint on a 129-day-old domain with unknown hosting reputation. (location: page.html:24-27, page-text.txt:21-24)
hidden content
An 'infoDiv' element is rendered with 'display:none' by default, containing additional Google-branded text and links. This content is hidden from casual visual inspection but present in the DOM and visible to scrapers/agents, potentially used to reinforce the Google impersonation narrative for automated systems. (location: page.html:26-28)
credential harvesting
The form contains a hidden field 'q' with an opaque base64-like encoded token value, submitted along with the reCAPTCHA response to the attacker's 'index' endpoint. This pattern is consistent with harvesting reCAPTCHA tokens or session identifiers that could be replayed or sold. (location: page.html:17)
curl https://api.brin.sh/domain/badak178regist.comCommon questions teams ask before deciding whether to use this domain in agent workflows.
badak178regist.com currently scores 24/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.