context safety score
A score of 27/100 indicates multiple risk signals were detected. This entity shows patterns commonly associated with malicious intent.
js obfuscation
JavaScript contains heavy hex-escape encoding typical of obfuscation
obfuscated code
JavaScript uses hex-encoded string array (_0x70a6) with Unicode escape sequences (\x70\x75\x73\x68 etc.) to obscure function names and string literals including 'push', 'replace', 'length', 'constructor', 'cookie', 'decrypt'. This is a classic obfuscation pattern used to hide malicious behavior from static analysis. (location: page.html:11)
obfuscated code
The page loads an external script '/vddosw3data.js' with a randomized/obfuscated filename, a common technique for delivering obfuscated or malicious payloads while evading detection. (location: page.html:3)
malicious redirect
A setTimeout-based redirect fires after 5000ms sending the user to 'https://magicrust.gg:443/'. While the destination matches the current domain, this redirect pattern combined with AES decryption and cookie manipulation is consistent with anti-bot/cloaking systems that redirect detected bots or security scanners while serving different content to real users. (location: page.html:12)
hidden content
The page uses w3IncludeHTML() to dynamically inject the content of '/5s.html' into the DOM at runtime. This technique hides the actual page content from static HTML analysis — the real payload (which may include phishing forms, credential harvesting, or malicious scripts) is loaded from a separate file not visible in the initial HTML source. (location: page.html:5,8)
hidden content
AES decryption is performed client-side using hardcoded keys (a, b, c derived from hex strings) via slowAES.decrypt(), and the result is written directly to document.cookie. This pattern is used to set encrypted tracking or session cookies in a way that conceals their true value from scanners, and may be used to fingerprint or track users covertly. (location: page.html:11)
social engineering
The noscript block displays a red, bold, centered message demanding the user enable JavaScript before proceeding. This pressure tactic is commonly used to coerce users into enabling JavaScript so that obfuscated or malicious scripts can execute. (location: page.html:6)
curl https://api.brin.sh/domain/magicrust.ggCommon questions teams ask before deciding whether to use this domain in agent workflows.
magicrust.gg currently scores 27/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.