context safety score
A score of 38/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
brand impersonation
The site presents itself as 'SnapInsta' — an unofficial Instagram downloader — while prominently using Instagram's branding, logos, and trade dress throughout the page (title, meta tags, OG tags all reference Instagram). The page explicitly disclaims affiliation ('WE ARE NOT AFFILIATED WITH INSTAGRAM OR META') yet is built to appear as an official or semi-official Instagram utility, deceiving users about the service's origin. (location: page.html: <title>, meta tags, og:title, page-text.txt line 1)
malicious redirect
The JavaScript variable k_url_convert is set to 'https://download.ig-12-data.xyz/api/json/convert' — an external third-party domain completely unrelated to Instagram or snapinsta.to. All media conversion and download requests are silently routed through this suspicious domain (ig-12-data.xyz), which could intercept URLs, harvest session tokens, or serve malicious files. The domain name mimics Instagram ('ig') to appear legitimate. (location: page.html line 1: k_url_convert="https://download.ig-12-data.xyz/api/json/convert")
hidden content
A 1x1 pixel invisible iframe is injected into the document body with style attributes position:absolute, top:0, left:0, border:none, visibility:hidden. This hidden iframe is used to inject a Cloudflare challenge script, but the pattern is also a classic vector for hidden tracking, clickjacking, or covert script execution outside the visible page context. (location: page.html lines 13-14: iframe height=1, width=1, visibility:hidden)
obfuscated code
All JavaScript <script> tags use a non-standard type attribute ('2e01d6ff22f8d4004da31265-text/javascript' and '2e01d6ff22f8d4004da31265-module') instead of the standard 'text/javascript'. This technique — commonly associated with Cloudflare Rocket Loader — prevents direct execution and defers script evaluation, effectively obfuscating when and how scripts run. It can mask malicious payloads from static scanners. (location: page.html: all inline <script> tags with type='2e01d6ff22f8d4004da31265-text/javascript')
credential harvesting
The page uses navigator.clipboard.readText() to silently read the user's clipboard contents and paste them directly into the URL input field. While presented as a convenience 'Paste' feature, this grants the site automatic access to whatever the user has copied — which may include passwords, tokens, private URLs, or sensitive data — without any explicit clipboard permission prompt in some browser configurations. (location: page.html line 1 / page-text.txt line 14: navigator.clipboard.readText())
social engineering
The site promotes an Android app download and PWA installation ('Add to Home Screen') with enthusiastic messaging ('PWA app installed by user!!! Hurray'). Encouraging installation of an unofficial app that proxies Instagram content through an unknown third-party backend (ig-12-data.xyz) increases the attack surface for data interception on mobile devices. (location: page-text.txt line 1: 'Download the Snapinsta app for Android'; page.html PWA install listeners)
curl https://api.brin.sh/domain/snapinsta.toCommon questions teams ask before deciding whether to use this domain in agent workflows.
snapinsta.to currently scores 38/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.