context safety score
A score of 61/100 indicates minor risk signals were detected. The entity may be legitimate but has characteristics that warrant attention.
hidden content
JavaScript function `ocultarFormulario()` is called immediately after page load to set the login form's display to 'none', hiding the credential form from view. This is anomalous behavior for a legitimate login page — a real Moodle login form should never programmatically hide itself. This could indicate the page is used as a decoy, or that a different (potentially malicious) login UI is injected after the form is hidden. (location: page.html:136-143)
credential harvesting
The page contains a username/password login form (Moodle login) that is immediately hidden via JavaScript after render. The form still exists in the DOM and submits to `https://campusdocenciaanterior.ucv.es/curso2425/login/index.php`. The combination of a credential form that is programmatically hidden is a strong indicator of credential harvesting infrastructure — credentials may be captured by injected scripts before or after the hidden form is manipulated. (location: page.html:54-74, page.html:136-143)
social engineering
The Microsoft OAuth2 SSO button loads a microsoft.png image from a different subdomain (`campusdocencia.ucv.es`) while the rest of the page is served from `campusdocenciaanterior.ucv.es`. This cross-subdomain asset inconsistency may be used to create a convincing Microsoft sign-in prompt on a page that does not fully match the legitimate platform, increasing the risk of users being deceived into entering Microsoft credentials. (location: page.html:79)
malicious redirect
The page includes 2 redirects (per Tier 1 scan) and contains a link directing users to a prior-year platform (`https://campusdocenciaanterior.ucv.es/curso2324/login/index.php`). While the URL remains on the same domain, the pattern of a login page that hides its own form combined with cross-year redirects may be used to funnel users to less-monitored or outdated platform instances. (location: page.html:86)
curl https://api.brin.sh/domain/campusdocenciaanterior.ucv.esCommon questions teams ask before deciding whether to use this domain in agent workflows.
campusdocenciaanterior.ucv.es currently scores 61/100 with a caution 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.