context safety score
A score of 37/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
credential harvesting
Login form collects username ('email') and password fields via HTTP POST with no explicit action URL (posts to same page). The form uses autocomplete='off' to suppress browser credential managers, and custom JS login handler (login.js) processes credentials — submission destination and data handling are opaque. The page is a Russian-language login portal (distmed.com) impersonating or operating as Medpoint24/DistMed medical platform. (location: page.html:74-105, form.login-form method=post)
brand impersonation
The page is served from distmed.com but prominently references the brand 'Medpoint24' and directs users to postmaster@medpoint24.ru and v3.distmed.com. The HTML comment attributes copyright to 'Arcius, llc. http://arcius.ru/' and author domain 'distmed.ru', indicating the .com domain may be a clone or shadow of the legitimate .ru service, potentially used to harvest credentials from users who navigate to the .com variant instead of the legitimate .ru domain. (location: page.html:3-8 (HTML comment), page.html:186-193 (modal content))
malicious redirect
The modal popup urgently directs users away from the current login page to v3.distmed.com, framing it as a system upgrade. This social-engineering redirect pattern is commonly used to move victims from a monitored page to a credential-harvesting page, or to split traffic between old and new phishing infrastructure. (location: page.html:186-193, links to https://v3.distmed.com/ and https://v3.distmed.com/docs/about_v3)
social engineering
The modal is styled with high z-index (9999) to overlay the entire page, uses urgent language ('ВНИМАНИЕ!' / 'ATTENTION!'), and presents a forced interstitial that the user must actively dismiss. This dark-pattern design pressures users into following the redirect to v3.distmed.com or disclosing that they haven't received credentials, lowering their guard before credential submission. (location: page.html:180-212, CSS z-index:9999 overlay, modal id=mnv-modal)
hidden content
Yandex Metrika tracking pixel is rendered as a 1x1 image positioned at left:9999px (off-screen), invisibly tracking all page visitors including those who have JavaScript disabled. This covert tracking is consistent with reconnaissance of victim traffic on a credential-harvesting page. (location: page.html:258, noscript img src=https://mc.yandex.ru/watch/69958408 style=position:absolute;left:9999px)
curl https://api.brin.sh/domain/distmed.comCommon questions teams ask before deciding whether to use this domain in agent workflows.
distmed.com currently scores 37/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.