context safety score
A score of 40/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
malicious redirect
JavaScript popstate history manipulation redirects users to https://t.co/f4A1NLlx1I (a shortened URL masking the real destination) when the browser back button is pressed. The script uses history.replaceState and history.pushState to trap users and force a redirect via location.replace, preventing normal navigation away from the site. (location: page.html:779 / page-text.txt:554)
obfuscated code
An obfuscated script is injected at page load that dynamically creates a script element and loads an external resource from //weightydesire.com/c.Ds9L6-bA2W5BlwSHWTQf9SNgjfMR4FNZTXA/5AMmSt0d2hMezJg/1UMEDHkQyn — an unrecognized third-party domain with a highly randomized path characteristic of malvertising or tracking payload delivery. The outer function uses a variable name 'yhhxyr' to obscure intent. (location: page.html:191-200)
hidden content
A 1x1 pixel hidden iframe is injected into the document body via Cloudflare challenge script, containing inline JavaScript that loads /cdn-cgi/challenge-platform/scripts/jsd/main.js. While CF challenge scripts can be legitimate, this iframe is set to position:absolute, top:0, left:0, visibility:hidden and injects further script via innerHTML — a pattern consistent with covert script execution. (location: page.html:890-891)
social engineering
Multiple video titles contain explicit references to minors (ABG = teenage girl, SMP/SD = junior/elementary school students) combined with sexually explicit Indonesian-language descriptions. Titles include 'Sempit Mulus Tanpa Bulu Apem Abg Pelajar SMP' and 'Video Abg Sma Viral 2026 Quality Time Ayah Dan Anak Tiri'. This content is designed to lure users seeking non-consensual or underage material, constituting a social engineering lure that exploits taboo content to drive engagement and clicks. (location: page.html:429-442, 339-352)
credential harvesting
The site presents a registration and login modal form (Join Infoabgviral) collecting username, email, and password credentials submitted via POST to https://infoabgviral.baby/. The site is an adult content platform of questionable legitimacy; collecting account credentials on such a platform poses a risk of credential harvesting, particularly since users may reuse passwords from other services. (location: page.html:789-829)
social engineering
Content titles use SEO keyword stuffing with real platform names (TikTok, FYP) and real-sounding Indonesian personal names (Tiara Andini, Salsabila, Hilda) combined with explicit sexual acts to create false impressions of leaked or viral celebrity/real-person content, manipulating users into clicking through. (location: page.html:354-366, 474-487)
hidden content
A Yandex Metrika tracking pixel is loaded with a hidden noscript image (position:absolute; left:-9999px) for covert analytics tracking of all visitors without visible disclosure. Combined with Histats.com analytics also injected, this site runs multiple covert tracking systems against users. (location: page.html:218)
malicious redirect
External script loaded from //weightydesire.com (page.html:196) is a known malvertising/redirect domain. The path structure with randomized alphanumeric tokens is consistent with ad fraud redirect chains that serve malicious payloads or redirect users to phishing/scam pages. (location: page.html:196)
curl https://api.brin.sh/domain/infoabgviral.babyCommon questions teams ask before deciding whether to use this domain in agent workflows.
infoabgviral.baby currently scores 40/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.