context safety score
A score of 30/100 indicates multiple risk signals were detected. This entity shows patterns commonly associated with malicious intent.
hidden instruction
high hidden content ratio detected in DOM
phishing
The domain deliveryhero.io serves a pixel-perfect clone of the Google Sign-In page (accounts.google.com/v3/signin/) with <base href="https://accounts.google.com/v3/signin/"> to spoof the Google login UI on a non-Google domain, deceiving users into believing they are authenticating with Google. (location: page.html:1 — <base href="https://accounts.google.com/v3/signin/">)
brand impersonation
The page fully replicates Google's sign-in UI including Google branding, styling, scripts, and layout (Sign in with your Google Account, email/phone field, Next button, Create account link) while being served from deliveryhero.io, not google.com. (location: page.html and page-text.txt — visible text: 'Sign in Use your Google Account Email or phone')
credential harvesting
A fully functional Google login form is hosted on deliveryhero.io. Credentials submitted are directed via the 'continue' parameter to https://sites.google.com/deliveryhero.io/engineeringops, indicating credential interception before or after forwarding to the attacker-controlled Google Site. (location: page.html:91 — <a href="/lifecycle/flows/signup?continue=https://sites.google.com/deliveryhero.io/engineeringops&...">, form action implicitly targets accounts.google.com base)
malicious redirect
After credential submission, the page redirects users to https://sites.google.com/deliveryhero.io/engineeringops via the 'continue' and 'followup' query parameters — an attacker-controlled Google Sites page used to provide a convincing post-login landing page and mask the credential theft. (location: page.html:91 — continue=https://sites.google.com/deliveryhero.io/engineeringops&followup=https://sites.google.com/deliveryhero.io/engineeringops)
obfuscated code
The page contains heavily obfuscated JavaScript using numeric state-machine control-flow flattening (while loops with integer dispatch variables), mangled single-character variable names, and base64-encoded source maps embedded inline. This obfuscation pattern exceeds standard minification and is consistent with phishing kit code designed to evade automated analysis. (location: page.html:16 and page-text.txt:2 — function J with p=69; while(p!=20) state machine pattern and base64 sourceMappingURL)
hidden content
The JavaScript dynamically creates hidden iframes (L.style.display=B where B is set to a hidden/none value) and loads attacker-controlled URLs into them in a polling loop via setInterval, used for fingerprinting visitors or detecting/evading security scanners without any visible UI element. (location: page.html:16 — F=function(...){...L=document.createElement('iframe')...L.style.display=B...L.src=Y...setInterval(...))
curl https://api.brin.sh/domain/deliveryhero.ioCommon questions teams ask before deciding whether to use this domain in agent workflows.
deliveryhero.io currently scores 30/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.