context safety score
A score of 36/100 indicates multiple risk signals were detected. This entity shows patterns commonly associated with malicious intent.
phishing
The page presents a login form in Arabic asking for email, username, or phone number plus password. The domain 'haniirohek.com' is a nonsensical/random-looking name with no clear legitimate brand identity, consistent with a phishing kit designed to harvest credentials under a generic banking/service facade (title 'BFS Hanii rohek'). The form POSTs credentials to /login on the same suspicious domain. (location: page.html:92-128, page.html:13)
credential harvesting
The login form collects username/email/phone and password fields and submits them via POST to /login. The JavaScript also reads 'auth-token' from localStorage and injects it as a hidden field before submission, potentially exfiltrating stored authentication tokens along with credentials. (location: page.html:93, page.html:148, page.html:92-153)
credential harvesting
The submitForm() JavaScript reads the localStorage 'auth-token' value and populates a hidden input field named 'auth_token' before form submission. This exfiltrates any stored auth token from the victim's browser alongside the harvested username and password. (location: page.html:145-154)
brand impersonation
The page title 'BFS Hanii rohek' and the domain 'haniirohek.com' appear to impersonate or mimic a financial/banking service (BFS likely stands for a banking or financial service brand). The Arabic-language login interface with 'Welcome' and 'Please sign in to your account' messaging is a common pattern in phishing kits targeting Arabic-speaking users of financial platforms. (location: page.html:13, page.html:87-90)
social engineering
The page uses Arabic language targeting ('مرحبا بكم', 'يرجى تسجيل الدخول إلى الحساب الخاص بك') with a 'Remember me' option and 'Forgot password' link to create a convincing, trust-inducing login experience designed to lower victim suspicion and encourage credential entry on a fraudulent site. (location: page.html:87-127)
hidden content
A hidden input field named 'auth_token' with no initial value is present in the form. Its value is silently populated by JavaScript from localStorage before submission, making the token exfiltration invisible to the user and not apparent from inspecting the static HTML alone. (location: page.html:93)
curl https://api.brin.sh/domain/haniirohek.comCommon questions teams ask before deciding whether to use this domain in agent workflows.
haniirohek.com currently scores 36/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.