context safety score
A score of 47/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
obfuscated code
An immediately-invoked function expression (IIFE) uses randomized string generation (randStr), dynamic property redefinition on document.currentScript (innerHTML and textContent getters), and a custom event 'getexoloader' to covertly bootstrap an external ad/payload loader ('ExoLoader'). The obfuscation is designed to evade static analysis and conceal the loader's true behavior. It then calls ExoLoader.serve() pointing to a server-side PHP script. (location: page.html:139-145 (inline <script> block))
malicious redirect
ExoLoader.serve() is called with a script_url of '/fuab/bl475.php', a server-side PHP endpoint with an opaque path. This pattern is consistent with ad-fraud or drive-by download infrastructure that dynamically serves further payloads, redirects, or popunders depending on visitor fingerprinting. The PHP endpoint is not a standard ad network integration and its purpose is not disclosed. (location: page.html:143)
hidden content
An HTML comment block contains a previously-displayed 'Announcement' div (dated September 27th regarding hardware downtime) that has been commented out but left in the source. While this specific instance appears benign, commented-out HTML is a common technique for hiding content from users while retaining it in the DOM for scraping, tracking, or future re-enablement without detection. (location: page.html:28-37)
social engineering
The site author meta tag exposes a personal Gmail address (xcoder963@gmail.com) rather than a corporate contact. Combined with the obfuscated ad loader, this suggests a low-accountability operator, which is a risk factor for social engineering abuse (e.g., using the free image hosting platform to host phishing assets or malicious images distributed to victims). (location: page.html:8)
curl https://api.brin.sh/domain/pixhost.toCommon questions teams ask before deciding whether to use this domain in agent workflows.
pixhost.to currently scores 47/100 with a suspicious verdict and medium 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.