context safety score
A score of 49/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
script/meta redirect patterns detected in page source
malicious redirect
The page is served under domain 5movierulz.condos but the Cloudflare challenge zone (cZone) is set to 'www.5movierulz.bargains', indicating the canonical/actual site operates under a different domain. This cross-domain mismatch is characteristic of domain-hopping infrastructure used by piracy/malware distribution networks to evade blocklists and redirect users across rotating domains. (location: page.html: _cf_chl_opt.cZone = 'www.5movierulz.bargains')
brand impersonation
The domain '5movierulz.condos' (and its associated domain 'www.5movierulz.bargains') impersonates the well-known piracy brand 'MovieRulz'. These sites are consistently associated with malware distribution, forced redirects to ad/scam pages, and credential harvesting. The use of multiple TLDs (.condos, .bargains) is a known evasion tactic employed by this network after repeated domain seizures. (location: metadata.json: domain=5movierulz.condos; page.html: cZone=www.5movierulz.bargains)
malicious redirect
A meta http-equiv refresh tag is present with a 360-second countdown, which will silently redirect the browser without user interaction after the Cloudflare challenge phase. This is a common technique to chain users through intermediate pages before landing on ad-fraud, malware, or phishing destinations. (location: page.html: <meta http-equiv="refresh" content="360">)
hidden content
The page sets meta robots to 'noindex,nofollow', suppressing crawler and search engine visibility of the actual page content. Combined with the Cloudflare managed challenge gate, this hides the true destination and payloads from automated scanners and indexers, a deliberate obfuscation technique used by malicious sites. (location: page.html: <meta name="robots" content="noindex,nofollow">)
curl https://api.brin.sh/domain/5movierulz.condosCommon questions teams ask before deciding whether to use this domain in agent workflows.
5movierulz.condos currently scores 49/100 with a suspicious verdict and medium 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.