context safety score
A score of 44/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
cloaking
Page conditionally redirects based on referrer or user-agent
hidden content
Five 1x1 tracking pixels loaded from suspicious third-party domains: unimportant-dance.com, secretdeparture.com, illiterate-reserve.com, fond-might.com, thin-public.com. These domains have no apparent legitimate affiliation with the site and their names suggest throwaway/burner domains commonly used for covert user tracking or data exfiltration. (location: page.html:227-231)
malicious redirect
Third-party ad script loaded from focheglyzy.com — a domain with a randomly-generated appearance typical of malvertising networks. The script uses referrerPolicy='no-referrer-when-downgrade' and is inline within the play dialog, positioning it to intercept user interactions and potentially serve malicious ads or trigger drive-by redirects. (location: page.html:77)
hidden content
A full-viewport overlay div (id='overlay') is present with z-index:9999999999999, opacity:0 and visibility:hidden. This overlay contains an 'ad_overlay' div and can be programmatically made visible, covering the entire page — a pattern used for clickjacking or forced ad impressions. (location: page.html:174-178)
hidden content
Commented-out script tag referencing ocule.co.uk with a hardcoded API key (74641aea-f924-4e70-9a40-c98d0de2a989). The script is disabled but its presence suggests a previously active or planned third-party tracking/analytics integration that may be re-enabled. (location: page.html:6)
social engineering
The 'Play Ogar' button redirects users to ogar.eatcells.com using a bright green styled button with a badge image loaded from icone-png.com (an external image host), potentially used to drive traffic to a subdomain outside users' expectations while appearing as a trusted in-site feature. (location: page.html:79-80)
hidden content
Multiple ad network verification meta tags present (exoclick, kadam, hilltopads, clckd) alongside an anonymous SHA1-hash meta tag (name and content both '77ed5bd6e5113fb30ed17a85438320a3dc898c81'). The volume and variety of ad network verifications indicates aggressive monetization infrastructure with multiple ad networks having site-level access. (location: page.html:16-17,35-37)
curl https://api.brin.sh/domain/eatcells.comCommon questions teams ask before deciding whether to use this domain in agent workflows.
eatcells.com currently scores 44/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.