context safety score
A score of 44/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 uses Function constructor for runtime code generation
credential harvesting
A WordPress login form is embedded directly on the homepage sidebar, collecting username and password credentials via POST to https://arabhubx.site/wp-login.php. The form is presented on an adult content site where users may not expect account credential submission, increasing risk of inadvertent credential exposure. (location: page.html:897-905, sidebar login widget #mars-loginform-widget-1)
malicious redirect
Navigation menu contains an outbound link to https://theporndude.com/ar (third-party domain) labeled 'مواقع سكس' (porn sites directory). This external link redirects users away from the site to a third-party aggregator, which could chain to further redirects or malicious content. The link also appears in the footer body text. (location: page.html:188, page.html:871)
malicious redirect
Footer body text links reference a different domain, https://www.arabhub-sex.site/, which is distinct from the page's domain arabhubx.site. These links (to arabhub-sex.site for Egyptian, Lebanese, Moroccan, Iraqi, Algerian, Tunisian, Saudi, Libyan content) redirect users to a separate domain that may be operated for tracking, monetization, or distribution of malicious content. (location: page.html:870-871)
hidden content
A Cloudflare challenge script is injected via a hidden 1x1 pixel invisible iframe appended to the document body at runtime. The iframe dynamically writes and executes a script loading '/cdn-cgi/challenge-platform/scripts/jsd/main.js' with an encoded parameter (t='MTc3MjYxNjI1MA=='). This pattern is used by Cloudflare Bot Management but can also be abused to fingerprint, track, or challenge users covertly without their knowledge. (location: page.html:1024 (inline script, bottom of body))
social engineering
The site employs bot-blocking JavaScript that detects Facebook crawler user agents (facebookexternalhit, facebot) and stops page rendering for those agents while displaying normal content to human visitors. This cloaking technique serves different content to automated crawlers versus real users, a common social engineering and evasion tactic used to hide true content from security scanners and social media preview tools. (location: page.html:33-39)
hidden content
Lazy-loaded images use inline SVG placeholders (data:image/svg+xml base64) as src attributes to defer actual image loading. While standard performance practice, combined with the cloaking bot-detection script, this pattern can be used to serve different image content to bots versus humans, making automated content analysis unreliable. (location: page.html:253, 271, 289, 307, 325 (multiple lazy-load image instances))
brand impersonation
The site presents itself as 'arabhub' (og:site_name, page title branding) but operates on the domain arabhubx.site — the 'x' suffix is a common typosquatting or brand-variation technique used to impersonate or siphon traffic from an established brand (arabhub). The footer also references 'موقع عرب سكس هوب' (Arab Sex Hub website) and links to the separate arabhub-sex.site domain, suggesting a network of related sites under a loosely consistent brand umbrella. (location: page.html:62-65, page.html:951)
curl https://api.brin.sh/domain/arabhubx.siteCommon questions teams ask before deciding whether to use this domain in agent workflows.
arabhubx.site currently scores 44/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.