context safety score
A score of 28/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
credential harvesting
credential form posts to an off-domain endpoint (may be legitimate SSO/OAuth)
malicious redirect
script/meta redirect patterns detected in page source
cloaking
Page checks user-agent for bot/crawler strings to serve different content
cloaking
Page conditionally redirects based on referrer or user-agent
malicious redirect
Back-button hijacking script manipulates browser history by pushing 10 states and intercepts the popstate event to force a location.replace() redirect to backbutton.videobaba.xyz. This traps users and prevents normal back-navigation, redirecting them to a third-party domain without consent. (location: page.html:213 - inline script block using history.pushState loop and onpopstate handler pointing to https://backbutton.videobaba.xyz/back-button-script/public/getit.php?site=KMB)
malicious redirect
The scanned URL (kamababa.desi) redirects users to a different primary domain (www.thekamababa.com). The canonical tag, all internal links, og:url, and asset URLs all point to thekamababa.com, meaning the .desi domain serves as a redirect/alias funnel to the main site. A domain-change notice banner also explicitly tells users the domain changed. (location: page.html:149 - <link rel="canonical" href="https://www.thekamababa.com/"> and page.html:1237 - domain-change-notice div)
hidden content
A login modal (credential form) is present in the DOM but set to display:none by default. It contains username and password fields that post to https://www.thekamababa.com/ via wpst_login_form. While this is a standard WordPress modal login, it is invisible to casual inspection and only revealed via JavaScript, making it a hidden credential-collection form from the perspective of the scanned domain (kamababa.desi). (location: page.html:1123-1183 - #wpst-user-modal with display:none login and password reset forms)
obfuscated code
Custom base64 encode/decode functions (b2a, a2b, b64e, b64d) are defined inline and wrapped in a <!--noptimize--> block to prevent optimization/inspection. These are minified, single-letter variable names making them hard to audit. They are used in conjunction with ad-inserter plugin (ai_front) logic, which could be used to dynamically load or decode obfuscated ad/redirect payloads at runtime. (location: page.html:1280-1293 and page-text.txt:959-961 - inline <script> block with b2a/a2b/b64e/b64d functions)
hidden content
Third-party analytics script from stats.indianpornempire.com is loaded via a defer script tag. This domain is a cross-site tracker operating outside the primary domain, harvesting visitor data including user-agent and referrer silently. The meta http-equiv delegate-ch header also delegates client hardware hints (architecture, model, platform, UA) to tsyndicate.com, a known ad-tech data broker. (location: page.html:211 - <script defer data-domain="thekamababa.com" src="https://stats.indianpornempire.com/js/script.js"> and page.html:233 - <meta http-equiv="delegate-ch" content="... https://tsyndicate.com">)
social engineering
The homepage description solicits user-generated content uploads: 'Upload your non-watermarked homemade chudai xvideos to us and we will get it published here.' This encourages users to submit private intimate recordings, which could be used for non-consensual content distribution or extortion. (location: page.html:1076 - <p class="homepage-description"> and page-text.txt:754)
curl https://api.brin.sh/domain/kamababa.desiCommon questions teams ask before deciding whether to use this domain in agent workflows.
kamababa.desi currently scores 28/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.