context safety score
A score of 43/100 indicates multiple risk signals were detected. This entity shows patterns commonly associated with malicious intent.
malicious redirect
Immediate meta-refresh redirect (content="0; url=...") sends visitors instantly to https://ibank-nbg-web.efficientscalp.com/wb — a suspicious domain mimicking a bank ('ibank', 'nbg' likely National Bank of Greece) hosted under the unrelated domain 'efficientscalp.com'. The redirect is instantaneous (0 seconds), leaves no visible content, and suppresses the referrer header to evade analytics and forensic tracking. (location: page.html:5 — <meta http-equiv="refresh" content="0; url=https://ibank-nbg-web.efficientscalp.com/wb" />)
brand impersonation
The redirect destination URL uses the subdomain 'ibank-nbg-web' which strongly mimics NBG (National Bank of Greece) internet banking branding. Combining 'ibank' (common bank portal prefix) with 'nbg' (NBG's ticker/abbreviation) on an unrelated commercial domain ('efficientscalp.com') is a classic brand-impersonation pattern used in banking phishing campaigns. (location: page.html:5 — redirect target https://ibank-nbg-web.efficientscalp.com/wb)
phishing
The overall page structure — a throwaway Firebase app acting as a redirect hop to a domain impersonating a bank's online portal — is characteristic of a phishing kill chain. The Firebase domain provides a trusted TLS certificate and hosting reputation while the actual phishing payload is served at the destination URL, bypassing URL reputation filters. (location: https://kzuqqvru.firebaseapp.com — full page)
credential harvesting
The destination path '/wb' on a domain mimicking NBG internet banking ('ibank-nbg-web.efficientscalp.com') strongly suggests a credential-harvesting landing page designed to capture banking usernames, passwords, and potentially OTP/2FA codes from victims who believe they are accessing their legitimate bank portal. (location: page.html:5 — redirect target path /wb on ibank-nbg-web.efficientscalp.com)
social engineering
The page is rendered in French ('lang="fr"', 'Redirection en cours...') despite targeting what appears to be a Greek bank (NBG). This may indicate targeting of French-speaking NBG customers or diaspora, or use of a generic multilingual phishing kit. The innocuous 'Redirection en cours...' message is designed to suppress user suspicion during the redirect. (location: page.html:2,10 — lang="fr" and visible text 'Redirection en cours...')
hidden content
The meta referrer policy is set to 'no-referrer', suppressing the originating URL from being passed to the destination server. While not malicious on its own, in this context it is used to hide the phishing chain's origin from the landing page operator and forensic analysts, and to prevent detection by referrer-based security controls. (location: page.html:7 — <meta name="referrer" content="no-referrer" />)
curl https://api.brin.sh/domain/kzuqqvru.firebaseapp.comCommon questions teams ask before deciding whether to use this domain in agent workflows.
kzuqqvru.firebaseapp.com currently scores 43/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.