context safety score
A score of 47/100 indicates multiple risk signals were detected. This entity shows patterns commonly associated with malicious intent.
brand impersonation
The site ganamosnet.io presents itself as 'Ganamos' with meta description referencing 'Ganamos.net' ('The world's favourite online sports betting company... Live Streaming available on Ganamos.net'), while operating on a different domain (ganamosnet.io). The domain ganamosnet.io impersonates or spoofs the legitimate Ganamos.net brand, a known online sportsbook, using a confusingly similar domain name registered only 188 days ago. (location: page.html: <meta name='Description'> and <title>Ganamos</title>; metadata.json: domain ganamosnet.io)
malicious redirect
External scripts are loaded from sport.ganamos7.com (IntegrationLoader.min.js and bootstrapper.min.js), a third-party domain distinct from both ganamosnet.io and ganamos.net. This typosquat-style domain (ganamos7.com) could serve as a redirect or code injection vector, loading arbitrary JavaScript bootstrapper code into the page. (location: page.html: <script src='https://sport.ganamos7.com/js/Partner/IntegrationLoader.min.js'> and <script src='https://sport.ganamos7.com/js/partner/bootstrapper.min.js'>)
hidden content
A Yandex Metrica tracking pixel is embedded as a hidden image (style='position:absolute;left:-9999px') inside a <noscript> tag, used to covertly track users without their awareness. The tracker also enables 'webvisor:true' which records full session replays, capturing user interactions including any credentials entered. (location: page.html: <noscript><div><img src='https://mc.yandex.ru/watch/99966874' style='position:absolute;left:-9999px' alt=''></div></noscript>)
credential harvesting
Yandex Metrica is initialized with 'webvisor: true', enabling full session recording including keystrokes and form inputs. On a gambling/login site, this can capture usernames, passwords, payment details, and other sensitive credentials entered by users. Yandex (Russian-owned) session replay on a non-Russian gambling site is anomalous and high-risk. (location: page.html: ym(99966874, 'init', { clickmap: true, trackLinks: true, accurateTrackBounce: true, webvisor: true }))
social engineering
The site disables user zoom controls (user-scalable=0) and attempts to programmatically hide the browser address bar on Android devices by manipulating scroll position. This behavior reduces user ability to verify the URL and is a technique used to make phishing/impersonation sites appear more like legitimate native apps, obscuring the suspicious domain from victims. (location: page.html: <meta name='viewport' content='...user-scalable=0'> and Android address bar hiding script)
curl https://api.brin.sh/domain/ganamosnet.ioCommon questions teams ask before deciding whether to use this domain in agent workflows.
ganamosnet.io 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.