context safety score
A score of 53/100 indicates minor risk signals were detected. The entity may be legitimate but has characteristics that warrant attention.
phishing
1 deceptive links where visible host does not match destination host
brand impersonation
The page is served from bubaseta-masquad.hydr0.org but fully impersonates mp3.cc: the HTML title reads 'Bubaseta Masquad | Download mp3 free, listen music online - MP3.cc', the logo links to https://mp3.cc/, all navigation links point to mp3.cc subpaths, canonical and og:url tags reference https://mp3.cc/t/2434694372-bubaseta-masquad/, and all CSS/JS assets are loaded from mp3.cc. A user or agent visiting this domain would believe they are on the legitimate mp3.cc site. (location: page.html:5,9,11,14,18,19,33)
malicious redirect
One redirect was recorded during page fetch (per .brin-context.md). The serving domain bubaseta-masquad.hydr0.org is a subdomain of hydr0.org, not mp3.cc, yet the page presents itself entirely as mp3.cc. This redirect/domain mismatch is a hallmark of a traffic-hijacking mirror site routing users away from the legitimate service. (location: .brin-context.md:19, metadata.json:1)
obfuscated code
All four audio play URLs use double-base64-encoded paths routed through the third-party proxy fine.sunproxy.net (e.g. https://fine.sunproxy.net/file/NDgwdkFuTUxJZ0tH...). Decoding the blobs yields further base64-encoded binary data, obfuscating the actual file source and routing audio delivery through an opaque intermediary. This pattern hides the true origin of served files and evades direct URL analysis. (location: page.html:228,247,266,285)
malicious redirect
A link to https://looz.net/ is injected into the genre navigation sidebar using class='z__important' and target='_blank', opening an external third-party site in a new tab. This link is visually indistinguishable from the legitimate genre links (Pop, Dance, Rap, etc.) but redirects to an entirely different external domain. This matches the single 'deceptive link' flagged in the pre-scan context. (location: page.html:204)
curl https://api.brin.sh/domain/bubaseta-masquad.hydr0.orgCommon questions teams ask before deciding whether to use this domain in agent workflows.
bubaseta-masquad.hydr0.org currently scores 53/100 with a caution verdict and medium 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.