context safety score
A score of 45/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
brand impersonation
The domain crummydevioussucculent.com hosts a page that fully impersonates Clickadu s.r.o.'s official privacy policy, using the Clickadu logo (embedded as a base64 SVG), Clickadu branding, company address, and Tax ID. The page is titled 'Operated by Clickadu Advertisement Network' but is served from an unrelated third-party domain, not clickadu.com. (location: page.html:4, page.html:153-155, page.html:159)
social engineering
The page poses as a legitimate privacy/unsubscribe portal for Clickadu push notification subscribers. It provides detailed instructions for managing browser push notification subscriptions, likely used to lure users who received unwanted push notifications into interacting with this third-party-controlled page rather than the legitimate Clickadu domain. (location: page.html:181-253, page-text.txt:31-103)
prompt injection
The page contains a hidden collapsible section (CSS class 'collapse' with 'display:none' by default) containing detailed browser notification manipulation instructions. This hidden content could be used to inject instructions into AI agents crawling/summarizing the page, directing them to guide users through disabling security notifications or manipulating browser settings. (location: page.html:186-253 (id='collapseContainer', class='collapse'))
hidden content
A collapsible div with id='collapseContainer' and class='collapse' is hidden by default via CSS (display:none). It contains step-by-step browser notification manipulation instructions that are not visible to users on page load but are present in the DOM and accessible to crawlers and AI agents. (location: page.html:186, page.html:87-89 (.collapse:not(.show) { display: none; }))
malicious redirect
The unsubscribe button silently POSTs a JSON payload to '/unsubscribe' on the same domain (crummydevioussucculent.com), a domain unrelated to Clickadu. This intercepts user unsubscribe requests that users believe are going to Clickadu, potentially harvesting subscription/device identifiers or confirming active users to the ad network operator. (location: page.html:330-364 (xhr.open POST /unsubscribe))
credential harvesting
The /unsubscribe endpoint receives a POST request with a JSON body containing a timestamp. While minimal, this interaction with an unaffiliated domain under the guise of an official Clickadu privacy page could be used to fingerprint and track users, or to silently collect browser/device metadata sent by the XHR request (cookies, headers). (location: page.html:364 (xhr.send JSON.stringify({ ts: Date.now() })))
curl https://api.brin.sh/domain/crummydevioussucculent.comCommon questions teams ask before deciding whether to use this domain in agent workflows.
crummydevioussucculent.com 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.