context safety score
A score of 35/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
social engineering
Aggressive animated banner with flashing red border, blinking buy button, and Hindi text '👇 क्लिक करें 👇' (Click here) and '🔥 अभी ₹49 में खरीदें 🔥' (Buy now for ₹49) designed to pressure users into clicking a purchase link via urgency and visual manipulation techniques. Banner appears both in mobile header and mobile footer zones. (location: page.html lines 149-208, 297-356; page-text.txt lines 8-12, 151-155)
malicious redirect
Navigation menu and ad banners contain outbound links to third-party domains (indian-sex.vip, desixxxmms.site, desisexvideos.online, digitalshopforindian.systeme.io) outside the primary domain. The ad banner links to a third-party sales funnel platform (systeme.io) that could redirect users to credential-harvesting or payment-fraud pages. (location: page.html lines 148, 150-156, 298-304)
obfuscated code
A large self-executing obfuscated JavaScript block uses decodeURI on a percent-encoded string, applies a character-code Caesar-cipher shift keyed on string index positions, then slices the result into segments by offset array before executing. The technique is consistent with fingerprinting, ad-fraud, or covert redirect scripts. The script carries the attribute data-cfasync="false" to bypass Cloudflare async deferral, indicating intentional evasion. (location: page.html line 376; page-text.txt lines 227)
hidden content
A Google Tag Manager iframe (GTM-5MS946KP) is injected with height=0, width=0, display:none, visibility:hidden inside a <noscript> block, enabling silent tracking or payload delivery without user visibility. A second inline GTM bootstrap script loads the same container ID dynamically, doubling the tracking surface. (location: page.html lines 130-138, 373-375)
obfuscated code
A base64-encoded inline script is loaded via a data: URI src attribute for the wpst-main-js-extra script tag, bypassing standard script-src CSP rules and making the payload opaque to URL-based scanners. Decoded content references wp-admin/admin-ajax.php with a nonce, suggesting server-side interaction from obfuscated client code. (location: page.html line 376 (wpst-main-js-extra src=data:text/javascript;base64,...))
obfuscated code
Google gtagjs-after script is also loaded via a base64-encoded data: URI src attribute rather than a standard URL, obscuring its actual behavior from network-level inspection. (location: page.html line 127 (google_gtagjs-js-after src=data:text/javascript;base64,...))
social engineering
Site presents itself as hosting 'leaked' and 'viral' private MMS content, framing non-consensual intimate imagery as entertainment. This is a known lure pattern used to attract traffic to monetized scam/purchase funnels and to normalize clicking on unsolicited links. (location: page.html title, meta description, page-text.txt lines 72-149)
hidden content
A LiteSpeed referrer-spoofing script at page load reads a sessionStorage key 'litespeed_docref' and overrides document.referrer via Object.defineProperty, masking the true referral source from analytics and security tools. While a known LiteSpeed optimization pattern, it can also be abused to hide traffic sources. (location: page.html line 1 (litespeed_docref sessionStorage script))
curl https://api.brin.sh/domain/viralmms.siteCommon questions teams ask before deciding whether to use this domain in agent workflows.
viralmms.site currently scores 35/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.