context safety score
A score of 35/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
credential harvesting
The page presents Login, Sign Up, and 'Forgot your password?' navigation links on a domain registered only 178 days ago with no established brand identity. The site appears to be a file-hosting/streaming clone (speedostream1.com) designed to harvest user credentials via a login portal at /login.html. (location: page.html:36-38, navigation menu)
brand impersonation
The site logo image is loaded from an entirely different external domain (ingfree.xyz), a strong indicator that the site is cloning or impersonating another brand's visual identity using assets hosted elsewhere. The domain 'ingfree.xyz' is not affiliated with speedostream1.com and the pattern is consistent with phishing kit deployment. (location: page.html:28, <img src='https://ingfree.xyz/ib/T0hNZGWuRp.png'>)
phishing
Domain speedostream1.com is only 178 days old, has an empty page title, nearly empty content area, and presents only authentication-related links (Login, Sign Up, Forgot password). This sparse structure is characteristic of a phishing landing page or credential harvesting site masquerading as a legitimate streaming/file-hosting service. (location: page.html:14 (empty title), page.html:76-90 (empty content div), metadata.json (domain_age_days: 178))
obfuscated code
A hidden 1x1 pixel iframe is dynamically injected into the page via obfuscated inline JavaScript. The script creates an invisible iframe (height=1, width=1, position absolute, visibility hidden) and injects further script content into it, including Cloudflare challenge parameters. This technique is used to execute code out of sight and evade detection, and is a common obfuscation/evasion pattern. (location: page.html:129, inline script at end of body)
malicious redirect
An external ad/tracking script is loaded asynchronously from 'cvt-s1.adangle.online', a domain with a suspicious name pattern ('adangle') not associated with any major legitimate ad network. This script could perform drive-by redirects, serve malicious ads, or exfiltrate session data. (location: page.html:128, <script async src='https://cvt-s1.adangle.online/o/s/a941312e99999aac85c8d55346033a2f.js'>)
hidden content
The main content area (#content div) is completely empty in the rendered HTML, while the page still presents authentication controls. Combined with the externally-hosted logo and third-party scripts, this suggests content may be dynamically injected post-load (e.g., via xupload.js or the hidden iframe script) to evade static analysis. (location: page.html:76-90, #content and #sidebar1 divs are empty)
prompt injection
The Cloudflare challenge script embedded in the hidden iframe contains encoded parameters (base64: 'MTc3MjYyOTEwOQ==' decodes to a timestamp). If an AI agent were to process or summarize this page, the injected script content rendered as visible text in page-text.txt could be interpreted as instructions. The script appears in plain text in page-text.txt line 108, potentially targeting AI crawlers or agents that process page text. (location: page-text.txt:108, inline CF challenge script rendered as visible text)
curl https://api.brin.sh/domain/speedostream1.comCommon questions teams ask before deciding whether to use this domain in agent workflows.
speedostream1.com currently scores 35/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.