context safety score
A score of 37/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 uses history.pushState() in a loop (10 times) to trap browser history, then intercepts popstate events to force-redirect users to https://backbutton.videobaba.xyz/back-button-script/public/getit.php?site=NI when they try to navigate away. This is a well-known malvertising technique that prevents users from leaving the site. (location: page.html:622-636, page-text.txt:413-427)
malicious redirect
Popunder ad script loaded from https://a.videobaba.xyz/plugins/poppy/poppy.js triggers a popunder window to https://blazingserver.net/revive/www/admin/plugins/redirectAd/redirect.php?zoneid=243 on user clicks. The redirect goes through an opaque ad-server redirect endpoint, obscuring the final destination. Cookie-based interval tracking (60s, 60s, 180s, 300s) controls pop frequency. (location: page.html:652-759)
malicious redirect
Navigation menu link labeled 'Naked Live Girls' routes through https://revive.videobaba.xyz/revive/www/admin/plugins/redirectAd/redirect.php?zoneid=206, an ad-server redirect that obscures the final destination. Similarly, 'Live Girls' goes through https://blazingserver.net/revive/www/admin/plugins/redirectAd/redirect.php?zoneid=363. Both use redirect.php endpoints that can be retargeted to arbitrary URLs without changing page content. (location: page.html:252, page.html:272)
hidden content
Commented-out ad script block in page source references https://a.pemsrv.com/ad-provider.js with an ad insertion tag (ins class='eas6a97888e33' data-zoneid='4461132'). The block is currently disabled via HTML comment but represents a ready-to-activate third-party ad injection vector from pemsrv.com, a known adult ad network. (location: page.html:602-606, page-hidden.txt:5-7)
hidden content
Cross-Origin client hint delegation header delegates sec-ch-ua, sec-ch-ua-bitness, sec-ch-ua-arch, sec-ch-ua-model, sec-ch-ua-platform, sec-ch-ua-platform-version, sec-ch-ua-full-version, sec-ch-ua-full-version-list, and sec-ch-ua-mobile to https://tsyndicate.com. This silently sends detailed browser/device fingerprinting data to a third-party ad network without user awareness. (location: page.html:59)
social engineering
Multiple post titles use non-consensual exposure framing ('Exposed!', 'gone viral', 'leaked', 'Leaked By Cuck Husband') to present content as real private images of named individuals (e.g., 'Ananya Taneja', 'Alisha', 'Namrata Menon'). This framing is used to drive engagement through voyeuristic social engineering and may facilitate real-world harassment of named persons. (location: page.html:304, page.html:342, page.html:399, page-text.txt:99, page-text.txt:137, page-text.txt:194)
social engineering
External affiliate link 'Indian Sex Cams' (menu item) routes to https://www.dscgirls.live/?oid=4&affid=2&source_id=NI&sub1=web&sub2=link&sub3=MENU with affiliate tracking parameters, and 'AI Porn Video' links to https://www.cmonbae.com/?union_id=MjM3. Both use deceptive menu placement to monetize clicks via affiliate programs without disclosure. (location: page.html:239, page.html:273)
curl https://api.brin.sh/domain/nudeindians2.netCommon questions teams ask before deciding whether to use this domain in agent workflows.
nudeindians2.net currently scores 37/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.