context safety score
A score of 36/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
cloaking
Page checks user-agent for bot/crawler strings to serve different content
cloaking
Page conditionally redirects based on referrer or user-agent
js obfuscation
JavaScript uses Function constructor for runtime code generation
obfuscated code
Heavily obfuscated popunder ad script using base64-encoded URLs (atob), encoded strings in an array, and a fallback chain loader. The script at line 326 dynamically decodes and injects scripts from multiple CDN domains (betteradsystem.com, d2kk0o3fr7ed01.cloudfront.net, tkqltqpjokry.com, tkyottkuxignq.com) with a Caesar-cipher-like rotation applied to the source strings. This pattern is consistent with popunder/redirect ad malware frameworks that evade static detection. (location: page.html:324-328 (inline script, data-cfasync=false))
malicious redirect
Script loaded from pubonrace.com (a known popunder/redirect ad network) injected both as a top-level async script and via a deferred banner loader that checks localStorage view counts to delay triggering. The domain pubonrace.com is associated with aggressive redirect and popunder ad delivery that can redirect users to phishing, scam, or malware-distribution pages. (location: page.html:323 and page.html:938 (pubonrace.com script tags))
obfuscated code
Second heavily obfuscated inline script using decodeURI with percent-encoded payload, combined with a positional Caesar cipher (charCodeAt offset by loop index mod 95), string-index slicing, and dynamic script element creation. The decoded payload constructs and injects third-party ad/tracker scripts at runtime, concealing actual target domains from static analysis. (location: page.html:371 (large inline script, data-cfasync=false, immediately after navbar))
malicious redirect
Third-party ad script loaded from carbonfeverthink.com with dynamic error/load callbacks (onerror/onload calling qnijwqit()). carbonfeverthink.com is a low-reputation ad network domain associated with intrusive redirect and popunder campaigns. The callback pattern suggests fallback redirect logic on load failure. (location: page.html:372 (carbonfeverthink.com script tag, data-cfasync=false))
social engineering
Site claims to host 'leaked' and 'viral' private Indian MMS sex videos, including content framed as non-consensual or secretly recorded ('leaked mms', 'viral leaked'). This framing is a social engineering technique used to lure users seeking voyeuristic content, increasing engagement and exposure to ad-redirect malware payloads on the site. (location: page.html:20-21, page.html:976-978 (title, meta description, hero text))
hidden content
Font resources are loaded via URL paths starting with /fonts.gstatic.com/ (a relative path starting with a slash) rather than the canonical https://fonts.gstatic.com/. This unusual path construction could be an attempt to proxy or intercept font requests through the origin server, or may indicate a misconfiguration that obscures third-party resource loading from security scanners. (location: page.html:79-96 (@font-face src URLs using /fonts.gstatic.com/...))
curl https://api.brin.sh/domain/viralkand.comCommon questions teams ask before deciding whether to use this domain in agent workflows.
viralkand.com currently scores 36/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.