context safety score
A score of 49/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
phishing
1 deceptive links where visible host does not match destination host
malicious redirect
Navigation tab link uses third-party ad network URL (a.neurogrid7.com) with tracking parameters disguised as site navigation. The link labeled 'AI JERK OFF' in the primary nav redirects to an external ad network rather than an on-site page. (location: page.html:139 - <a href="https://a.neurogrid7.com/bacdafce-6e6c-4891-b316-4cb55176211a?creative=ai_jerk_off&spot=nav_home_news">)
malicious redirect
Native ad unit embedded inline within the story listing grid uses an external ad network redirect (a.neurogrid7.com) styled identically to organic story listings, with only a small 'Ad' badge distinguishing it. The link destinations are obfuscated UUIDs on a.neurogrid7.com. (location: page.html:303-319 - Candy AI native ad block linking to https://a.neurogrid7.com/be325fa8-70ec-43e8-98e2-caa76083c18a)
social engineering
'Interactive Chat Stories' section labeled 'Ad' promotes GirlfriendGPT (gptgirlfriend.online) characters with grooming/manipulation scenario descriptions (e.g., 'Perfect for you to corrupt by slowly earning her trust and affection'). This exploits user trust to drive engagement with third-party AI chat platforms via social/emotional manipulation framing. (location: page.html:671-762 - Interactive Chat Stories Ad section)
hidden content
HTML comment in the page <head> attempts to address anyone inspecting the source code with social/playful framing ('you little PERV like to have a lookie lookie'). While humorous in intent, this is a form of content directed at automated scanners and humans reviewing source, potentially intended to disarm scrutiny. (location: page.html:38-42 - HTML comment block)
prompt injection
ExoLoader third-party ad script loaded from an opaque path (/6sb2DQenyX/yTqpa88bgF.js) with inline JavaScript that dispatches a custom DOM event ('getexoloader') and sets domain_base to 'exosrv.com'. An AI agent processing this page could be directed to interact with or trust content served by exosrv.com without clear provenance. (location: page.html:94-101 - ExoLoader script block)
curl https://api.brin.sh/domain/chyoa.comCommon questions teams ask before deciding whether to use this domain in agent workflows.
chyoa.com currently scores 49/100 with a suspicious verdict and medium 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.