context safety score
A score of 33/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
social engineering
Third-party push notification SDK (push-sdk.com, zone 1500787) is dynamically injected and solicits browser push notification permissions. This is a well-known vector for delivering malicious push ads and social engineering users into granting persistent notification access on a piracy site. (location: page.html:55-75, script src=https://push-sdk.com/f/sdk.js?z=1500787)
malicious redirect
Push SDK at push-sdk.com captures affiliate click_id and source_id URL parameters and forwards them to the ad network. Users who grant push notification permission can subsequently be redirected to malicious advertiser URLs via push notifications, bypassing browser navigation controls. (location: page.html:57-74, opts.extClickID / opts.subID1 passed to push-sdk.com zone 1500787)
hidden content
The entire hero slider carousel (containing all featured movie content) is rendered with inline style 'display: none !important', making it invisible to human users while remaining fully parseable by bots, scrapers, and AI agents. This pattern can be used to serve different content to automated agents vs. human visitors. (location: page.html:205, <div class="container hero-slider" style="display: none !important;">)
social engineering
Floating premium membership popup with an invisible full-overlay anchor tag covering the entire modal uses deceptive UI: a large z-index absolute-positioned transparent link (<a class='banner-yes'>) layered over the dismiss button, creating a clickjacking-style trap that sends users to /premium.html when they attempt to close the banner. (location: page.html:5293-5345, <a target='_blank' href='/premium.html' class='tw-absolute banner-yes tw-top-0 tw-left-0 tw-right-0 tw-bottom-0 tw-z-50'>)
social engineering
Site presents itself as a free, legitimate streaming service ('Watch Online is a free movie and TV shows streaming site') to lower user guard, while operating as a piracy site distributing copyrighted content without authorization from rights holders. This misrepresentation is used to build trust before exposing users to ad monetization and push notification SDKs. (location: page.html:5251-5254, footer promo text)
hidden content
Embedded Yii2App JS object exposes internal configuration including P2P token ('UkfBqB64R'), P2P announce URL (https://www.lookmovie2.to/announce/v1), and third-party API domain (api.mydash.cc). The P2P token suggests the site may leverage user browsers for peer-to-peer content distribution (browser-based torrenting), consuming user bandwidth without explicit consent. (location: page.html:5481, var Yii2App = {"p2p":{"token":"UkfBqB64R","enabled":true,"announce":"https://www.lookmovie2.to/announce/v1"},...})
malicious redirect
External third-party API domain 'api.mydash.cc' is referenced in the embedded Yii2App configuration object. This domain has no visible relationship to lookmovie2.to and its ownership and content are unknown, representing an unvetted external dependency that could serve malicious content or redirect users. (location: page.html:5481, "apiDomain":"//api.mydash.cc")
curl https://api.brin.sh/domain/lookmovie2.toCommon questions teams ask before deciding whether to use this domain in agent workflows.
lookmovie2.to currently scores 33/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.