context safety score
A score of 46/100 indicates multiple risk signals were detected. This entity shows patterns commonly associated with malicious intent.
js obfuscation
JavaScript uses Function constructor for runtime code generation
brand impersonation
The site operates as 'StreamEast' on the domain istreameast.app, which is a well-known copycat/impersonation of the legitimate StreamEast brand. The domain uses a prefix 'i' (istreameast) to mimic the original service, presenting itself with identical branding, logo, and site name 'StreamEast - Home of Sports Streaming Since 2018'. This is a common brand-squatting pattern used to redirect traffic from the legitimate service. (location: page.html:7, page.html:393-395, page.html:1583 — title tag, logo, and h1 element)
social engineering
The site offers free access to premium live sports streams (NFL, NBA, NHL, MLB, Premier League, etc.) without authorization from rights holders. This 'free streaming' value proposition is a well-established social engineering lure used to attract users who then become exposed to malicious ads, redirects, or malware payloads typically embedded in stream player pages. The 'Multi Stream - Free' nav item reinforces this lure. (location: page.html:651-656 — Multi Stream nav item; page.html:1608 — 'It is cheap for students, youthful fans, and low-income families')
malicious redirect
Blog images and assets are loaded from the external domain scdnmain.net rather than istreameast.app itself. This third-party CDN domain (scdnmain.net) is unrelated to the site's own domain and could serve as a vector for malicious content, tracking, or redirects. Stream link pages (linked from the game listings) are known on piracy streaming sites to chain through multiple ad-redirect networks before reaching a player. (location: page.html:1538, 1554, 1570 — img src attributes referencing https://scdnmain.net/images/blog/)
hidden content
The page-text.txt and page-hidden.txt extraction show that large blocks of inline CSS style rules are rendered as visible text content by the browser's text extractor, indicating these style blocks are embedded inside the body in non-standard locations. Additionally, the canonical URL points to /v44 subdirectory while the domain root is served, suggesting URL versioning or cloaking behavior where different content may be served to crawlers vs. users. (location: page.html:10-11 — canonical href points to /v44; page-text.txt:28-188 — CSS rendered as text)
social engineering
The site includes a blog post titled 'How Football Fans Can Avoid Fake Streaming Pages and Malicious Links' while itself being an unauthorized streaming site. This reverse-psychology trust-building tactic is designed to make the site appear legitimate and safety-conscious to both users and automated scanning tools, reducing suspicion while the site itself engages in the exact behavior it warns against. (location: page.html:1565-1577 — blog card linking to /blog/how-football-fans-can-avoid-fake-streaming-pages-and-malicious-links)
curl https://api.brin.sh/domain/istreameast.appCommon questions teams ask before deciding whether to use this domain in agent workflows.
istreameast.app currently scores 46/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.