context safety score
A score of 37/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
phishing
1 deceptive links where visible host does not match destination host
malicious redirect
Third-party script loaded from 'deliveredlivestock.com' — a suspicious domain with an obfuscated path injected into the page head. This is a known pattern for malvertising/redirect chains used to push users to phishing or exploit pages. (location: page.html:31 — //deliveredlivestock.com/hCZDlfV/28UyGcjHUjA8U_/ztxaB5P_sw8KO3/QJWIP/7NoGiaUUnj3eEpi/JmSSl/98kckG/v7Ts4urZOENzE2eSFK/kiV/0ulngbzeRUdptmQLPqyU/3R5U/WHrG11hqdVV0f/q)
malicious redirect
Script dynamically injected from 'pusishegre.com' via obfuscated self-executing function. The domain name is randomly-looking and the path is heavily obfuscated, consistent with push-notification hijacking or drive-by redirect malware. (location: page.html:570-579 — s.src = '//pusishegre.com/ccDO9G6kb.2p5/...')
malicious redirect
Script loaded from 'absorptionservant.com' — a suspicious low-reputation domain used twice on the page (invoke.js and a second JS file). This domain pattern is associated with malvertising networks that redirect users to scam/phishing pages. (location: page.html:540 and page.html:583 — //absorptionservant.com/...)
malicious redirect
Ad script loaded from 'profitableratecpm.com' with a long hash path. This is a known ad network associated with aggressive redirects and malvertising chains that can redirect users to credential-harvesting or scam pages. (location: page.html:316 — //pl15210141.profitableratecpm.com/561a188c423013c862658ba536ecd826/invoke.js)
obfuscated code
All script tags have their type attribute set to a non-standard value '34a53e2186d60736d598803f-text/javascript'. This is a Cloudflare Rocket Loader obfuscation technique that defers script execution and can mask the true behavior of malicious scripts from static scanners. The same hash is used as a cf-settings value in the rocket-loader script, confirming deliberate obfuscation of all third-party ad/tracker scripts. (location: page.html:11,12,13,21,22,31,129,138,531,540,570,583 — type='34a53e2186d60736d598803f-text/javascript')
obfuscated code
Inline script at page bottom uses a self-executing anonymous function to dynamically create an invisible 1x1 iframe with position:absolute, visibility:hidden, then injects a script into it. This is a classic technique to execute hidden code outside the main document context, evading content security inspection. (location: page.html:586 — Cloudflare challenge iframe injection with hidden iframe (height=1, width=1, visibility:hidden))
social engineering
Page text instructs users to use a VPN to view blocked videos ('အချို့ Videoများကို မမြင်ရပါက VPN လေးခံကြည့်ပေးပါခင်ဗျာ'). This social engineering tactic encourages users to bypass network-level protections, increasing exposure to malicious content and ad redirects on the site. (location: page.html:121 / page-text.txt:68)
curl https://api.brin.sh/domain/buumal.comCommon questions teams ask before deciding whether to use this domain in agent workflows.
buumal.com currently scores 37/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.