context safety score
A score of 45/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 conditionally redirects based on referrer or user-agent
obfuscated code
All JavaScript on the page (30+ script tags) uses a non-standard type attribute 'c6d7cb29668892de3a6fa7cc-text/javascript' instead of 'text/javascript'. This is a known technique used by ad-blocker bypass plugins (deblocker) to prevent content security scanners and ad blockers from identifying and blocking scripts. The random hex prefix obfuscates the script type so browsers still execute them (as unknown MIME types fall back to execution in some contexts) while evading automated detection. (location: page.html: all <script> tags, type attribute prefix 'c6d7cb29668892de3a6fa7cc')
obfuscated code
A base64-encoded JavaScript configuration blob is stored in the variable 'Databccbdc'. When decoded it contains doubly-nested base64 strings: one resolving to 'https://pagead2.googlesyndication.com/pagead/js/adsbygoogle.js' and another to 'https://sgxnifty.org/wp-content/plugins/deblocker/'. This multi-layer encoding is used to hide the true payload and bypass static analysis of ad-blocker detection code. (location: page.html line 3: var Databccbdc = ["eyJ..."])
hidden content
The deblocker plugin enforces an overlay modal (blur + dark overlay at rgba(0,0,0,0.75)) that blocks page content until the user disables their ad blocker. The modal configuration is concealed inside a double-base64 encoded blob. The 'cross: off' setting removes the dismiss button, forcing user compliance. This constitutes manipulative hidden configuration controlling user interaction. (location: page.html line 3: decoded Databccbdc config — overlay:on, blur:on, button:off, cross:off)
social engineering
The deblocker overlay displays the message 'Please disable Adblocker !' with step-by-step instructions to disable browser security extensions. The modal cannot be dismissed (cross:off, button:off) and loops until the user complies. This coerces users into weakening their browser defenses to access financial market data they sought, a social engineering pattern that increases exposure to malicious ads. (location: page.html line 3: decoded Databccbdc — title, guideTranslation fields)
malicious redirect
A third-party video ad script is loaded from 'https://live.primis.tech/live/liveView.php?s=119775'. Primis.tech is a video ad network known to serve interstitial and redirect-style ad units. Loading external PHP-based ad scripts introduces risk of malicious redirect chains through the ad network outside the site operator's control. (location: page.html: <script src="https://live.primis.tech/live/liveView.php?s=119775">)
curl https://api.brin.sh/domain/sgxnifty.orgCommon questions teams ask before deciding whether to use this domain in agent workflows.
sgxnifty.org currently scores 45/100 with a suspicious verdict and medium 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.