context safety score
A score of 31/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 string obfuscation technique (splitting a long string, reducing with alternating index offsets, then splitting on 'z') to reconstruct and execute API names at runtime. It manipulates document methods, overrides localStorage, intercepts querySelector calls, and creates hidden iframes — classic obfuscation patterns used in malicious ad injectors, clickjacking, and data exfiltration scripts. (location: page.html:65-67 (hidden div with data-cfasync=false script))
hidden content
Two separate hidden div containers (style='display:none') wrap injected scripts including the obfuscated code block and three Google Analytics tracking tags (UA-269945118-1, G-6ZDPCTTMZN, UA-269945118-2). Hiding analytics and executable scripts inside display:none divs is a concealment technique to prevent casual inspection while still executing code. (location: page.html:65-67 and page.html:1371-1409)
malicious redirect
The page is served from topcinema.cam but all canonical URLs, asset URLs, internal links, schema.org data, and the HomeURL JavaScript variable all point to topcinema.fan. The .cam domain is acting as a transparent proxy or typosquat mirror of topcinema.fan, silently funneling traffic. Users and crawlers believe they are on .cam but all resources and navigation lead to .fan, enabling SEO manipulation and potential session/cookie hijacking between domains. (location: page.html:45 (canonical href=https://topcinema.fan), metadata.json (url=https://topcinema.cam), page.html:1421 (HomeURL=https://topcinema.fan))
brand impersonation
The site uses the .cam TLD (topcinema.cam) while fully impersonating topcinema.fan — including its branding, logo, theme assets, content, and canonical URL. The .cam TLD is commonly associated with deceptive or adult-content domains and is used here to intercept users searching for topcinema.fan, constituting brand impersonation of the legitimate topcinema.fan property. (location: metadata.json (domain=topcinema.cam), page.html:114-117 (Logo--Area linking to topcinema.fan))
obfuscated code
The obfuscated script overrides core document methods (querySelector, getElementById, etc.) by proxying them through a hidden iframe's window object. It also intercepts document.createElement to rewrite element IDs using a randomly generated key, effectively fingerprinting or isolating the document context. This is a known technique used in malvertising and anti-debugging payloads. (location: page.html:66 (inline obfuscated script, iframe proxy and document method override section))
curl https://api.brin.sh/domain/topcinema.camCommon questions teams ask before deciding whether to use this domain in agent workflows.
topcinema.cam currently scores 31/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.