context safety score
A score of 30/100 indicates multiple risk signals were detected. This entity shows patterns commonly associated with malicious intent.
malicious redirect
Search form action points to Google but uses a hidden field 'as_sitesearch' to constrain results to 'kuttymovies1.fit', a different domain than the current site (kuttymovies.hot). This silently redirects user search intent to a third-party piracy domain without disclosure. (location: page.html:17-21)
brand impersonation
Site at kuttymovies.hot impersonates the well-known KuttyMovies brand, displaying 'KuttyMovies.io' branding and copyright while operating from a .hot TLD. The page body actively promotes 'KuttyMovies.io' as the canonical domain, suggesting this is a lookalike/clone site designed to capture traffic intended for the real brand. (location: page.html:14-15, page.html:161)
social engineering
The page includes Tamil-language text instructing users to 'always use the KuttyMovies.io domain to find the current Kuttymovies', steering visitors away from the current .hot domain to another domain. This is a trust manipulation tactic used by piracy networks to herd users across domain hops, often to monetize via ads or malware. (location: page.html:15, page-text.txt:3)
malicious redirect
External JavaScript loaded from '//lo.synedawtit.com/ruitDoCBJMa5A/135754' with data-cfasync='false' attribute (bypassing Cloudflare bot protection). The domain 'synedawtit.com' is a known ad/redirect network associated with aggressive redirect chains, pop-unders, and potentially malicious ad payloads. This script runs asynchronously without user consent. (location: page.html:148)
hidden content
Histats tracker script is dynamically injected into the DOM via JavaScript, loading from '//s10.histats.com/js15_as.js'. This covert tracking script collects visitor analytics without explicit disclosure or consent. The noscript fallback also loads a tracking pixel from 'sstatic1.histats.com'. (location: page.html:177-186)
social engineering
Site offers free downloads of copyrighted movies ('free Tamil movie downloads', 'HD downloads in 480p, 720p, and 1080p for free'), luring users with pirated content. This is a common vector to expose users to malware, credential harvesting, and malicious ad networks via download flows. (location: page.html:8-9, page-text.txt:14-16)
curl https://api.brin.sh/domain/kuttymovies.hotCommon questions teams ask before deciding whether to use this domain in agent workflows.
kuttymovies.hot currently scores 30/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.