context safety score
A score of 32/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 pushes 10 history states so pressing Back triggers location.replace() to an external affiliate/ad redirect URL at backbutton.videobaba.xyz. This traps users in a navigation loop and forces them to an unrelated third-party site without consent. (location: page.html:1423-1440 and page-text.txt:1394-1405 (JavaScript block labeled '<!-- Back button -->'))
malicious redirect
External analytics/tracking script loaded from stats.indianpornempire.com, a third-party domain not affiliated with kamareels2.com, capable of tracking users and potentially serving malicious payloads. (location: page.html:32 (<script defer data-domain="kamareels2.com" src="https://stats.indianpornempire.com/js/script.js">))
malicious redirect
Two ad network scripts loaded from namastedharma.com (an unverified third-party ad broker) with spot/subid tracking parameters, creating a vector for malvertising and unwanted redirects. (location: page.html:1418-1419)
malicious redirect
Script loaded from news-xpunobu.cc/process.js with a numeric ID parameter. The .cc TLD combined with the opaque 'process.js' filename and numeric ID is a strong indicator of a malicious or suspicious ad/redirect network script loaded asynchronously. (location: page.html:1420 (<script type="text/javascript" src="https://news-xpunobu.cc/process.js?id=1559802053" async>))
social engineering
Navigation link labeled 'Live Girls' uses a heavily parameterized affiliate tracking URL (go.rmshqa.com/easy?campaignId=...&userId=...&sourceId=KRS-MTAB) disguised as site navigation, directing users to an external cam/adult service without clear disclosure. (location: page.html:89 (header-mob-sites nav link))
brand impersonation
Page title and OG metadata reference '3sex.com' alongside 'Kama Reels' branding, suggesting the site may be attempting to inherit or leech SEO authority/brand association from a separate domain (3sex.com) not owned by kamareels2.com. (location: page.html:4 (<title>Indian sex reels - 3sex.com - Kama Reels</title>) and line 28 (og:title))
hidden content
The back-button hijack script is wrapped in an HTML comment '<!-- Back button -->' to label it innocuously, and the script's redirect URL target (backbutton.videobaba.xyz) is only revealed at runtime, obscuring its redirecting behavior from casual code inspection. (location: page.html:1422 (HTML comment) and page-hidden.txt:1)
curl https://api.brin.sh/domain/kamareels2.comCommon questions teams ask before deciding whether to use this domain in agent workflows.
kamareels2.com currently scores 32/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.