context safety score
A score of 42/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
social engineering
The site operates as a celebrity and influencer image/video leak forum explicitly advertising 'nackt leaks' (nude leaks) and 'unzensierte Welt der Schönen und Reichen' (uncensored world of the rich and beautiful). It solicits user registration to access content involving non-consensual intimate imagery of real, named individuals (celebrities, influencers, streamers). This constitutes social engineering to lure users into participating in distribution of non-consensual content. (location: page.html:22 (title), page.html:655-668 (welcome block), forum categories throughout)
social engineering
The forum contains a dedicated 'Fake-Requests' section (538 threads, 2.9K posts) and 'Deepfakes' section (664 threads, 8.9K posts) explicitly for requesting and distributing AI-generated non-consensual deepfake pornography of named real individuals such as 'Lisa Küppers', 'Yvonne Schönenborn', and others. The 'Software & Guides' subforum provides tutorials titled 'Der Guide für ULTRA realistische (paid) Deepfakes', enabling and normalizing this abuse. (location: page.html:2866-3139 (Deepfakes/Fake-Requests nodes), page.html:2911 (deepfake guide thread title))
hidden content
Thumbnail images throughout the page use a 1x1 transparent PNG as the src attribute (data:image/png;base64,iVBORw0KGgoAAAANSUhEUgAAAAEAAAABCAQAAAC1HAwCAAAAC0lEQVR42mP8Xw8AAoMBgDTD2qgAAAAASUVORK5CYII=) while the actual image is loaded via CSS background-image from external URLs. This pattern decouples the visible image source from the declared src, potentially evading content scanners that only inspect src attributes. (location: page.html:3669, 3717, 3765, 3813, 3861, 3909, 3957, 4005, 4053, 4101 (threadThumbnailWrapper img elements))
hidden content
Cloudflare bot-challenge script injected at end of body creates a hidden 1x1 iframe and dynamically injects a script from '/cdn-cgi/challenge-platform/scripts/jsd/main.js' with obfuscated parameters including base64-encoded values (r:'9d70c7dc8966b612', t:'MTc3MjYyNjI1Nw=='). While this is a standard Cloudflare anti-bot mechanism, the technique of using a hidden iframe to inject scripts is a pattern also used maliciously. (location: page.html:4746 (inline script at end of body))
social engineering
The site uses a tiered membership/gamification system ('Silber Status', 'Gold Status') to gate access to deepfake and explicit NSFW content, incentivizing users to increase engagement and post volume to unlock restricted forums. This exploits psychological reward mechanisms to drive participation in distributing potentially illegal non-consensual imagery. (location: page.html:2620 (Manga/Hentai - Silber Status), page.html:2720 (Transgender - Gold Status), page.html:3069 (Deepfakes - Gold Status), page.html:3169 (AI Models - Gold Status))
curl https://api.brin.sh/domain/celebforum.toCommon questions teams ask before deciding whether to use this domain in agent workflows.
celebforum.to currently scores 42/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.