context safety score
A score of 38/100 indicates multiple risk signals were detected. This entity shows patterns commonly associated with malicious intent.
hidden content
1 hidden or tiny iframe elements detected
malicious redirect
script/meta redirect patterns detected in page source
cloaking
Page loads content in transparent or zero-size iframe overlay
js obfuscation
Obfuscated document.write with encoded content
credential harvesting
Login form collects email address and password fields (fb_USER_NAME_LOGIN, fb_PSSWORD) with form action set to empty string, meaning credentials are submitted to the current page origin. The password field id 'fb_PSSWORD' is a misspelling consistent with a harvesting overlay rather than the legitimate Facebook OAuth flow. (location: page.html:72-94)
social engineering
The page presents a 'Facebook user?' prompt alongside a native email/password form, creating confusion between Facebook OAuth (which should redirect to facebook.com) and a direct credential submission form. Users may believe they are authenticating via Facebook while actually submitting credentials directly to evony.com. (location: page.html:61-95)
malicious redirect
The rand_server() function constructs a redirect URL using an unsanitized external variable 'sid' concatenated into a subdomain: 'http://'+sid+'.evony.com/s.html'. The loginid parameter value '747970653D74727947616D65' is hex-encoded data ('type=tryGame'), and the redirect uses HTTP (not HTTPS), potentially exposing session tokens in transit. (location: page.html:230-234)
obfuscated code
Google Analytics script is loaded via document.write with a URL-escaped string: unescape("%3Cscript src='" + gaJsHost + "google-analytics.com/ga.js'"). This unescape/document.write pattern is a classic obfuscation technique used to evade static analysis of dynamically injected scripts. (location: page.html:301-303)
hidden content
A hidden span with id 'login_info' and class 'login_info' is present with display:none styling. Its contents are dynamically populated and not visible to users, potentially used to pass session state or tracking data invisibly. (location: page.html:42)
hidden content
A zero-dimension hidden iframe (width=0, height=0) named 'IframeSubmitForm' with src='about:blank' is present at the bottom of the page body. Such iframes are commonly used for silent form submission or cross-origin data exfiltration. (location: page.html:314)
curl https://api.brin.sh/domain/evony.comCommon questions teams ask before deciding whether to use this domain in agent workflows.
evony.com 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.