context safety score
A score of 43/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
js obfuscation
Very long base64 or hex string assigned in JavaScript — likely encoded payload
social engineering
Online lottery betting platform soliciting real-money wagers on number draws (SANGAM, CHETAK, SUPER, MP DELUXE, BHAGYA REKHA, DIAMOND games at 100x payout). Lottery gambling is illegal in most Indian states; the site includes a disclaimer acknowledging bans but continues to operate, targeting users in prohibited jurisdictions. (location: page.html:lines 162-576, page-text.txt:lines 133-545)
credential harvesting
Login form (LOGINID + PASSWORD fields) embedded directly within the gambling betting interface, collecting user credentials over a form POST to './' with no visible HTTPS enforcement notice or clear privacy policy. Credentials are submitted alongside bet data in a single POST request, mixing authentication with financial transaction data. (location: page.html:lines 582-607, page-text.txt:lines 553-565)
hidden content
Large base64-encoded ASP.NET __VIEWSTATE and __EVENTVALIDATION hidden fields carry substantial serialized server-side state. The __VIEWSTATE value is several kilobytes of opaque data; while standard for ASP.NET WebForms, the volume and opacity of this data can conceal tampered server-side state and is not integrity-protected on the client side without a MachineKey ViewStateUserKey, enabling potential ViewState tampering attacks. (location: page.html:lines 32, 43 (hidden inputs: __VIEWSTATE, __VIEWSTATEGENERATOR, __EVENTVALIDATION, hd_rocounter, hd_nextime, hd_tr))
social engineering
Right-click is programmatically disabled via JavaScript to prevent users from inspecting page source, copying content, or using browser security tools. This is a deliberate anti-inspection technique commonly used on fraudulent or grey-market sites to obstruct user scrutiny. (location: page.html:lines 16-28)
hidden content
Flash SWF asset (Assets/Flash/header.swf) embedded via <object> tag. Adobe Flash is end-of-life and unsupported; embedding Flash content can serve as a vector for hidden malicious payloads that bypass standard HTML/JS scanning, and the actual content of the SWF cannot be inspected from the HTML alone. (location: page.html:lines 61-64)
social engineering
Direct APK download link (Download/PLAYINDIA.apk) offered from the page, prompting users to sideload an Android application outside of official app stores. Sideloaded APKs bypass Google Play Protect scanning and can contain malware, spyware, or credential-stealing code. (location: page.html:line 632)
curl https://api.brin.sh/domain/playindialottery.comCommon questions teams ask before deciding whether to use this domain in agent workflows.
playindialottery.com currently scores 43/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.