context safety score
A score of 32/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 at skinnycrawlinglax.com fully impersonates a Google CAPTCHA/reCAPTCHA verification page, replicating Google's exact UI, messaging, and branding ('About this page', 'Our systems have detected unusual traffic', Terms of Service links pointing to google.com) while being hosted on a completely unrelated domain. (location: page.html:3-34, page-text.txt:19-27)
phishing
The page title is set to 'https://google.com/' and the form's hidden 'continue' field redirects to 'https://google.com/', creating a convincing phishing lure that makes users believe they are interacting with a legitimate Google service while on a fraudulent domain. (location: page.html:3, page.html:17)
malicious redirect
A hidden form field named 'continue' with value 'https://google.com/' is embedded in the POST form. After CAPTCHA completion the form submits to 'index' (same domain), and the continue parameter can be used to redirect victims to attacker-controlled destinations or harvest the CAPTCHA token before passing the user along. (location: page.html:17)
prompt injection
The page uses an onload handler invoking 'solveSimpleChallenge(0,0)' — a function call suggesting automated CAPTCHA bypass logic targeting AI agents or bots that render and execute JavaScript. This is consistent with attempts to manipulate agentic systems into auto-solving or auto-submitting the challenge form. (location: page.html:4)
credential harvesting
The fake Google CAPTCHA form POSTs to 'index' on the same malicious domain with an opaque encoded token in hidden field 'q'. This pattern is used to harvest reCAPTCHA responses and session tokens. The reCAPTCHA site key (6LfwuyUTAAAAAOAmoS0fdqijC2PbbdH4kjq62Y1b) is embedded and the solved token would be submitted to the attacker's server. (location: page.html:15, page.html:17)
social engineering
The page mimics an authoritative Google security warning ('unusual traffic detected', 'not a robot', reference to Terms of Service violations) to pressure users into completing the fake CAPTCHA, exploiting trust in Google's brand to compel interaction with the malicious form. (location: page.html:21-28, page-text.txt:21-24)
hidden content
An expandable 'Why did this happen?' div (id='infoDiv') is hidden by default (display:none) and contains additional social engineering text with links to google.com support pages, designed to further reinforce the Google impersonation and legitimize the fake page when revealed. (location: page.html:26-28)
curl https://api.brin.sh/domain/skinnycrawlinglax.comCommon questions teams ask before deciding whether to use this domain in agent workflows.
skinnycrawlinglax.com currently scores 32/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.