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
malicious redirect
script/meta redirect patterns detected in page source
cloaking
Page conditionally redirects based on referrer or user-agent
malicious redirect
Back-button hijacking script uses history.pushState() to flood the browser history stack (10 pushes) and intercepts the popstate event to force-redirect users to https://backbutton.videobaba.xyz/back-button-script/public/getit.php?site=SMM — an external affiliate/ad redirect domain — preventing normal back navigation. This pattern traps users and redirects them to third-party destinations without consent. (location: page.html:1557-1573 and page-text.txt:1522-1537 (duplicated in footer and inline script))
malicious redirect
Navigation link labeled 'Live Sex' uses a heavily obfuscated tracking URL at go.bluetrafficstream.com with long hex userId and sourceId parameters, pointing to an opaque traffic monetization network. The destination is not disclosed to the user and may lead to adult cam or malvertising sites. (location: page.html:92)
malicious redirect
Navigation link labeled 'Live Girls' uses a similarly obfuscated tracking URL at go.rmshqa.com with hex-encoded userId and campaignId parameters. This is a third-party traffic redirect network whose final destination is undisclosed. (location: page.html:93)
hidden content
Third-party analytics/ad script loaded from stats.indianpornempire.com via a deferred script tag. This domain is a cross-site tracker operated by a separate adult network (Indian Porn Empire), collecting behavioral data on visitors without clear disclosure. (location: page.html:34)
hidden content
Two ad/pop scripts loaded from namastedharma.com (c3q8z28.js and KyDQLS3.js) with data-spots parameters (505959, 505960, 506020) and a subid1 tag 'SMM'. These scripts deliver pop-under and interstitial ads and are capable of executing arbitrary JavaScript, spawning new tabs, or triggering drive-by download prompts. (location: page.html:1551-1554)
social engineering
Site description invites users to 'share your porn videos with SpicyMMS Community', soliciting user-generated content uploads from visitors. This is a common social engineering tactic on amateur adult sites to harvest user-submitted intimate media. (location: page.html:1542, page-text.txt:1503-1506)
curl https://api.brin.sh/domain/spicymms.comCommon questions teams ask before deciding whether to use this domain in agent workflows.
spicymms.com 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.