context safety score
A score of 38/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
js obfuscation
JavaScript contains heavy hex-escape encoding typical of obfuscation
obfuscated code
Two instances of heavily obfuscated JavaScript using hex-encoded strings (\x30\x78... notation) and a self-invoking array-rotation anti-tamper loop. The decoded logic checks window.location.hostname and, if the visitor is NOT on hot-sex-tube.com, dynamically injects a <script> tag pointing to //hot-sex-tube.com/js.php?h=<current_href>|<token>, effectively exfiltrating the visitor's full URL and a session token to a remote endpoint. This is a classic cloaking/traffic-stealing payload used in malvertising chains. (location: page.html lines 1110 and also rendered in page-text.txt line 1078 (inline <script> block near #footer))
malicious redirect
All outbound video links are routed through /o.php with a base64-encoded destination URL in the 'u' parameter (e.g. u=aHR0cHM6Ly94aC5wYXJ0bmVycy94L...). This redirect layer conceals the true destination from scanners and users, enabling the operator to silently swap destinations, redirect to malware, phishing pages, or forced-download payloads without changing visible HTML. The 'Live Sex Cams' nav link routes through s.zlinkb.com/d.php?z=4948590 — an unrelated third-party redirect broker. (location: page.html lines 44, 467, 475, 483, 491, 499, 507, etc. (all /o.php?id=...&u=<base64> href attributes))
brand impersonation
The site prominently features navigation links and a dedicated category labeled 'BRAZZERS' (brazzers.com affiliate) and 'Mofos' (mofos.com affiliate) with tracking-laden affiliate URLs containing encoded ATS tokens (eyJhIjoxMzE1OSwiYyI6NDYyMjgwMTgsIm4iOjE0...base64). These links impersonate well-known brands to drive affiliate traffic, but the ATS tokens and encoded parameters obscure the true referral chain and could be used in fraudulent commission schemes. (location: page.html lines 45-47 (nav menu affiliate links to brazzersnetwork.com, iknowthatgirl.com, babesnetwork.com))
hidden content
The page sets <meta name='referrer' content='unsafe-url'> and <base target='_blank'>, ensuring all outbound clicks leak the full referrer URL (including any session tokens in the URL) to third-party destinations, and all links open in new tabs bypassing browser back-navigation protections. Combined with dns-prefetch and preconnect to tn.hot-sex-tube.com, this establishes covert pre-loading of third-party resources before user interaction. (location: page.html lines 13-17 (meta referrer, base target, dns-prefetch, preconnect headers))
social engineering
The page header displays 'BOOKMARK US DUE TO REGULAR UPDATES!' — a social engineering prompt designed to establish persistent browser access. Combined with document.cookie='js=1; path=/; domain=.hot-sex-tube.com' set via inline JavaScript (tracking all subdomains), this harvests a persistent cookie across the entire .hot-sex-tube.com domain to track users across sessions. (location: page.html lines 23 (bookmark prompt), line 1117 (cookie-setting script))
prompt injection
The obfuscated script payload appends a pipe-delimited token string ('b0c90356ef9b0ae9066e604871310870|1772627507') to the exfiltrated URL when calling /js.php. This token format matches patterns used in bot-fingerprinting and AI agent tracking systems, where the injected identifier is used to correlate automated crawler/agent traffic with specific sessions — a technique targeting headless browsers and AI web agents specifically. (location: page.html line 1110 (obfuscated script argument: 'b0c90356ef9b0ae9066e604871310870|1772627507'))
curl https://api.brin.sh/domain/hot-sex-tube.comCommon questions teams ask before deciding whether to use this domain in agent workflows.
hot-sex-tube.com currently scores 38/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.