context safety score
A score of 39/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
obfuscated code
Obfuscated popunder/ad injection script using base64-encoded URLs loaded via dynamic script injection. The script decodes four base64 strings (cdn4ads.com, CloudFront-hosted JS, xnwyqmaqwladi.com, lffmauigoa.com) at runtime, injects them as script tags with fallback chaining, and uses a timestamp kill-switch (1798553096000). This pattern is characteristic of malvertising/popunder ad networks that can redirect users to phishing or malware pages. (location: page.html line 211 / page-text.txt line 148)
malicious redirect
The obfuscated ad script loads external scripts from domains including 'www.cdn4ads.com', 'xnwyqmaqwladi.com', and 'lffmauigoa.com' — all decoded from base64 at runtime. These are third-party ad/popunder network domains with no transparency, capable of serving drive-by redirects, malvertising, or unwanted popunders to visitors. (location: page.html line 211 (base64 decoded: d3d3LmNkbjRhZHMuY29tL3JzYXNzLm1pbi5jc3M=, d3d3Lnhud3lxbWFxd2xhZGkuY29tL2RzYXNzLm1pbi5jc3M=, d3d3LmxmZm1hdWlnb2EuY29tL016Q0YvaGZyYW1ld29yazcubWluLmpz))
hidden content
A 1x1 pixel hidden iframe is injected into the document body via JavaScript (height=1, width=1, position absolute, visibility hidden) and used to load Cloudflare challenge scripts. While this specific instance appears to be a Cloudflare bot-detection mechanism, the pattern of injecting hidden iframes via script — especially combined with the obfuscated ad loader on the same page — represents a hidden content vector that could be repurposed for tracking or silent redirects. (location: page.html line 1290 / page-text.txt line 1227)
social engineering
The site uses the brand name 'Fry99' alongside references to 'Fry99.com' in metadata (the .com variant in the description meta tag), while the actual domain is fry99.cc — a TLD substitution pattern commonly used to impersonate or capitalize on the reputation of an established .com domain and lure users who mistype or follow links expecting the original site. (location: page.html line 30 (meta description: 'Fry99.com Viral indian porn'))
brand impersonation
The meta description explicitly references third-party brand names 'Masahub', 'Desi49', and 'mydesi' as if this site serves their content ('Masahub porn videos, Desi49 porn, mydesi mms sex clips'). This is a brand-jacking/SEO poisoning technique to capture search traffic intended for those competitor or legitimate platforms. (location: page.html line 30 (meta name='description'))
malicious redirect
An external ad manager script is loaded from 'js.wpadmngr.com' with a data-admpid attribute. This is a known third-party ad injection service (Tssp ad network, commented as such in the HTML) that can serve popunders, forced redirects, and malvertising payloads outside the site operator's direct control. (location: page.html line 208)
curl https://api.brin.sh/domain/fry99.ccCommon questions teams ask before deciding whether to use this domain in agent workflows.
fry99.cc currently scores 39/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.