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
phishing
1 deceptive links where visible host does not match destination host
brand impersonation
The domain schwabrt.com impersonates Charles Schwab's brand by using the official Charles Schwab logo (charles_schwab_logo.svg), loading proprietary Charles Modern fonts directly from www.schwab.com, and presenting itself as 'Schwab Retirement Technologies' — mimicking the legitimate schwabrt.com subsidiary. The actual legitimate domain appears to be www.schwabrt.com (used in all internal links), while this site is served from schwabrt.com (without 'www'), raising the possibility this is a typosquat or subdomain-confusion attack targeting the Schwab brand. (location: page.html:9-20, metadata.json domain field)
malicious redirect
A dynamically obfuscated JavaScript file is loaded at the very end of the page body from a heavily path-obfuscated local endpoint: /ehvYOh/wi9z/i2D18/eaPwUP/29p/aVV1hXzXL5hSht/R3weTgo7RAE/BF/QKOxNKSSAB. This path bears no resemblance to any legitimate asset path used elsewhere on the page (css/main.css, images/, etc.) and is consistent with a server-side malware dropper, redirect injector, or credential skimmer script. Legitimate Schwab pages do not use randomized multi-segment paths for scripts. (location: page.html:121)
obfuscated code
The script tag src='/ehvYOh/wi9z/i2D18/eaPwUP/29p/aVV1hXzXL5hSht/R3weTgo7RAE/BF/QKOxNKSSAB' uses a deeply obfuscated, pseudo-random URL path with no semantic meaning, characteristic of obfuscated malware delivery, cryptomining loaders, or credential-harvesting scripts injected into compromised sites. No other resource on the page uses a path with this pattern. (location: page.html:121)
credential harvesting
The page impersonates a trusted financial institution (Charles Schwab) complete with official logo, branded fonts sourced from schwab.com, and institutional-grade UI, creating a high-trust environment. Combined with the obfuscated script, this setup is consistent with a credential harvesting operation where the injected script silently intercepts any form submissions, session tokens, or user interactions on behalf of Schwab clients or retirement plan administrators. (location: page.html:19-20, page.html:121)
phishing
The site presents as a legitimate Schwab B2B portal targeting institutional recordkeepers and retirement plan administrators — a high-value demographic. It uses Schwab's official visual identity (logo, fonts, color scheme), references legitimate Schwab subsidiaries, SIPC membership, and FDIC affiliation to establish false legitimacy, while the domain schwabrt.com (vs. the legitimate www.schwabrt.com used in all hrefs) may be used to intercept institutional users navigating to the wrong URL. (location: page.html:1-122, metadata.json)
curl https://api.brin.sh/domain/schwabrt.comCommon questions teams ask before deciding whether to use this domain in agent workflows.
schwabrt.com 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.