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
malicious redirect
External domain dmm-extension.com (not a dmm.com subdomain) loads auto-login.js with a data-encoded obfuscated payload attribute 'DRVESRUMTh1PEkYWV1sLGQIKWxk_'. The script is labeled 'auto-login' and executed synchronously in the <head>, giving it full page access before DOM load. The encoded data attribute may carry configuration or exfiltration parameters for credential harvesting. (location: page.html, line 48)
credential harvesting
Script from dmm-extension.com (id='auto-login') is a third-party, non-dmm.com domain loading JavaScript named 'auto-login.js' with a base64-like encoded data attribute. This script has the capability to intercept login form submissions or session cookies, as it executes synchronously in the <head> before any other content loads. (location: page.html, line 48)
obfuscated code
The 'data-encoded' attribute on the dmm-extension.com auto-login script tag contains the value 'DRVESRUMTh1PEkYWV1sLGQIKWxk_', which appears to be a base64url or XOR-encoded payload. The encoding purpose is not disclosed and the value is not a standard versioning hash. (location: page.html, line 48)
malicious redirect
navismithapis-cdn.com (not a dmm.com subdomain) serves 10+ critical JavaScript files including pc-tablet-login.js, tracking.js, and exchange-link-rewriter.js. The 'exchange-link-rewriter' script in particular can silently rewrite outbound links to redirect users to attacker-controlled destinations. Supply-chain compromise of this CDN would affect all navigation on the page. (location: page.html, lines 52-95)
brand impersonation
p-smith.com (a non-dmm.com external domain) serves all brand assets for DMM.com including the site logo, favicon, OGP sharing images, Apple touch icon, and all service icons. These assets are used to construct DMM's visual identity. If p-smith.com is attacker-controlled or compromised, it can swap brand imagery to impersonate or defame DMM or redirect users via image-based attacks. (location: page.html, lines 17, 24, 37, 40, 43, 683 (and throughout))
hidden content
CSS rule '.top-login { display: none; }' hides a login UI element from visual display. While this may be intentional (login state toggled by JS), it could be used to hide a secondary login form that captures credentials invisibly. (location: page.html, lines 53-55)
hidden content
Anonymous CloudFront URL (d2ezz24t9nm0vu.cloudfront.net) loads a script asynchronously with no id, no version parameter, and no identifiable owner. The lack of any identifying attributes makes this script's purpose opaque and unauditable. (location: page.html, line 123)
curl https://api.brin.sh/domain/dmm.comCommon questions teams ask before deciding whether to use this domain in agent workflows.
dmm.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.