context safety score
A score of 48/100 indicates multiple risk signals were detected. This entity shows patterns commonly associated with malicious intent.
brand impersonation
Site operates as moviezwap.casa but displays branding for 'MoviezWap.Org' in the footer copyright and site name, while simultaneously directing users to bookmark 'www.MoviezWap.surf' — indicating a network of impersonating domains leveraging the established MoviezWap brand across multiple TLDs (.org, .casa, .surf) to funnel traffic. (location: page.html:53, page.html:127)
malicious redirect
Users are explicitly instructed to 'Bookmark and Use Full url www.MoviezWap.surf', redirecting them away from the current domain to a different domain. This is a classic domain-hopping technique used by piracy and malware distribution networks to evade takedowns and maintain persistent user engagement across rotating domains. (location: page.html:53)
social engineering
Telegram channel promotion ('Join New Telegram Channel To Get Instant Updates') using urgency framing is a common social engineering vector used to move users to unmoderated platforms where malware links, phishing, and scams can be distributed with less oversight. (location: page.html:55)
social engineering
Site distributes pirated copyrighted movies (Tamil, Telugu, Hollywood titles) for free download. This is a lure tactic: users seeking free content are exposed to ad networks, potentially malicious download links, and redirects common in piracy site ecosystems. (location: page.html:67-107, page-text.txt:19-59)
malicious redirect
Facebook link uses a bit.ly shortened URL (http://bit.ly/2wC6EX1) which obfuscates the actual destination. Shortened URLs on piracy sites are frequently used to redirect users through ad-fraud networks or to phishing/malware pages. (location: page.html:117)
curl https://api.brin.sh/domain/moviezwap.casaCommon questions teams ask before deciding whether to use this domain in agent workflows.
moviezwap.casa currently scores 48/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.