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
The page contains a sophisticated geo-fenced and bot-evasion redirect system. Visitors from Tunisia (TN) or Bulgaria (BG) who are NOT identified as security scanners, bots, or researchers are silently redirected to 'https://e-postada.web.app/' — a likely phishing or malicious destination. All other visitors (including those from security vendors, cloud providers, and known scanning IPs) are redirected to google.com as a decoy to evade detection. (location: page.html:1036 — window.location.href = 'https://e-postada.web.app/')
phishing
The redirect target 'https://e-postada.web.app/' is hosted on Firebase (as is the source page), uses a random-looking subdomain with no legitimate branding, and is only served to real human victims in Tunisia and Bulgaria after passing all bot/scanner filters. The name 'e-postada' may impersonate a postal service (e.g., Bulgarian Posts / La Poste Tunisienne), strongly indicating a credential-harvesting phishing page targeting those countries. (location: page.html:1036 — redirect target https://e-postada.web.app/)
brand impersonation
The subdomain 'e-postada' mimics postal service branding ('e-posta' means 'e-mail/post' in several languages including Turkish and Balkan languages). Combined with the exclusive targeting of Bulgaria (BG) and Tunisia (TN), this strongly suggests impersonation of a national postal or parcel delivery service to lure victims into entering credentials or payment information. (location: page.html:1036 — redirect target https://e-postada.web.app/)
social engineering
The page implements a multi-stage anti-analysis system specifically designed to show security researchers, bots, automated scanners, and users from non-target countries a benign redirect to google.com, while only exposing the real malicious payload to human victims in target geographies. This is a deliberate deception technique to evade detection while maximizing victim reach. The provider blacklist explicitly blocks Google, Microsoft, Amazon, Palo Alto Networks, Zscaler, DigitalOcean, and many other security and cloud providers. (location: page.html:28-1044 — checkCountry() and redirectBasedOnBlacklist() logic)
hidden content
The page has no visible content whatsoever (title is 'BG', body is empty except for a script block). The entire malicious functionality is concealed within JavaScript — there is no user-visible UI. The page is a purely invisible redirect gate, making it impossible for a human casually viewing the page to understand its purpose. (location: page.html:1-6 — empty <body> with script-only content; title 'BG')
credential harvesting
An API key for ipbase.com is hardcoded and exposed in the JavaScript: 'ZkTPe6tfZyRAos1REPYuhaPmjcCWxKVwcNGh6ksE'. This key is used to geolocate and profile every visitor. The overall infrastructure (geofenced redirect to a suspicious Firebase app targeting postal-service users) is consistent with a credential harvesting campaign. (location: page.html:22 — xhr.open('GET', 'https://api.ipbase.com/v2/info?apikey=ZkTPe6tfZyRAos1REPYuhaPmjcCWxKVwcNGh6ksE', true))
curl https://api.brin.sh/domain/firebeplyostigtehos.firebaseapp.comCommon questions teams ask before deciding whether to use this domain in agent workflows.
firebeplyostigtehos.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.