context safety score
A score of 34/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
phishing
1 deceptive links where visible host does not match destination host
cloaking
Page checks user-agent for bot/crawler strings to serve different content
cloaking
Page conditionally redirects based on referrer or user-agent
js obfuscation
JavaScript uses Function constructor for runtime code generation
malicious redirect
Two external scripts loaded from 'diagnosedecorationvideotape.com' — a suspicious, obfuscated-looking domain unrelated to any legitimate ad network. One script (code-block-3) uses a heavily obfuscated path with mixed-case characters and underscores: '//diagnosedecorationvideotape.com/gz7dsHq/8S4/-TX-ZLzVzf/Rai1w0Fx/dBy7/_Tf3HLoPcco3qwMY6g/1_eHj3yhr3ZFglHAOB-/kpDXhAZrqU/tDP/7C_liNmGseaj0ev/edaWnRURvhKFFYqe/QFFl/kP1o/Kj3P'. The second script (code-block-2) loads 'invoke.js' from the same domain keyed with '8438ea1a6cfda4427707358311de6ae1'. These scripts execute with full page access and can redirect users, inject pop-ups, or deliver malware payloads. (location: page.html:845 and page.html:954)
obfuscated code
The page embeds custom base64 encode/decode functions (b2a, a2b, b64e, b64d) alongside the AI insertion plugin (Ad Inserter). These functions are used at runtime to decode and inject arbitrary HTML/JavaScript content into the page DOM via 'createContextualFragment'. The b64d function decodes base64 strings and inserts them as live script fragments, making it impossible to statically analyze what code will be executed without runtime evaluation. (location: page.html:969-971 and page-text.txt:826-828)
malicious redirect
The footer copyright link points to 'https://https://t7t-al7zam.com/...' (note the double 'https://' scheme — a URL construction anomaly) redirecting users to an external domain 't7t-al7zam.com' rather than the site's own domain. The 'Contact Us' button also redirects to this external domain. This indicates the site operator is funneling users to a separate third-party site. (location: page.html:941, page.html:925)
social engineering
The site prominently promotes multiple external adult content sites in header, body, and footer widgets with calls-to-action like '>>' directing users to arabgy.com, nafakarab.com, shraraa.com, t7t-al7zam.com, and sokoosoko.com. This affiliate/traffic-funneling pattern is a common social engineering technique to drive users to potentially higher-risk third-party sites without clear disclosure. (location: page.html:912-920, page-text.txt:769-777)
hidden content
The Ad Inserter plugin ('ai-viewport' CSS classes) uses viewport-based display logic with 'display: none !important' and absolute positioning off-screen (top: -1000px, z-index: -9999) for elements with classes 'ai-list-data', 'ai-ip-data', 'ai-filter-check', 'ai-fallback'. These hidden elements are processed at runtime and can contain encoded ad or redirect payloads injected into the visible DOM based on user IP, cookies, referrer, or device type — content invisible to static scanners. (location: page.html:133-134)
obfuscated code
The Ad Inserter plugin stores ad payloads as base64-encoded strings in 'data-code' and 'data-fallback-code' HTML attributes, then decodes and injects them at runtime using b64d() and createContextualFragment(). This allows arbitrary script injection that bypasses static content analysis. The plugin also reads and manipulates cookies ('aiBLOCKS') to track user behavior across sessions and conditionally serve different content. (location: page.html:844-895 (Ad Inserter JS blocks))
social engineering
The Telegram channel 'https://t.me/arab_naar' is listed in the site's schema.org Organization 'sameAs' field, linking the site's official identity to a Telegram channel. Telegram channels associated with adult content aggregators are commonly used to harvest follower data, distribute malware links, or conduct direct social engineering against subscribers. (location: page.html:24 (schema.org JSON-LD, sameAs field))
curl https://api.brin.sh/domain/shrmha.comCommon questions teams ask before deciding whether to use this domain in agent workflows.
shrmha.com currently scores 34/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.