context safety score
A score of 37/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
malicious redirect
script/meta redirect patterns detected in page source
brand impersonation
The site operates as 'GenYoutube' / 'GenYTB' and explicitly instructs users to prepend 'gen' to YouTube URLs (e.g., youtube.com becomes genyoutube.com), directly impersonating YouTube's brand, logo colors, and UI patterns to deceive users into thinking they are interacting with an official YouTube-affiliated service. (location: page.html:6, page.html:1193, page.html:1281-1292)
malicious redirect
The page is served at genyt.net but all canonical URLs, OG tags, and internal links point to www.genytb.net — indicating a domain redirect/forwarding scheme where the scanned domain (genyt.net) silently forwards users to genytb.net without disclosure. The twitter:url and og:url meta tags both point to genytb.net while the page is served from genyt.net. (location: page.html:14, page.html:20, page.html:26)
malicious redirect
JavaScript iframe-busting code forces the page to break out of any parent frame by replacing the top-level window location: 'if (window.top !== window.self){ window.top.location.replace(window.self.location.href); }'. While sometimes legitimate, this can be abused to hijack navigation in embedded or agent-browsed contexts. (location: page.html:1433-1435)
hidden content
Large blocks of HTML content including the full service description, download instructions, browser extension promotions, and recent search tags are wrapped in HTML comment blocks (<!-- ... -->) making them invisible to users but still parseable by crawlers and AI agents. This is a common SEO manipulation and hidden content injection technique. (location: page.html:1272-1329, page.html:1330-1336, page.html:1337-1351, page.html:1357-1359)
hidden content
Multiple duplicate CSS style blocks appear — one active <style> block and two identical blocks commented out (<!--<style>...-->). The commented-out blocks are byte-for-byte duplicates of the active style, suggesting prior obfuscation attempts or content that was toggled on/off to manipulate rendering or scanning tools. (location: page.html:58-59, page.html:60)
social engineering
The site promotes browser extensions for Firefox, Chrome, and Safari (links to genytb.net/firefox-extension.html, /chrome-extension.html, /safari-extension.html) within hidden HTML comment blocks. Unofficial browser extensions that hook into YouTube are a well-known vector for credential harvesting and session hijacking. (location: page.html:1295-1328)
social engineering
The site claims to download 'age-restricted videos', 'Vevo videos', and 'region protected videos' — explicitly advertising circumvention of platform access controls. This social engineering lures users into installing extensions or submitting YouTube session credentials/cookies to bypass protections. (location: page.html:1344-1347)
curl https://api.brin.sh/domain/genyt.netCommon questions teams ask before deciding whether to use this domain in agent workflows.
genyt.net currently scores 37/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.