context safety score
A score of 42/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
obfuscated code
All script tags use a non-standard type attribute value '7fd6898fdf4bd65cedb09a81-text/javascript' instead of 'text/javascript'. This is a Cloudflare Rocket Loader obfuscation technique where scripts are deferred by mangling their type, but the same token pattern is used across all inline and external scripts including first-party code, making it impossible to distinguish legitimate deferral from intentional type obfuscation used to evade content security scanners. (location: page.html: lines 6, 17-21, 22, 602-604, 619, 625, 632, 639, 783, 1107, 1108, 1119, 1130)
malicious redirect
All news article links are routed through a dynamic redirect function 'loadingNews.getRedirectUrl(campaignId, url)' rather than linking directly to source articles. This intermediary redirect layer, combined with campaign tracking IDs, means users and AI agents following links are sent through an unauditable redirect chain whose final destination cannot be determined from the page source alone. This pattern is consistent with traffic monetization networks that can silently redirect to malicious or advertiser-controlled destinations. (location: page.html: lines 958, 971, 979, 984, 1004, 1031, 1035, 1051, 1059, 1064, 1084, 1101)
hidden content
The Google Tag Manager noscript iframe (GTM-PXMS5MZ) is rendered with style='display:none;visibility:hidden' and zero dimensions (height=0, width=0), creating a hidden iframe that executes in no-script environments. While GTM is commonly used legitimately, a hidden zero-dimension iframe can be used to load third-party tracking or malicious payloads invisible to the user. (location: page.html: lines 629-630)
social engineering
The site prompts unauthenticated users with a registration popup ('Sign up and get more interesting news') and encourages social network login via Facebook and Google OAuth flows. The login popup collects social network credentials indirectly. While standard for news aggregators, the combination of opaque redirect infrastructure and OAuth collection warrants noting as a credential aggregation vector. (location: page.html: lines 641-668)
hidden content
The <!--googleoff: all--> and <!--googleon: all--> comments wrap the doT.js template scripts, instructing Google's crawler to ignore this block. This suppresses indexing of the dynamic redirect template code, reducing visibility of the getRedirectUrl redirect mechanism to search engine security scanners while still executing it for users and AI agents. (location: page.html: lines 948, 1106)
curl https://api.brin.sh/domain/idealmedia.ioCommon questions teams ask before deciding whether to use this domain in agent workflows.
idealmedia.io currently scores 42/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.