context safety score
A score of 30/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
js obfuscation
JavaScript uses Function constructor for runtime code generation
obfuscated code
A heavily obfuscated JavaScript block is injected inside a hidden div (display:none). The code uses a character-interleaving obfuscation technique to reconstruct function names at runtime (createElement, localStorage, setItem, getItem, removeItem, clearStorage, addEventListener, encodeURIComponent, etc.) and then monkey-patches core DOM APIs (document.createElement, document.getElementById, document.querySelector, etc.) inside a sandboxed iframe. This pattern is consistent with anti-analysis evasion, fingerprinting, or covert data exfiltration and is characteristic of malicious ad-injection or tracking scripts that evade static detection. (location: page.html:65-67, hidden div wrapping obfuscated script block)
hidden content
The obfuscated script block and three separate Google Analytics tracking tags (UA-269945118-1, G-6ZDPCTTMZN, UA-269945118-2) are all wrapped inside a <div style="display:none;"> element at the bottom of the page. Hiding analytics and executable JavaScript from view is anomalous and consistent with covert tracking or payload concealment. (location: page.html:1371-1409, <div style="display: none;"> containing all analytics scripts)
malicious redirect
The page is served from topcinema.media but all internal links, canonical tag, logo href, schema.org URLs, font/asset references, and AJAX endpoints point exclusively to topcinema.fan. The canonical tag explicitly declares the authoritative URL as https://topcinema.fan. The .media domain appears to be a shadow/mirror domain silently forwarding users and bots to topcinema.fan, which is a redirect/cloaking pattern commonly used to siphon SEO authority, evade blocklists, or stage drive-by attacks from a disposable domain. (location: page.html:45 (canonical), page.html:9-14 (font src), page.html:114 (logo href), page.html:1421-1424 (JS vars))
brand impersonation
The site reproduces and aggregates copyrighted content from Netflix, Disney+, Amazon Prime and other streaming platforms (Stranger Things, Loki, Captain America, Avatar, Venom, Secret Invasion, etc.) without authorization, explicitly labeling them as available for free streaming and download. Menu items directly reference 'افلام نتفليكس' (Netflix movies) and 'اجنبي نتفليكس' (Netflix foreign series), trading on Netflix and other brand names to attract users to an unlicensed piracy platform. (location: page.html:80, 110, 129, 137, 1195-1198 (Netflix-branded menu and section headings))
social engineering
The site offers a 'العضوية المميزة' (Premium Membership) call-to-action link with an empty href attribute. Clicking it leads nowhere currently, but this pattern is a common setup for a future credential-harvesting or payment-collection page, enticing users to register or pay for premium access to pirated content. (location: page.html:200, <a href="" class="PremiumUser"> العضوية المميزة</a>)
curl https://api.brin.sh/domain/topcinema.mediaCommon questions teams ask before deciding whether to use this domain in agent workflows.
topcinema.media currently scores 30/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.