context safety score
A score of 22/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 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 then intercepting the popstate event to redirect the user to https://backbutton.videobaba.xyz/back-button-script/public/getit.php?site=KMB. This traps users on the site and forces a redirect to a third-party domain when they attempt to navigate away. (location: page.html:213)
malicious redirect
An iframe in the mobile footer loads content from https://go.xlviiirdr.com, an opaque third-party ad/redirect network domain with no clear provenance. It passes user identifiers (userId parameter with a long hash) and targeting parameters, and targets hot-india.com as its landing domain. This iframe can serve drive-by redirects or malvertising to mobile visitors. (location: page.html:1083)
hidden content
A domain-change notice banner (id='domain-change-notice') is injected with display:none and only revealed via JavaScript for users with fewer than 2 prior page views. While ostensibly a legitimate domain migration notice, the mechanism of conditionally hiding markup from crawlers/bots while showing it to real users is a cloaking pattern. The notice directs users from kamababa.desi to TheKamaBaba.com. (location: page.html:1236-1251)
obfuscated code
Inline script defines custom base64 encode/decode functions (b2a, a2b, b64e, b64d) wrapped in a <!--noptimize--> block to prevent optimization/inspection. These functions are not used by any visible feature on the page and serve as utility primitives for runtime obfuscation or dynamic payload construction. Their presence alongside ad-inserter plugin infrastructure suggests potential use for concealed ad injection or data exfiltration. (location: page.html:1281-1292)
hidden content
Several ad scripts from namastedharma.com are conditionally loaded: one only when the page is accessed as a PWA (standalone display-mode), and others are commented out with notes like 'DISABLED INPP DUE TO ABUSIVE EXP'. The commented-out scripts reference interstitial and pop-under ad formats previously disabled for abusive user experience. The PWA-conditional script (rOqKbo7.js) bypasses the standard ad-loading path entirely and runs outside the age-verification gate. (location: page.html:216-231)
social engineering
The site solicits user-generated content upload with the prompt: 'Upload your non-watermarked homemade chudai xvideos to us and we will get it published here.' This encourages users to upload potentially non-consensual intimate imagery (NCII) by framing it as a content contribution, which is a social engineering vector for harvesting such material. (location: page.html:1076)
hidden content
A <meta http-equiv='delegate-ch'> tag delegates Client Hints headers (including detailed UA architecture, platform, version, and mobile status) to tsyndicate.com, a third-party ad network. This silently passes detailed browser fingerprinting data to an external domain without user awareness or consent notice on the page. (location: page.html:233)
curl https://api.brin.sh/domain/thekamababa.comCommon questions teams ask before deciding whether to use this domain in agent workflows.
thekamababa.com currently scores 22/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.