context safety score
A score of 36/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
brand impersonation
The page at pas-mantap.fun fully impersonates a Google CAPTCHA/reCAPTCHA verification page, copying Google's exact UI, messaging ('Our systems have detected unusual traffic'), and branding. The page title is set to 'https://www.google.com/' and all visible text mimics Google's legitimate traffic-block/CAPTCHA page verbatim. (location: page.html:3, page.html:22-28)
phishing
The domain pas-mantap.fun hosts a fake Google CAPTCHA challenge page. The form posts to 'index' (a local endpoint on the malicious domain) rather than Google, while deceiving users into believing they are interacting with Google's infrastructure. This is a classic phishing lure designed to harvest form submissions or redirect victims after a fake CAPTCHA solve. (location: page.html:7 (form action='index'), page.html:17)
malicious redirect
A hidden form field 'continue' is set to 'https://www.google.com/', which will redirect victims to Google after form submission, masking the malicious nature of the interaction and making the phishing flow appear seamless. Combined with the fake CAPTCHA, this creates a transparent redirect chain from the malicious domain to Google. (location: page.html:17 (input name='continue' value='https://www.google.com/'))
hidden content
The form contains a hidden input field 'q' with a long opaque encoded/token value ('EhAmABkAAAAtBwAA...'), which is submitted silently to the malicious server. This hidden payload likely encodes session tracking, victim fingerprint, or exfiltration data sent to the attacker's backend without user awareness. (location: page.html:17 (input type='hidden' name='q'))
prompt injection
The page title is set to 'https://www.google.com/' rather than a descriptive title. If an AI agent browses this page and reads the title or URL-like content, it could be misled into believing it is on the legitimate Google domain. The entire page content is crafted to appear as an authoritative Google system message, which could manipulate an AI agent's trust assessment and cause it to follow instructions (e.g., 'solve the CAPTCHA', 'submit the form') as if issued by Google. (location: page.html:3 (title tag), page.html:4 (onload with solveSimpleChallenge))
social engineering
The page uses authoritative Google-branded language ('Our systems have detected unusual traffic', 'in violation of the Terms of Service') to create urgency and legitimacy, pressuring users to complete the fake CAPTCHA and submit the form. The hidden 'infoDiv' section provides a fabricated technical explanation to further convince victims the block and CAPTCHA are genuine. (location: page.html:24-28, page-text.txt:21-24)
obfuscated code
The body onload attribute calls 'solveSimpleChallenge(0,0)' — a function not defined in the visible HTML — suggesting additional JavaScript is loaded externally or injected at runtime to automate CAPTCHA solving or perform other hidden actions. This is consistent with bot-evasion or automated credential harvesting toolkits. (location: page.html:4 (onload='...if(solveSimpleChallenge){solveSimpleChallenge(0,0);}'))
curl https://api.brin.sh/domain/pas-mantap.funCommon questions teams ask before deciding whether to use this domain in agent workflows.
pas-mantap.fun currently scores 36/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.