context safety score
A score of 42/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 checks user-agent for bot/crawler strings to serve different content
obfuscated code
All script tags use a non-standard type attribute '10aa357c9d58f820c34b60b2-text/javascript' — a hash-prefixed MIME type used by Cloudflare Rocket Loader to defer execution. While Rocket Loader is legitimate, this pattern prevents direct static analysis of which scripts execute and in what order, and is a known technique for hiding malicious payloads from scanners that only parse scripts with type='text/javascript'. (location: page.html — all <script> tags, e.g. <script src=https://cdnjs.cloudflare.com/ajax/libs/jquery/3.5.1/jquery.js type="10aa357c9d58f820c34b60b2-text/javascript">)
hidden content
Inline JavaScript performs Googlebot/crawler cloaking: checks navigator.userAgent for 'googlebot', 'adsbot', and 'mediapartners-google' and conditionally loads content from a suspicious endpoint (porn.nungxxx.net/wp-content/plugins/v/xxx.php) into 17 ad slots ONLY for non-bot, non-Google users. This is a cloaking technique that serves different content to crawlers vs. real users, which can be used to deliver malicious ads or redirects while evading detection. (location: page.html — inline script: var isGoogleBotUA3=/googlebot|adsbot|mediapartners-google/.test(ua3); ... $(elementId).load('https://porn.nungxxx.net/wp-content/plugins/v/xxx.php'))
malicious redirect
The scanned URL is nungxxx.net but the canonical URL, OG URL, and all internal links point to porn.nungxxx.net. The root domain silently redirects visitors to the subdomain. This subdomain-based redirect pattern can be used to bypass blocklists applied to the root domain. (location: page.html — <link rel=canonical href=https://porn.nungxxx.net/> and metadata.json url: https://nungxxx.net)
hidden content
Histats tracker (s10.histats.com/js15_gif_as.js) is injected with a fixed-position overlay div (#histatsC positioned fixed at top:0px, left:0px) via inline CSS in the tracker configuration string. This creates an invisible fixed-position element covering the page, which can intercept clicks, overlay content, or deliver unsolicited UI elements to users. (location: page.html — Histats inline script: _Hasync.push(['Histats.startgif','1,4834433,4,10049,"div#histatsC {position: absolute;top:0px;left:0px;}body>div#histatsC {position: fixed;}"']))
social engineering
The site features a navigation menu item 'หาเงินกับเว็บ18+' (Thai: 'Earn money with 18+ website'), which is a social engineering lure targeting users with financial incentives to engage with adult content monetization schemes. This pattern is commonly used to recruit unwitting affiliates or harvest personal/payment information. (location: page-text.txt — navigation menu item: หาเงินกับเว็บ18+)
curl https://api.brin.sh/domain/nungxxx.netCommon questions teams ask before deciding whether to use this domain in agent workflows.
nungxxx.net currently scores 42/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.