context safety score
A score of 45/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
malicious redirect
script/meta redirect patterns detected in page source
cloaking
Page conditionally redirects based on referrer or user-agent
malicious redirect
An inline script performs a hardcoded URL redirect: if the current page is a specific Wire article about a Hezbollah attack, it redirects to a completely different article about an Australian-Indian killed in Gaza. The replacement URL contains a leading space (' https://thewire.in/world/australian-indian-killed-gaza'), which is anomalous and could be used to bypass URL filters or cause unexpected navigation behavior. (location: page.html, line 1 — first <script type="text/javascript"> block: '"https://thewire.in/world/one-indian-killed..."===window.location.href&&(window.location.href=" https://thewire.in/world/australian-indian-killed-gaza")')
malicious redirect
An external JavaScript file is loaded from a different domain (thewirehindi.com) with a versioned query parameter: 'https://thewirehindi.com/redirect.js?v=14052025'. This cross-domain script has full DOM and navigation access and could perform arbitrary redirects or content injection. The domain thewirehindi.com is distinct from thewire.in and its trustworthiness cannot be confirmed from this page alone. (location: page.html, line 1 — <script type="text/javascript" src="https://thewirehindi.com/redirect.js?v=14052025">)
hidden content
The page contains an empty <script> tag with content '0' (<script>0</script>), which is a no-op but is anomalous and could be a placeholder for injected content or a fingerprinting/tracking probe. (location: page.html, line 1 — <script>0</script>)
hidden content
The meta http-equiv refresh tag is set to an extremely large timeout value of 999999 seconds (approximately 11.5 days). While not an immediate redirect, this is non-standard and unusual for a legitimate news site. It could be a remnant of obfuscated redirect logic or anti-analysis measure. (location: page.html, line 1 — <meta http-equiv="refresh" content="999999">)
curl https://api.brin.sh/domain/thewire.inCommon questions teams ask before deciding whether to use this domain in agent workflows.
thewire.in currently scores 45/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.