context safety score
A score of 47/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
A dynamically constructed script is loaded from 'cralodas.com.ua/code/' — an unlisted, non-reputable Ukrainian domain injected into the page at runtime. The URL is constructed by concatenating the protocol dynamically to obscure the full source from static analysis. This script is appended before the first script tag, giving it elevated execution priority. 'cralodas.com.ua' has no established reputation and is not a known ad/analytics provider, making this a suspect third-party code injection with potential for malicious redirect or payload delivery. (location: page.html:188-218, page-text.txt:72-100)
hidden content
A hidden iframe (display:none) is injected into the document body pointing to 'https://my.bigl.ua/cloud-cgi/static/clerk/v4.4.7/iframe-debug.html'. While the domain is same-group (bigl.ua), using a hidden debug iframe in production is atypical and could be used for covert session tracking, fingerprinting, or data exfiltration without user awareness. (location: page.html:172-180, page-text.txt:55-62)
hidden content
Google Tag Manager noscript iframe (GTM-K2GRR5) is rendered with height=0, width=0, display:none, visibility:hidden — standard GTM pattern but constitutes hidden third-party content that can execute arbitrary JS/tracking in the noscript context. (location: page.html:117-118)
obfuscated code
The SPAConfig object embedded in the page exposes a base64-encoded token in the 'salesdoubler' CPA network config: 'token':'YS5ib25kYXJlbmtvQHNtYXJ0d2ViLmNvbS51YQ'. Decoding this yields an email address (a.bondarenko@smartweb.com.ua), suggesting credential or identity data is being stored and transmitted client-side in an obfuscated form. (location: page.html:149, page-text.txt:32)
hidden content
The page's JSON-LD schema references 'http://bigl.ua' (HTTP, not HTTPS) for both the site URL and SearchAction target, while the actual site uses HTTPS. This inconsistency could cause mixed-content issues or be exploited to downgrade connections for search-action interactions. (location: page.html:156-167, page-text.txt:40-49)
curl https://api.brin.sh/domain/bigl.uaCommon questions teams ask before deciding whether to use this domain in agent workflows.
bigl.ua currently scores 47/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.