context safety score
A score of 33/100 indicates multiple risk signals were detected. This entity shows patterns commonly associated with malicious intent.
encoded payload
suspicious base64-like blobs detected in page content
cloaking
Page conditionally redirects based on referrer or user-agent
credential harvesting
JavaScript reads 'token', 'account', 'password', and 'loginType' from IndexedDB (_ionicstorage/_ionickv) and exfiltrates them via postMessage to a parent window with no origin validation (wildcard '*'). This harvests stored credentials and session tokens cross-origin. (location: page.html:74-93)
credential harvesting
The initAccount function stores received token, account, password, and loginType values into IndexedDB when a 'fixToken' postMessage is received from any origin (no origin check on event.data). This enables credential injection and harvesting via cross-origin iframe messaging. (location: page.html:85-95)
social engineering
Site promotes a gambling platform (JILIKK.VIP) with deceptive sign-up bonus lure: 'get a free random sign up bonus and withdraw it after one round of betting.' This is a classic social engineering hook to draw users into a gambling site and obtain their financial credentials. (location: page.html:1-2 (meta description))
brand impersonation
The domain mi3jn00u.com (91 days old, random-looking) hosts a site branded as 'JILIKK.VIP', masking the true domain identity. The mismatch between the hosting domain and the branded site name is consistent with brand impersonation used to evade blocklists while appearing legitimate. (location: page.html:6-9 (og:site_name, og:url))
obfuscated code
The window.__APP_CONFIG__ object contains a 'domainInfo' property with a very long base64/custom-encoded string (starting 'EdTJEdTJEdTJ...') that is not human-readable. This obfuscated payload is loaded at page init and likely contains server configuration, redirect targets, or exfiltration endpoints hidden from static analysis. (location: page.html:18 (window.__APP_CONFIG__.domainInfo))
malicious redirect
The isInIframe() function checks for URL parameters 'unTopWindow=true' and 'domainType!=google' to determine iframe context, then conditionally posts credentials to parent. This logic is designed to detect and exploit iframe embedding scenarios for cross-site token relay or redirect abuse. (location: page.html:21-24)
social engineering
The site integrates Telegram Web App JS (telegram.org/js/telegram-web-app.js), suggesting it targets Telegram users and may use Telegram bot/mini-app social engineering vectors to lure victims into the gambling/credential harvesting flow. (location: page.html:115 (script src telegram-web-app.js))
phishing
The domain is 91 days old with a random alphanumeric name (mi3jn00u.com), uses a DV TLS certificate from Google Trust Services, and impersonates the JILIKK.VIP brand. These are hallmarks of a phishing infrastructure: short-lived throwaway domain with free TLS presenting a fake branded gambling site to harvest user credentials. (location: metadata.json (domain_age_days:91), page.html:6-9)
curl https://api.brin.sh/domain/mi3jn00u.comCommon questions teams ask before deciding whether to use this domain in agent workflows.
mi3jn00u.com currently scores 33/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.