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
JavaScript on page extracts the URL fragment (hash) and immediately redirects the browser to a suspicious external domain 'hutchinsonmedicamentsandaids.work.gd' appending the hash value as an 'ext_user' parameter. The comment '//PUT YOUR MAIN LINK HERE//' is a phishing kit builder artifact indicating this is a configured phishing relay/redirector. (location: page.html:17)
credential harvesting
The redirect destination 'hutchinsonmedicamentsandaids.work.gd/koreanspec/?ext_user=' receives an email address (or other identifier) extracted from the URL hash and passes it as a query parameter to the downstream phishing site, enabling pre-population of harvesting forms with victim email addresses. (location: page.html:13-17)
phishing
The page functions as an open redirector in a phishing chain: a trusted-looking Firebase URL (kureshnameshindex.firebaseapp.com) is used to disguise a redirect to a suspicious .work.gd domain. This technique abuses the reputation of Google Firebase to bypass email security filters and deceive recipients into trusting the initial link. (location: page.html:3-20)
social engineering
Use of a legitimate Google Firebase domain (firebaseapp.com) as the entry point in a redirect chain is a deliberate trust-laundering technique. Victims clicking a link to a Google-hosted domain are less likely to be suspicious before being silently redirected to the malicious destination. (location: metadata.json:domain, page.html:17)
hidden content
The page body is completely empty and renders no visible content to the user (page-text.txt is blank). The entire malicious functionality is concealed within a script tag in the head, making the page invisible to casual inspection and to users with JavaScript disabled — the redirect is the sole purpose of the page. (location: page.html:22-24, page-text.txt)
curl https://api.brin.sh/domain/kureshnameshindex.firebaseapp.comCommon questions teams ask before deciding whether to use this domain in agent workflows.
kureshnameshindex.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.