context safety score
A score of 43/100 indicates multiple risk signals were detected. This entity shows patterns commonly associated with malicious intent.
malicious redirect
The page uses a Telegram bot API token to fetch the latest message update and then redirects the visitor's browser to whatever URL is contained in that message (window.location.replace(_0x403ex3)). This is a classic Telegram-bot-controlled traffic redirector: the attacker can change the redirect destination at any time by sending a new message to the bot, enabling dynamic phishing, malware delivery, or scam landing pages without modifying the hosted code. (location: page.html:11-21, function ratedata())
obfuscated code
The JavaScript uses a string-array obfuscation pattern (_0x3587) where property names and method calls are replaced with indexed array lookups (e.g., _0x3587[8] = 'ok', _0x3587[5] = 'replace', _0x3587[6] = 'location'). This is a deliberate technique to evade static analysis and human review while executing redirect and fetch logic. (location: page.html:9-21, var _0x3587 array)
credential harvesting
A live Telegram bot token is hardcoded in the page source: '5842411421:AAFQmHryEBI5OS1UaA2CLKJpT1ZOh_HdNSY'. This token grants full control of the bot and is used to receive attacker-controlled redirect URLs via /getUpdates. The token exposure also allows any party to read all messages sent to this bot, which may include harvested credentials or PII if the bot is also used as a data exfiltration channel. (location: page.html:6, var kick)
phishing
The domain 'doc-0sign.web.app' strongly impersonates a document signing service (e.g., DocuSign) using typosquatting ('doc-0sign' vs 'docusign'). The page presents only a 'Loading...' placeholder while silently redirecting to an attacker-controlled URL fetched from a Telegram bot, consistent with a phishing relay that routes victims to credential-harvesting pages. (location: metadata.json: domain=doc-0sign.web.app; page.html:3,14,19)
brand impersonation
The subdomain 'doc-0sign' on the Firebase hosting domain 'web.app' mimics the DocuSign brand through numeric substitution ('0' replacing 'u'). Combined with the document-signing implied context, this is designed to deceive users and automated systems into trusting the URL as a legitimate DocuSign property. (location: metadata.json: url=https://doc-0sign.web.app)
social engineering
If the Telegram bot redirect URL fails or returns a non-HTTP response, the page falls back to redirecting users to 'https://www.google.com/search?q=covid', a benign-looking URL used as a decoy to appear harmless during sandbox analysis or when the attacker's bot is offline, thereby evading detection while maintaining a plausible cover. (location: page.html:7, var showmeway; page.html:13-14, fallback redirect logic)
curl https://api.brin.sh/domain/doc-0sign.web.appCommon questions teams ask before deciding whether to use this domain in agent workflows.
doc-0sign.web.app currently scores 43/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.