context safety score
A score of 38/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
phishing
1 deceptive links where visible host does not match destination host
obfuscated code
Scripts use a non-standard MIME type 'd3d10189e6276015f8b8934a-text/javascript' to prevent browser execution while still being present in the DOM. This is a known technique to hide script payloads from standard security scanners and content policies, with a separate loader activating them selectively. (location: page.html lines 2, 31, 56 — script type attributes)
obfuscated code
An IIFE deliberately overrides document.currentScript.innerHTML and document.currentScript.textContent via Object.defineProperty to return randomly-generated dummy content (randStr), actively defeating script-content inspection by security tools and AI agents that read script source text. (location: page.html line 33-34, page-text.txt line 34)
malicious redirect
ExoClick popunder ad network script (popMagic v8.0.0) is embedded and configured to fire popup/redirect events triggered by clicks on site content (trigger_class: 'ui-card-link__KxRw6l', frequency_count: 3 per 10-minute period). The syndication host 's.gentlefieldpattern.com' and ads host 'adsession.exacdn.com' are known ExoClick redirect infrastructure used to deliver unwanted redirects and potentially malicious ad payloads. (location: page.html lines 38-57, page-text.txt lines 38-57)
malicious redirect
External script loaded from 'go.bluetrafficstream.com' (SmartPop spot script) with a long hashed user ID. bluetrafficstream.com is a known adult traffic/popunder network that can serve redirects to third-party destinations outside the site operator's control. (location: page.html line 60 — script#SCSpotScript src)
malicious redirect
Banner preheader redirects all clicks to 'https://fhgte.com/tour?utm_campaign=ai.BmY&utm_content=preheader_PB' — an external affiliate/traffic domain (fhgte.com) unrelated to pimpbunny.com, used to funnel traffic off-site without clear disclosure to users. (location: page.html line 21, page-text.txt line 21 — var options.url)
malicious redirect
Navigation link 'AI Porn Chat' points to 'https://s.zlinkw.com/v1/d.php?z=5841904' — a tracker/redirect intermediary (zlinkw.com) rather than a direct destination, routing users through an opaque redirect chain of unknown final destination. (location: page.html line 30 — anchor href s.zlinkw.com)
social engineering
Subscription upgrade dialog uses high-pressure sales tactics and accepts exclusively cryptocurrency payment methods (Bitcoin, Monero, Ethereum, Tether, etc.) with no traditional payment options. Crypto-only payment for adult subscriptions is strongly associated with fraud, non-delivery, and difficulty in dispute resolution/chargebacks. (location: page-text.txt line 60 — Premium upgrade dialog)
hidden content
Multiple scripts are loaded with type 'd3d10189e6276015f8b8934a-text/javascript', a fabricated MIME type that prevents browser execution. These scripts are invisible to users and bypass standard CSP/script-blocking but can be activated by a companion loader script, constituting hidden executable content. (location: page.html lines 2, 31, 56)
social engineering
The site promotes 'Undress AI' and 'AI JERK OFF' services linked from the main navigation, directing users to third-party AI services with unknown data handling practices. These services may collect images or personal data under misleading consent flows. (location: page-text.txt line 30 — navigation links)
curl https://api.brin.sh/domain/pimpbunny.comCommon questions teams ask before deciding whether to use this domain in agent workflows.
pimpbunny.com currently scores 38/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.