context safety score
A score of 27/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 page is served from hitmaal.com but all canonical URLs, og:url, internal links, and content references point to hitmaal.com.co — a different domain. The canonical tag explicitly redirects SEO authority and user navigation to hitmaal.com.co, indicating the .com domain acts as a redirect/cloaking layer to funnel traffic to the .co domain. (location: page.html:27 — <link rel="canonical" href="https://hitmaal.com.co/" />)
obfuscated code
Obfuscated popunder/ad injection script using base64-encoded CDN URLs stored in array 'c'. The script decodes URLs at runtime via atob() and dynamically injects script tags with fallback chaining across multiple CDN hosts. This is a classic pattern for evading static ad-blockers and delivering malicious or unwanted popunder ads. The hardcoded timestamp check (1798549290000) suggests the obfuscation was designed to expire in the future, allowing long-term silent operation. (location: page.html:17-21 — inline script tagged '<!-- Tssp-->')
malicious redirect
Custom context menu (CCM) script replaces the browser's native right-click menu and injects 11 external adult/piracy site links (mastiwala.com, uffmaal.com, webxseries.to, playmaal.com, ymaza.com, zmaal.net, ymaal.co, fapstory.net, yesmaal.com, xmasti.net). When a user right-clicks and selects any of these items, window.open(url, '_self') navigates the current tab away from the site — a forcible redirect used to drive traffic to affiliate piracy networks. (location: page.html:675-793 — ccm-frontend-js-after script block)
social engineering
Footer copy uses manipulative social proof language ('millions trust HITMaal') and explicitly names competing piracy sites (AagMaal, Webxseries, XMasti, XMaza) to position itself as the superior free streaming destination. The promise of 'no redirects, no hassles' is contradicted by the actual presence of redirect scripts, popunder ad loaders, and a custom context menu that forces navigation away — constituting deceptive user manipulation. (location: page.html:666 — <footer> paragraph)
hidden content
A hidden 1x1 pixel iframe is injected by a Cloudflare challenge script. The iframe is absolutely positioned at top:0/left:0 with visibility:hidden and injects a secondary script (/cdn-cgi/challenge-platform/scripts/jsd/main.js) via dynamically created script elements inside the hidden iframe's document. While Cloudflare bot-detection is legitimate, the pattern of injecting executable code inside a hidden iframe is a known technique for covert script execution invisible to users. (location: page.html:804 — inline script at end of <body>)
brand impersonation
The site impersonates or piggybacks on legitimate OTT platform brands — ULLU, Digi Movieplex, Atrangii, Besharams, BigShots, CinePrime, Hunters, JUGNU, ALTT, Rabbit — by using their trademarked names as navigation categories and SEO keywords to attract users searching for those platforms' paid content, then serving it for free to drive ad/affiliate revenue. (location: page.html:317 — <div class="menu"> navigation links; page.html:24-25 — <title> and meta description)
curl https://api.brin.sh/domain/hitmaal.comCommon questions teams ask before deciding whether to use this domain in agent workflows.
hitmaal.com currently scores 27/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.