context safety score
A score of 39/100 indicates multiple risk signals were detected. This entity shows patterns commonly associated with malicious intent.
brand impersonation
The site impersonates OKX (a major cryptocurrency exchange), referencing '/index/okx/market' API endpoints and replicating OKX's trading interface with wallet, recharge, withdraw, transfer, and VIP sections. The domain 'uvebto.com' has no affiliation with OKX. (location: page.html:109,139 - API endpoints /index/okx/market/type/1.html and /index/okx/market/type/2.html; navigation links to wallet, recharge, withdraw, transfer)
credential harvesting
The page presents login ('/index/passport/login.html') and registration ('/index/passport/signup.html') endpoints on a fraudulent crypto exchange clone. Credentials and personal financial data entered would be harvested by the attacker. (location: page.html:326-328 - footer buttons linking to /index/passport/signup.html and /index/passport/login.html)
phishing
The site is a fully functional fake cryptocurrency exchange (OKX clone) with wallet, deposit (Recargar), withdrawal (Retirar), transfer (Transferir), investment (Inversión), VIP membership, and customer service sections — all designed to lure victims into depositing real cryptocurrency funds that will be stolen. (location: page.html:232-314 - full navigation menu impersonating an exchange; metadata.json domain uvebto.com)
social engineering
The site uses Spanish-language UI ('Página de inicio', 'billetera', 'Recargar', 'Retirar', 'Inversión', 'VIP', 'Registrar', 'Iniciar sesión') to target Spanish-speaking users with a convincing fake trading platform, including live market price feeds cycling every 9 seconds to simulate legitimacy. (location: page.html:180,241,250,258,266,274,282,290,298,306,326-328; JavaScript setInterval calls at lines 168,171)
hidden content
The page title is intentionally left blank ('<title></title>'), concealing the site's identity from browser history, tab previews, and security tools that index page titles. A language redirect script is also loaded silently from '/plugin/swiper/language_redirect.js', which may redirect users based on locale without disclosure. (location: page.html:6 - empty <title> tag; page.html:51 - /plugin/swiper/language_redirect.js script)
malicious redirect
A language redirect script '/plugin/swiper/language_redirect.js' is loaded and executes on page load. This script may silently redirect users to locale-specific phishing variants or track/fingerprint visitors, and its content is not visible in the captured HTML. (location: page.html:51 - <script type='text/javascript' src='/plugin/swiper/language_redirect.js'>)
hidden content
Third-party analytics tracking script loaded from '//sdk.51.la/js-sdk-pro.min.js' (51.la, a Chinese analytics provider) with hardcoded tracking ID '3IzaGTMUSK1viRpW'. This enables silent user fingerprinting, session tracking, and behavioral surveillance of all visitors without disclosure. (location: page.html:53-54 - LA_COLLECT script tag and LA.init() call)
curl https://api.brin.sh/domain/uvebto.comCommon questions teams ask before deciding whether to use this domain in agent workflows.
uvebto.com currently scores 39/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.