context safety score
A score of 39/100 indicates multiple risk signals were detected. This entity shows patterns commonly associated with malicious intent.
hidden instruction
high hidden content ratio detected in DOM
encoded payload
suspicious base64-like blobs detected in page content
js obfuscation
JavaScript uses Function constructor for runtime code generation
social engineering
The site cricbet99.green operates as an online cricket betting/gambling platform. The page is a single-page Angular app that renders no visible text content (page-text.txt is blank), hiding its true purpose from static scanners while delivering a full gambling interface via JavaScript bundles. This pattern is commonly used to evade content-based detection systems. (location: page.html: <app-root> body, main.76cd4e640a5fcef37e97.js)
hidden content
A commented-out IP harvesting script was found in the HTML source. The code loads https://api.ipify.org?format=jsonp&callback=getIP and calls document.write() with the visitor's public IP address. Although currently commented out, its presence indicates prior or intended visitor IP collection without disclosure. (location: page-hidden.txt lines 7-13, page.html lines 22-28)
hidden content
A commented-out Facebook Meta Pixel tracking block (Pixel ID: 1949390595505532) is embedded in the HTML source. While inactive, it was previously used for covert behavioral tracking and audience profiling of visitors, consistent with credential-harvesting and social engineering campaign infrastructure. (location: page-hidden.txt lines 14-30, page.html lines 30-45)
hidden content
The page title is simply 'Index' with empty meta description and keywords tags, deliberately providing no identifying information. Combined with the blank visible text content, this is consistent with cloaking — serving different content to crawlers versus browsers to evade detection. (location: page.html lines 5, 7-8)
social engineering
The domain name 'cricbet99' combines a popular sport (cricket) with a betting brand pattern ('bet99'), a well-known technique to exploit fan interest and cultural affinity to lure users into unregulated gambling. The .green TLD adds a veneer of legitimacy while the brand is unregistered/unlicensed. (location: metadata.json: domain cricbet99.green)
obfuscated code
The page loads multiple content-hashed JavaScript bundles (main.76cd4e640a5fcef37e97.js, scripts.4220f4c72c81af4d0167.js, polyfills.39bc949cc6cfccc9e4b0.js, runtime.f85a0a451237e46bd1d0.js) via deferred script tags. The entire application logic, including any credential harvesting, redirect, or tracking code, is hidden inside these opaque bundles and not inspectable from static HTML analysis alone. (location: page.html line 64)
curl https://api.brin.sh/domain/cricbet99.greenCommon questions teams ask before deciding whether to use this domain in agent workflows.
cricbet99.green 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.