context safety score
A score of 40/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 checks user-agent for bot/crawler strings to serve different content
js obfuscation
JavaScript uses Function constructor for runtime code generation
brand impersonation
The page meta description explicitly mimics Facebook's platform language ('Create an account or log into Vevioz. Connect with friends, family and other people you know. Share photos and videos, send messages and get updates.') — a near-verbatim copy of Facebook's own homepage description. The site uses Facebook's exact brand color (#1877f2) pervasively throughout all UI elements, replicating Facebook's visual identity. (location: page.html:7, page.html:163-467)
brand impersonation
The site loads the official Facebook JS SDK (connect.facebook.net/en_US/sdk.js) and Google Sign-In SDK, presenting OAuth login flows that may confuse users into believing they are interacting with or authorizing Facebook/Google directly, while credentials and tokens are processed by vevioz.com servers. (location: page.html:474)
hidden content
A Yandex Metrika tracking pixel is rendered off-screen using 'position:absolute; inset-inline-start:-9999px;' — a classic technique to hide tracking images from visible content while still firing the beacon. This silently exfiltrates visitor data to Yandex servers (mc.yandex.ru). (location: page.html:787)
hidden content
A second footer div is present in the DOM with 'display: none' styling, containing duplicate navigation links. While likely a UI pattern, hidden duplicate DOM structures can be used to conceal content or inject links not visible to users. (location: page.html:884)
credential harvesting
The page embeds a Google One Tap sign-in widget (data-login_uri pointing to vevioz.com/login-with.php?provider=Google) with data-cancel_on_tap_outside='false', making it persistent and harder to dismiss. This is configured to silently receive Google OAuth tokens on the vevioz.com backend, potentially harvesting Google identity tokens. (location: page.html:760-766)
social engineering
The page displays a maintenance message ('We'll be back soon!') while simultaneously loading full social platform infrastructure (socket.io, Agora RTC, Facebook SDK, payment modals, story viewers, chat systems). This discrepancy between stated maintenance state and actual loaded functionality is deceptive and could be used to mislead users or automated scanners about the true nature of the page. (location: page.html:849-856, page.html:477-748)
curl https://api.brin.sh/domain/vevioz.comCommon questions teams ask before deciding whether to use this domain in agent workflows.
vevioz.com currently scores 40/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.