context safety score
A score of 45/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
js obfuscation
JavaScript uses Function constructor for runtime code generation
brand impersonation
The site tiktokio.net impersonates TikTok's brand by using the TikTok name, logo references, and brand colors to appear as an official or affiliated TikTok service. The domain name blends 'TikTok' with 'io' to create a convincing lookalike. The site presents itself as an authoritative TikTok tool without any affiliation disclosure. (location: page.html:34, metadata.json domain field, page.html:14 (logo alt text 'TikTok Video Downloader'))
social engineering
The site uses repeated trust signals ('100% free', '100% safety', 'no virus', 'Safe and Secure', 'SSL certificate', 'personal information will not be revealed') to lower user guard and encourage submission of TikTok video URLs and clipboard access. The 'Paste' button actively reads the user's clipboard via navigator.clipboard.readText() without clear disclosure of what data may be captured. (location: page.html:232 (navigator.clipboard.readText()), page.html:113-114)
malicious redirect
An inline script dynamically injects a third-party push notification SDK from push-sdk.net (zone 1207788) and passes URL parameters 'click_id' and 'source_id' to the external script. This is an adware/affiliate tracking injection that can trigger push notification permission prompts and redirect users through affiliate networks. The domain push-sdk.net is a known push notification monetization/adware network. (location: page.html:52-71 (inline script injecting https://push-sdk.net/f/sdk.js?z=1207788))
hidden content
The push-sdk.net script injection is placed inside a div with class 'ac' immediately after the main form, making it visually invisible to the user. The script's action callbacks (onPermissionGranted, onPermissionDenied, onAlreadySubscribed, onError) are all empty, obscuring what the SDK actually does once loaded. The script also suppresses console output via commented-out console.log calls. (location: page.html:52-72 (div.ac containing push-sdk script with empty callbacks and suppressed logging))
social engineering
The site cross-promotes competitor brand names (Snaptik, SSSTikTok, ssstiktok) and links to external domains (sstiktoks.com, tiktokio.tools) as part of a coordinated SEO/affiliate network, potentially routing users to other sites in the same threat actor ecosystem without transparency. (location: page.html:88 (link to sstiktoks.com), page.html:84 (link to tiktokio.tools))
curl https://api.brin.sh/domain/tiktokio.netCommon questions teams ask before deciding whether to use this domain in agent workflows.
tiktokio.net currently scores 45/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.