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
cloaking
Page conditionally redirects based on referrer or user-agent
cloaking
Page loads content in transparent or zero-size iframe overlay
js obfuscation
JavaScript uses Function constructor for runtime code generation
brand impersonation
The site uses the name '888PG Official Genuine' and domain '888pg-ox.vip' to impersonate or clone the legitimate PG Soft/888PG gaming brand. The meta og:title explicitly claims 'Official Genuine' status, a classic impersonation tactic to establish false legitimacy. The CDN assets are served from 'cdntoos.cf888pg.com', a lookalike domain not associated with the official PG Soft infrastructure. (location: page.html: <meta property=og:title content='888PG Official Genuine'>, metadata.json: domain=888pg-ox.vip)
social engineering
The page description promises extremely large monetary bonuses ('Convide amigos para receber R$ 18,88/pessoa, e o bônus máximo chega a R$ 888.888,88') — translated: 'Invite friends to receive R$18.88/person, and the maximum bonus reaches R$888,888.88'. This is a classic social engineering lure using unrealistic financial incentives to attract victims and harvest their account/payment credentials. (location: page.html: <meta name=description content='Convide amigos para receber R$ 18,88/pessoa, e o bônus máximo chega a R$ 888.888,88'>)
credential harvesting
The site presents itself as an online gambling/gaming lobby ('data-template-type=lobby') with referral bonuses and large prize incentives. Such platforms typically require account registration with personal and financial information. Combined with the impersonation of a legitimate brand and use of a suspicious .vip TLD with an 'ox' subdomain pattern, this strongly indicates a credential and payment data harvesting operation targeting gambling users. (location: page.html: data-template-type=lobby, metadata.json: domain=888pg-ox.vip)
malicious redirect
The page-text.txt reveals JavaScript that unconditionally redirects users: 'window.location.href="/pages/browser/index.html?from="+encodeURIComponent(window.location.href)'. This redirect passes the originating URL as a parameter, which can be used for tracking, phishing chain construction, or redirecting users to malicious payloads based on browser fingerprinting. Additionally, a noscript iframe loads '/pages/noscript/pt.html' for users without JavaScript. (location: page-text.txt: window.location.href='/pages/browser/index.html?from='+encodeURIComponent(window.location.href))
brand impersonation
Keywords in meta tags include well-known legitimate PG Soft game titles ('Fortune Snake', 'Fortune Rabbit', 'Fortune Tiger', 'Fortune Dragon', 'Gates of', 'Joker's Jewels', 'Crazy777') to achieve SEO poisoning — making the fraudulent site appear in searches for legitimate games, luring users who intend to visit the real platform. (location: page.html: <meta name=keywords content='888PG、Fortune Snake、Fortune Rabbit、Fortune Tiger、Fortune Dragon、Fortune Ox、Fortune Mouse、Lucky Neko、Piggy Gold、Fortune Gems、Gates of、Money Coming、Joker's Jewels、Crazy777'>)
hidden content
The page uses an 'antiban' CSS overlay (position:fixed, z-index:99999, full viewport coverage with white background) that can be activated to hide the page's true content from automated scanners or display alternate content to specific visitors. This is a cloaking mechanism commonly used to evade detection while showing malicious content to real users. (location: page-text.txt: .antiban{position:fixed;left:0;right:0;top:0;bottom:0;background-color:#fff;z-index:99999})
curl https://api.brin.sh/domain/888pg-ox.vipCommon questions teams ask before deciding whether to use this domain in agent workflows.
888pg-ox.vip 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.