context safety score
A score of 49/100 indicates multiple risk signals were detected. This entity shows patterns commonly associated with malicious intent.
credential harvesting
The page presents a login form (Username + Password fields) under the branding of 'ТехноКад OAuth' on a subdomain newprivate.technokad.ru. Three credential-collecting forms are present: /Account/Login, /Account/LoginWithCertificate, and /Account/PasswordRecoveryRequest. The subdomain 'newprivate' is atypical for a legitimate OAuth endpoint and may indicate a staging or rogue instance harvesting credentials outside normal infrastructure. (location: page.html:55-107, line 229-242, line 251-284)
credential harvesting
A digital signature (certificate-based login) flow collects a cryptographic Signature field via /Account/LoginWithCertificate. Combined with username/password capture, this represents a full credential sweep including PKI credentials. (location: page.html:229-242)
social engineering
The page displays a spinner with text 'Проверяем плагин...' (Checking plugin...) before the login form renders. This creates a false sense of security verification, potentially lowering user suspicion before credentials are entered. (location: page.html:22-27)
social engineering
The certificate login modal falsely reassures users that 'all data is encrypted and protected from attackers' (все данные зашифрованы и защищены от воздействия злоумышленников), which is a common trust-building technique used in phishing pages to reduce user skepticism. (location: page.html:176-179)
malicious redirect
The ReturnUrl parameter embedded in all three forms encodes a redirect back to newprivate.technokad.ru/signin-oidc after login. If this is a rogue OAuth server, successful credential submission will complete a token issuance flow that could redirect the victim back with a valid session token, enabling account takeover on legitimate downstream services. (location: page.html:62, 230, 270)
phishing
The page impersonates a legitimate OAuth/OpenID Connect authorization server for 'ТехноКад' (TechnoKad), a Russian cadastral services company. The subdomain 'newprivate.technokad.ru' with client_id=lk and PKCE flow (code_challenge, S256) mimics a production OAuth server. If this is not the canonical production endpoint, it constitutes a full OAuth phishing attack to harvest authorization codes or credentials. (location: page.html:7, 55-107)
hidden content
A Yandex Metrika tracking pixel is loaded with position:absolute; left:-9999px off-screen, invisibly tracking all page visitors including click maps and session recordings (webvisor:true). This silently records user interactions including form field activity. (location: page.html:303)
curl https://api.brin.sh/domain/newprivate.technokad.ruCommon questions teams ask before deciding whether to use this domain in agent workflows.
newprivate.technokad.ru 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.