context safety score
A score of 32/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 checks user-agent for bot/crawler strings to serve different content
cloaking
Page conditionally redirects based on referrer or user-agent
js obfuscation
JavaScript uses Function constructor for runtime code generation
js obfuscation
Obfuscated document.write with encoded content
malicious redirect
A popunder ad script (popunderpro.js) is loaded with a data-urls attribute containing a multi-hop redirect chain: a Google redirect URL (google.com/url?q=) pointing to a Bing redirect URL (bing.com/ck/a) which ultimately resolves to digistrone.com/about-us/. This layered redirect through trusted search engine domains obfuscates the final destination and is a classic technique used to bypass URL reputation checks. (location: page.html:487-492, <script src='popunderpro.js' data-urls='["https://www.google.com/url?q=https%3A%2F%2Fwww.bing.com%2Fck%2Fa...digistrone.com..."]'>)
obfuscated code
The page contains inline base64-encoded payloads dynamically decoded and injected at runtime via b64d(). Specifically, ai_insert is called with a base64 string that decodes to ad injection code (adskeeeper.com and mgwidget) appended to the video player element. The use of b64d() throughout to store and execute code hides the actual payload from static scanners and AI agents parsing the HTML. (location: page.html:584, ai_insert('append', '.beeteam368-player...', b64d('PGRpdiBjbGFzcz0nY29kZS1ibG9jay...')))
malicious redirect
A navigation menu item labeled 'Tv Shows' links to the external domain arivumani.net rather than the primary tamilgun.now domain. This is an off-domain redirect embedded in the main navigation, silently routing users to a third-party site. The same domain (arivumani.net) also appears in search suggestions and in a prominent banner image link, indicating coordinated cross-site traffic funneling. (location: page.html:193, <a href='https://arivumani.net'>Tv Shows</a>; also line 374, 424)
hidden content
Multiple <span> elements with data-mce-type='bookmark' style='display: inline-block; width: 0px; overflow: hidden; line-height: 0;' are present inside an iframe embed. These zero-width hidden bookmark spans are invisible to users and standard text extraction but are present in the DOM. While often a WordPress TinyMCE editor artifact, their presence inside a banner iframe is anomalous. (location: page.html:425, inside <iframe src='https://tamilgun.now/new/banner.html'>)
brand impersonation
The page is served from tamilgun.group but all canonical URLs, og:url, schema.org structured data, internal links, asset references, and the site's self-identification all point to tamilgun.now. The current domain (tamilgun.group) is a shadow/mirror of the canonical tamilgun.now site. Users and AI agents resolving this domain would be interacting with a site presenting itself as a different domain, enabling URL confusion and potential SEO manipulation or traffic interception. (location: metadata.json (domain: tamilgun.group), page.html:13 <link rel='canonical' href='https://tamilgun.now/'>, page.html:20 og:url='https://tamilgun.now/')
social engineering
The site distributes copyrighted Tamil movies (HD Movies, Dubbed Movies, Web Series) for free streaming/download, which constitutes piracy. The footer claims 'Copyright 2006 Tamil Gun Team. All Rights are reserved to their respective owners' — a disclaimer designed to deflect legal responsibility while continuing to facilitate infringing content distribution. This social engineering tactic creates a false sense of legitimacy. (location: page.html:441, footer copyright notice; page.html:188-193, navigation categories (HD Movies, Dubbed Movies, etc.))
obfuscated code
The page includes custom base64 encode/decode functions (b2a, a2b, b64e, b64d) defined inline before their use in dynamically injecting ad and tracking code. This self-contained obfuscation infrastructure enables runtime code execution from encoded strings, making static analysis of injected payloads difficult. (location: page.html:494-496, function b2a(), a2b(), b64e=, b64d= definitions)
curl https://api.brin.sh/domain/tamilgun.groupCommon questions teams ask before deciding whether to use this domain in agent workflows.
tamilgun.group currently scores 32/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.