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
brand impersonation
The site core.pw presents itself as the official Wargaming Legal Portal, cloning the visual design, branding, navigation structure, and content of the legitimate legal.wargaming.net site. It uses the title 'Legal Portal', displays Wargaming logos, copyright '© 1998–2025 Wargaming.net. All rights reserved.', and references Wargaming games and services — all while being hosted on the unrelated domain core.pw. (location: page.html:11, page.html:164, page.html:431, page.html:627)
malicious redirect
All CSS and JavaScript assets are loaded directly from legal.wargaming.net (the legitimate domain), including the primary site stylesheet and JS module. This cross-origin asset loading allows the attacker's site to mirror the legitimate site's appearance in real time while keeping the user on the fraudulent core.pw domain. (location: page.html:12)
phishing
The site impersonates Wargaming's legal portal on the deceptive domain core.pw. It replicates the full site structure including 'User Documents', 'Partner Documents', 'Data Privacy', and 'Online Safety' sections, as well as a contact email privacy@wargaming.net — designed to deceive users into believing they are interacting with the official Wargaming legal site. (location: page.html:289, page.html:307, page.html:323, page.html:470-471)
credential harvesting
The page includes a CSRF token meta tag and loads Zendesk form builder scripts (zendesk-form.js) along with Dropzone file upload functionality. These elements suggest the site may serve forms that collect user data or credentials under the guise of the legitimate Wargaming legal portal. (location: page.html:13, page.html:796, page.html:789, page.html:798)
hidden content
A div with class 'd-none' (Bootstrap display:none) contains multiple anchor tags with sub-document paths including '/en/user-documents/eula', '/en/partner-documents/partners-privacy', and '/en/online-safety/create-ticket'. These hidden links are invisible to users but may be crawled by bots or used to construct navigation state, obscuring the full attack surface. (location: page.html:375-393)
curl https://api.brin.sh/domain/core.pwCommon questions teams ask before deciding whether to use this domain in agent workflows.
core.pw 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.