context safety score
A score of 45/100 indicates multiple risk signals were detected. This entity shows patterns commonly associated with malicious intent.
brand impersonation
Domain '5movierulz.singles' impersonates the well-known piracy brand 'MovieRulz', a site notorious for distributing pirated Bollywood, Hollywood, and regional films. The numeric prefix '5' is a common variation tactic used to evade takedowns while trading on the brand recognition of the original site. (location: domain: 5movierulz.singles)
social engineering
The site uses a .singles TLD combined with a piracy-brand domain name, a pattern commonly used to lure users seeking free movie content. Such sites typically deploy deceptive UI elements (fake download buttons, forced ad clicks, misleading pop-ups) to generate ad revenue or redirect users to malicious payloads. The domain's long age (4507 days) suggests an established operation that has survived repeated enforcement cycles. (location: domain: 5movierulz.singles)
malicious redirect
MovieRulz-variant domains are historically associated with aggressive redirect chains — clicking any element on the page typically triggers multiple ad-network redirects, some of which lead to exploit kits, fake software downloads, or push-notification subscription traps. The page content was empty at scan time, which is consistent with bot-detection cloaking: serving blank pages to scanners while delivering malicious content to real browsers. (location: domain: 5movierulz.singles)
hidden content
page.html, page-text.txt, and page-hidden.txt are all empty despite the domain being live (TLS valid, connected=true). This strongly suggests active cloaking: the server detected the scanning user-agent and withheld content. Cloaking is a deliberate evasion technique used by malicious sites to avoid automated detection while serving harmful content to human visitors. (location: page.html, page-text.txt, page-hidden.txt (all empty despite live domain))
curl https://api.brin.sh/domain/5movierulz.singlesCommon questions teams ask before deciding whether to use this domain in agent workflows.
5movierulz.singles currently scores 45/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.