context safety score
A score of 50/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
malicious redirect
The page is served from babe-rexa.hydr0.org but all canonical URLs, assets (CSS/JS), and links point to mp3.cc. The canonical tag (line 9) explicitly redirects canonical authority to https://mp3.cc/t/928711833-babe-rexa/. This subdomain acts as a proxy/mirror for mp3.cc content, consistent with the 1 redirect flagged in Tier 2 pre-scan data, and may be used to route users through an uncontrolled intermediary domain. (location: page.html:9 - <link rel="canonical" href="https://mp3.cc/t/928711833-babe-rexa/">)
malicious redirect
All MP3 audio file URLs are served via fine.sunproxy.net, a third-party proxy domain distinct from both the hosting domain (babe-rexa.hydr0.org) and the canonical brand domain (mp3.cc). Audio play requests are routed through this intermediary, which could facilitate traffic interception, data collection, or malware delivery via media files. This is the deceptive link flagged in Tier 2 (deceptive_link_count: 1). (location: page.html:228 - data-url="https://fine.sunproxy.net/file/NDgwdkFu...")
brand impersonation
The site fully impersonates MP3.cc — including its logo SVG, branding, CSS/JS assets loaded from mp3.cc, footer copyright '© 2017-2026 MP3.cc', and all navigation links pointing to mp3.cc — while being hosted on an entirely different domain (babe-rexa.hydr0.org). Users visiting this domain would believe they are on the legitimate MP3.cc site. The canonical link attempts to mask this by pointing back to mp3.cc, but the actual serving domain is babe-rexa.hydr0.org. (location: page.html:5,9,18,19,33,671 - title, canonical, assets, logo, footer all reference MP3.cc brand)
hidden content
The 12 suspicious base64 blobs flagged in Tier 2 are present in the data-url attributes of playlist play buttons. Each blob (e.g. NDgwdkFuTUxJZ0tH...) is a base64-encoded string passed to fine.sunproxy.net as an opaque file path parameter. The content of these encoded strings is not transparent to the user or easily auditable, and could encode tracking parameters, session tokens, or redirect targets beyond the visible MP3 file names embedded in the decoded filenames. (location: page.html:228,247,266,285,304,323,342,361,380,399,418,437 - data-url attributes with base64 path segments)
curl https://api.brin.sh/domain/babe-rexa.hydr0.orgCommon questions teams ask before deciding whether to use this domain in agent workflows.
babe-rexa.hydr0.org currently scores 50/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.