context safety score
A score of 43/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
js obfuscation
JavaScript uses Function constructor for runtime code generation
obfuscated code
Main ad script loaded from obfuscated filename '/afon/azazaz7.10.13.df04a0f24d7780c32f760f12117cd73e.js' with variable name 'adver' explicitly set to '7.10.13.obfuscated.js' in vONidVai config object. Obfuscation flag is self-declared in the source. (location: page.html:60-62)
obfuscated code
Inline script contains minified/obfuscated JavaScript with single-character variable names (t, e, n, r, o, i, c) dynamically building and injecting a script element for the ad popunder system via 'vmh637tsxg.js'. (location: page.html:65)
malicious redirect
Popunder/tabunder ad system configured to open new tabs on user interaction with video player elements. Uses 'tabunder' type with force_url pointing to external ad networks (kts.bartcons.com, s.pemsrv.com). Frequency resets aggressively and binds to virtually all clickable elements including 'body' in some modes. (location: page.html:326-373)
malicious redirect
Push notification subscription interstitial configured with directLink 'https://online-hd.amazingcontent.site/?tag_id=93577&cl=3&click=1' embedded in two push spot configs. This redirects users who interact with the push subscription prompt to a third-party site. (location: page.html:64)
social engineering
'UNLOCK FULL' and 'FULL VIDEO HERE' button labels used as CTAs that redirect users to affiliate/pay sites (fhgte.com, enter.javhd.com). The button text implies content is locked and tricks users into clicking through to external paid sites. (location: page.html:73-85)
social engineering
Age verification bypass logic: when referrer is not empty and URL contains promo/source params, age gate is silently bypassed by setting localStorage '_agv'=1. This circumvents age verification controls programmatically. (location: page.html:143-150)
social engineering
Tab-link ads use emoji-laden titles ('🔥Uncensored JavHD', '🍑AI Undress Porn💦', '🔥AI porn') targeting users with sensational/misleading labels to drive affiliate clicks to javhd-trk.com, cmonbae.com, and candyai.gg. (location: page.html:949-1006)
hidden content
DIV#app contains only '<i style="font-size:0.1px">...</i>' — a near-invisible inline element (0.1px font) used as placeholder. The actual content is injected dynamically via JavaScript, hiding page structure from static analysis and scrapers. (location: page.html:1021)
hidden content
window._hidden_channels = ['51'] sets a hidden channel identifier in global scope, used to suppress or modify ad delivery for specific traffic segments without visible indication to users. (location: page.html:53-54)
hidden content
Client Hints (sec-ch-ua, sec-ch-ua-platform, sec-ch-ua-full-version-list, etc.) delegated to tsyndicate.com via http-equiv delegate-ch meta tag. This silently shares detailed browser/platform fingerprint data with a third-party ad syndication domain. (location: page.html:51)
malicious redirect
Hardlink (direct_link) ad format loaded dynamically via AdManager spot 84723; links received via callback 'on_links_recived' are injected into page links, transparently replacing navigation targets with ad network URLs without user awareness. (location: page.html:735-748)
malicious redirect
Conditional VAST ad URL 'https://kts.sensitiveclick.com/in/959/?katds_ep=...' injected into video player via pl3748.playAd() when URL contains '755071', using a long obfuscated token parameter. This silently hijacks the video ad slot for specific traffic. (location: page.html:939-943)
social engineering
Right-click (button===2) suppressed via stopImmediatePropagation on all click events, preventing users from inspecting links or opening context menus on ad elements — a common technique to hinder user awareness of redirect destinations. (location: page.html:824-826)
curl https://api.brin.sh/domain/vjav.comCommon questions teams ask before deciding whether to use this domain in agent workflows.
vjav.com currently scores 43/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.