context safety score
A score of 46/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
malicious redirect
The scanned URL is carmudi.com.co (a Colombian automotive marketplace domain), but the page serves content entirely from adiglobal.com.co — a Vietnamese-language online gambling/card game site (Rikvip). The canonical URL, all asset URLs, og:url, and pingback all point to adiglobal.com.co. This is a clear domain hijack or cloaking redirect: visitors to carmudi.com.co are transparently served a different site's content. (location: page.html:1 — <link rel='canonical' href='https://adiglobal.com.co/'>, <link rel='pingback' href='https://adiglobal.com.co/xmlrpc.php'>)
brand impersonation
The page impersonates or parasitizes the carmudi.com.co domain (a known Latin American car classifieds brand) to host and promote the Rikvip online gambling platform. The domain reputation and trust associated with Carmudi is being exploited to lend legitimacy to the gambling site and improve its search engine ranking. (location: metadata.json — domain: carmudi.com.co; page.html:1 — title and og:site_name reference RIKVIP/adiglobal.com.co)
social engineering
The page promotes an online gambling/card game reward-exchange platform (game bài đổi thưởng) using trust-building language: claims of high security, fast transactions, stable operations, and legitimacy. It encourages users to download the app and make deposits ('nạp rút siêu tốc'). This is consistent with social engineering to drive financial engagement on an unlicensed offshore gambling site. (location: page-text.txt:45-46, page.html line 70-71 — promotional content for Rikvip gambling platform)
malicious redirect
All call-to-action buttons and images link to '/mlink/?branchseo=rik-el', a tracking/affiliate redirect path that routes users to the Rikvip gambling platform. This redirect mechanism obscures the final destination and is used to funnel users from the hijacked carmudi.com.co domain to the gambling site. (location: page.html:40,52 — href='/mlink/?branchseo=rik-el' on CTA button images)
hidden content
Multiple images use inline base64-encoded SVG placeholders (lazy-load technique) that replace actual images until JavaScript loads. While this is a common legitimate lazy-load pattern, combined with the domain hijack context it contributes to concealing the true nature of the page during initial load/crawl. The pre-scan context flagged 12 suspicious base64 blobs, all consistent with these SVG placeholders. (location: page.html:34,37,41,53,84,105 — data:image/svg+xml;base64 src attributes on img tags)
curl https://api.brin.sh/domain/carmudi.com.coCommon questions teams ask before deciding whether to use this domain in agent workflows.
carmudi.com.co currently scores 46/100 with a suspicious verdict and medium 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.