context safety score
A score of 32/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 (_ionicstorage/_ionickv) and transmits them via postMessage to window.parent with a wildcard origin ('*'). This silently exfiltrates stored credentials and session tokens to any parent frame, enabling cross-origin credential theft when the page is embedded in an iframe. (location: page.html:74-100)
credential harvesting
The message event listener accepts inbound postMessage events from any origin ('*') and writes received token, account, password, and loginType values directly into IndexedDB without any origin validation. An attacker-controlled parent frame can inject arbitrary credentials or overwrite legitimate session data. (location: page.html:85-94)
obfuscated code
window.__APP_CONFIG__.domainInfo contains a very large base64-like encoded string (beginning with '=Q0NlQ0Nl...') embedded inline in the page. The encoding obfuscates the actual configuration and any embedded URLs, commands, or instructions loaded at runtime, preventing static analysis of the true application behavior. (location: page.html:18)
social engineering
Meta description and Open Graph tags in Portuguese promise users they will 'become the next millionaire' ('torne-se o próximo milionário'), a classic get-rich-quick lure used in gambling and investment scams to attract victims to a fraudulent platform. (location: page.html:1-2,11)
prompt injection
The obfuscated __APP_CONFIG__ domainInfo blob is decoded and consumed at runtime by the application JS. Because its contents are not human-readable, it could contain injected instructions targeting AI agents or automated crawlers that process page configuration, including directives to exfiltrate data or alter agent behavior. (location: page.html:18)
malicious redirect
The isInIframe() function checks for the query parameter 'unTopWindow=true' combined with 'domainType' not equal to 'google', and conditionally changes postMessage behavior. This logic suggests the site is designed to operate inside deceptive iframes that masquerade as Google properties while performing token exfiltration. (location: page.html:21-24)
brand impersonation
The site loads the official Telegram Web App JS SDK (telegram.org/js/telegram-web-app.js) to present itself as a legitimate Telegram Mini App. The randomlooking domain 'vbkuaaqa4.com' (298 days old) combined with Telegram SDK integration is a common pattern for fake Telegram gambling/phishing mini-apps impersonating legitimate services. (location: page.html:115)
phishing
The domain 'vbkuaaqa4.com' is a randomly-generated, meaningless string domain (298 days old) hosting what appears to be a gambling/lottery platform branded '85K'. Such throwaway domains with lottery lures are routinely used for phishing campaigns to harvest payment and identity information under the guise of prize winnings. (location: metadata.json, page.html:6-7)
hidden content
Assets are loaded from the external CDN domain 'upload-us.f-1-g-h.com' for all images and app icons. This obfuscated CDN hostname decouples the visible brand identity from the hosting infrastructure and allows dynamic swapping of logos or images (e.g., to impersonate a different brand) without modifying the HTML. (location: page.html:3-5,13-17)
curl https://api.brin.sh/domain/vbkuaaqa4.comCommon questions teams ask before deciding whether to use this domain in agent workflows.
vbkuaaqa4.com currently scores 32/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.