context safety score
A score of 40/100 indicates multiple risk signals were detected. This entity shows patterns commonly associated with malicious intent.
brand impersonation
The page title is '用户登录-58同城' (58.com login page) served from ganji.com. 58同城 (58.com) is a major Chinese classifieds platform that acquired Ganji.com; however, the page explicitly presents as a 58同城 login interface while the domain is ganji.com, and window.SOURCE is set to '58-ganji-pc'. The page loads all authentication/passport scripts from 58cdn.com.cn (a 58.com CDN), meaning credentials entered would be processed by 58.com infrastructure via a ganji.com URL — a classic brand impersonation and credential harvesting vector for users who do not recognize ganji.com as affiliated with 58.com. (location: page.html:7, page.html:12)
malicious redirect
window.ISREDIRECT is explicitly set to 'true' and window.PATH encodes a redirect back to 'https://ganji.com?pts=1772638644544'. The 'pts' parameter appears to be a tracking/session token appended to the redirect URL. This redirect chain — landing on ganji.com, presenting a 58同城 login, then redirecting back with a session token — is consistent with an open redirect or session-fixation flow used in phishing campaigns. (location: page.html:13, page.html:16)
credential harvesting
The page loads 58.com passport/login SDK scripts (passport-sdk-pc and passport-pc-ui login_scan) from j1.58cdn.com.cn. These scripts handle authentication flows including QR code scanning and mobile login. Any credentials or session tokens submitted are sent to 58.com's backend via externally hosted scripts that cannot be audited from this page. Combined with the redirect and tracking token in the URL, this constitutes a credential harvesting setup. (location: page.html:43, page.html:44)
phishing
The page body is completely empty (<body></body>) with no visible UI, yet loads a full login/passport SDK. The actual login UI is rendered entirely by external JavaScript from 58cdn.com.cn. This technique hides the true nature of the page from static analysis and makes the phishing interface appear only at runtime, evading content scanners that analyze static HTML. (location: page.html:9-10, page.html:43-44)
hidden content
The rendered page has no visible HTML content in the body — all content is injected dynamically via externally hosted scripts. The page-text.txt confirms no user-visible text is present in the static HTML. This pattern is used to hide the true purpose of a page from crawlers, security scanners, and AI agents performing static analysis. (location: page.html:9-10, page-text.txt:1-37)
curl https://api.brin.sh/domain/ganji.comCommon questions teams ask before deciding whether to use this domain in agent workflows.
ganji.com currently scores 40/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.