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
cloaking
Page loads content in transparent or zero-size iframe overlay
js obfuscation
JavaScript uses Function constructor for runtime code generation
malicious redirect
Multiple third-party ad banner links use plain HTTP (not HTTPS) and point to unverified gambling/betting domains (e.g., http://nrt-aa.com, http://nc-aa.com, http://bsbs-777.com, http://btbt-1111.com, http://snc-rr.com, http://upsite-24.com, http://core-site365.com, http://tenca-10.com) embedded directly in the page content. These HTTP links expose users to potential MITM-based redirect chains and landing on malicious gambling or scam sites. (location: page.html line 960, top-ad-padding div)
social engineering
The site operates as an adult content aggregator (Korean: 야동/yadong) that requires user registration and login to access favorites and full content. The login popup loads from '/shop/?_Action=login&inajax=1&pop=1' in an iframe overlay, creating a credential-harvesting surface for users who may not verify the origin context carefully. (location: page.html lines 438-440, events.login function)
credential harvesting
Login and registration are handled via a layui popup iframe that loads '/shop/?_Action=login&inajax=1&pop=1'. The site collects user tokens and stores them in local browser data via layui.data('odAdmin'). Token is automatically appended to all AJAX requests including request headers, creating a persistent session token exfiltration risk if the domain is compromised or the CDN-hosted scripts are tampered with. (location: page.html lines 172-185, view.req function)
hidden content
Multiple channel/content category labels are commented out in the HTML source (e.g., '따봉 개추작', '피딩', '팬트리', '대륙 매춘 시리즈', '비밀스토리', 'BJ 라이브', '스트립챗', '대만성방') as hidden paragraph tags. While these appear to be UI labels intentionally suppressed, they reveal internal content taxonomy and could indicate content categories not disclosed to users or regulators. (location: page-hidden.txt lines 55-78)
malicious redirect
A bottom navigation button labeled '야스코' (yaskorea) triggers a JavaScript redirect to 'https://yaskorea.cc' — an external domain separate from the main site. This cross-domain redirect from an adult content site to an affiliated external domain (yaskorea.cc) presents a risk of users being sent to uncontrolled third-party content or phishing pages. A commented-out sidebar link to the same domain also exists. (location: page.html lines 420-422, events.bottomBtn; page-hidden.txt lines 10-14)
hidden content
A third-party web analytics tracker from '//waust.at/d.js' (waust.at) is injected at the bottom of the page outside the main body tag, loaded asynchronously. This is an obscure analytics provider not disclosed in any privacy policy visible on the page, collecting visitor fingerprint data silently. (location: page.html line 4440)
social engineering
The site footer presents a seemingly legitimate business identity with a US phone number (+1 312-856-4074) and an obfuscated email address (protected via Cloudflare's email obfuscation). This creates a false sense of legitimacy for an adult content site hosting potentially non-consensual or pirated material, which could be used to social-engineer users into registering accounts or making payments. (location: page.html line 4073)
curl https://api.brin.sh/domain/yasyadong.tvCommon questions teams ask before deciding whether to use this domain in agent workflows.
yasyadong.tv 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.