context safety score
A score of 38/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
cloaking
Page checks user-agent for bot/crawler strings to serve different content
js obfuscation
JavaScript uses Function constructor for runtime code generation
obfuscated code
A base64-encoded script is loaded inline via a data URI (`src="data:text/javascript;base64,ZnVuY3Rpb24g...`). The decoded content contains heavily obfuscated JavaScript using hex-encoded variable names (_0x* pattern), string array rotation, and anti-tamper logic — a classic malware obfuscation pattern used to conceal redirects, tracking, or payload delivery. (location: page.html line 87, <script src="data:text/javascript;base64,...">)
hidden content
A `<marquee>` element with `style="position:absolute; width:0px;"` is injected after the closing `</html>` tag via a plugin called `wpseoinj` (WP SEO Injector). It contains two hidden outbound links to `flowerhome.com.tw` (titled 'casino online no aams') and `unoregler.com` (titled 'Casino Utan Svensk Licens'). These are invisible to users but visible to crawlers and AI agents — a classic SEO spam / hidden link injection technique. (location: page.html lines 1591-1594, `<div class="wpseoinj-block" data-wpseoinj-id="1">`)
hidden content
Two plain-text gambling/spam keywords appear in page-text.txt without any visible associated content or labeling: 'casino online no aams' and 'Casino Utan Svensk Licens'. These correspond to the hidden injected links and confirm the SEO spam injection is rendering text that is invisible in normal browsing but extractable by text parsers and AI agents. (location: page-text.txt lines 1028-1029)
social engineering
The Histats tracker script is injected outside the closing `</html>` tag (lines 1578-1589), meaning it executes after the document is nominally complete. While Histats is a known analytics service, placing tracking code outside the HTML document boundary is non-standard and can be used to evade CSP policies or security scanners. (location: page.html lines 1578-1589, Histats script block after </html>)
curl https://api.brin.sh/domain/avyuri.comCommon questions teams ask before deciding whether to use this domain in agent workflows.
avyuri.com currently scores 38/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.