context safety score
A score of 35/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
Two scripts loaded directly from 'violentlinedexploit.com' — a domain whose name strongly signals malicious intent. These are unconditional script tags that execute arbitrary remote code on page load, capable of drive-by downloads, redirects, or payload delivery. (location: page.html:425 — <script src="https://violentlinedexploit.com/b2/c3/24/b2c32452aa7125e7323eb6ed0cc4a7cb.js"> and <script src="https://violentlinedexploit.com/ef/69/a3/ef69a304a9548c2f7a37a8a89137ee32.js">)
obfuscated code
Popunder ad network script uses Base64-encoded URLs in an array (e.g. 'd3d3LnZpc2FyaW9tZWRpYS5jb20v...') decoded at runtime via atob(), with fallback chaining across multiple CDN domains and a hardcoded expiry timestamp (1798459558000). This pattern is characteristic of obfuscated malvertising loaders that conceal their true payload destinations. (location: page.html:424 / page-text.txt:222 — inline script block with atob(q[s]) loader)
malicious redirect
Three separate ad injection scripts dynamically load from 'immaterialmarriage.com' using long obfuscated path URLs with no-referrer-when-downgrade policy. This third-party domain is unrelated to any legitimate ad network and the obfuscated paths are consistent with malvertising redirect chains. (location: page.html:210,355 / page-text.txt:12,155 — s.src = '//immaterialmarriage.com/b.XIVjsHd/...' and '//immaterialmarriage.com/bxXfV.sYdfG/...')
malicious redirect
Ad injection script dynamically loads from 'downrightfootball.com' using a long obfuscated path, injected via dynamic script element creation. Domain is unrelated to any known legitimate ad network and the pattern matches malvertising payload delivery. (location: page.html:430 / page-text.txt:228 — s.src = '//downrightfootball.com/bDXYVls.dGGplk0xYYWxcn/...')
hidden content
A 1x1 pixel hidden iframe (position:absolute, top:0, left:0, border:none, visibility:hidden) is injected into the page body and used to load Cloudflare challenge scripts. While Cloudflare bot protection is legitimate, the hidden iframe pattern can also be abused for clickjacking or invisible content loading. (location: page.html:434 — iframe with height=1, width=1, style visibility:hidden)
social engineering
Multiple video titles exploit non-consensual voyeurism framing ('Hidden Ceiling Cam Records...', 'Husband Records Secretly From Window', 'Delhi-Meerut Metro Couple Viral MMS Caught on CCTV') to attract clicks. This normalizes and monetizes non-consensual recording, and such content is frequently used as lures in malvertising campaigns. (location: page.html:337-340,250-252,387-390 — video titles referencing hidden cameras and leaked/viral MMS)
social engineering
Page deploys a right-click disabler, F12 key blocker, and Ctrl+Shift+I/J/C/S blockers via the 'disabled-source-and-content-protection' plugin, actively preventing users and security researchers from inspecting page source or scripts. This anti-analysis behavior is commonly paired with malicious ad injection to hinder detection. (location: page.html:417 / page-text.txt:215 — jh_disabled_options_data with disabled_f12, disabled_ctst_i, disabled_ctst_j, disabled_ctst_c all set to '1')
curl https://api.brin.sh/domain/mastiraja.comCommon questions teams ask before deciding whether to use this domain in agent workflows.
mastiraja.com currently scores 35/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.