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
The initAccount() function reads 'token', 'account', 'password', and 'loginType' from IndexedDB and transmits them via postMessage to a parent window with a wildcard origin ('*'). This allows any cross-origin parent frame to receive sensitive credentials including plaintext passwords. (location: page.html:81-93)
credential harvesting
The page stores and retrieves plaintext passwords in IndexedDB (key: 'password') and transmits them cross-origin. Storing plaintext credentials client-side and exfiltrating them via postMessage with no origin validation is a severe credential harvesting vector. (location: page.html:89)
social engineering
The site impersonates a gambling/bonus platform (JiLiSS.VIP) using a randomized-looking domain (od6x32ve.com) only 144 days old. It lures users with 'free random sign up bonus' messaging to harvest account credentials under the guise of a VIP gambling platform. (location: page.html:1-8, metadata.json)
brand impersonation
The page presents itself as 'JiLiSS.VIP' while hosted on the unrelated domain od6x32ve.com. The og:url meta tag references 'od6x32ve.com:2087' while all branding references JiLiSS.VIP, indicating the real brand domain is being impersonated or proxied through this throwaway domain. (location: page.html:6-9)
obfuscated code
The window.__APP_CONFIG__.domainInfo value is a heavily base64/obfuscated encoded string of significant length. This obfuscated blob conceals the true application configuration, likely including backend API endpoints, redirect targets, or operational parameters that cannot be inspected without decoding. (location: page.html:18)
malicious redirect
The isInIframe() function checks for query parameters 'unTopWindow=true' and 'domainType!=google', enabling conditional behavior when the page is embedded in an iframe. This is consistent with clickjacking or redirect-chaining infrastructure where the page behaves differently depending on how it is framed. (location: page.html:21-24)
phishing
The domain od6x32ve.com is a randomized, low-trust domain (144 days old, unknown hosting reputation) hosting a gambling sign-up flow with credential collection. The combination of a disposable-looking domain, bonus lures, and credential storage/exfiltration is consistent with a phishing operation targeting gambling platform users. (location: metadata.json, page.html:1-18)
social engineering
Telegram Web App JavaScript SDK is loaded (telegram.org/js/telegram-web-app.js), integrating Telegram Mini App capabilities. This is commonly used in social engineering campaigns to reach victims via Telegram bots or channels, lending false legitimacy to the gambling lure. (location: page.html:115)
curl https://api.brin.sh/domain/od6x32ve.comCommon questions teams ask before deciding whether to use this domain in agent workflows.
od6x32ve.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.