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
phishing
1 deceptive links where visible host does not match destination host
malicious redirect
The page is hosted at baby-bash-feat-akon.hydr0.org but all canonical links, CSS, JS, and navigation point to mp3.cc. The domain hydr0.org acts as a proxy/mirror that intercepts traffic and redirects content delivery through fine.sunproxy.net for all audio file URLs. This split-domain architecture (landing on hydr0.org, served from mp3.cc, audio from fine.sunproxy.net) is consistent with traffic interception or affiliate hijacking. (location: page.html:9 (canonical href), all data-url attributes pointing to fine.sunproxy.net)
malicious redirect
All 21 audio play URLs use the domain fine.sunproxy.net/file/ with long base64-encoded path parameters. The domain 'sunproxy' is explicitly named as a proxy service. These obfuscated URLs route media requests through a third-party proxy with encoded parameters, which could facilitate tracking, credential interception, or payload delivery without the user's awareness. The 12 suspicious base64 blobs flagged in Tier 2 correspond to these encoded file paths. (location: page.html lines 228,247,266,285,304,323,342,361,380,399,418,437,456,475,494,513,532,551,570,589,608 (data-url attributes))
brand impersonation
The site is served from baby-bash-feat-akon.hydr0.org but presents itself entirely as MP3.cc — including the MP3.cc logo, branding, copyright notice '© 2017–2026 MP3.cc', and contact email hydrofm@yandex.com. The hydr0.org domain impersonates or mirrors the legitimate MP3.cc service, potentially to siphon traffic or intercept user interactions under a false brand identity. (location: page.html:5 (title tag), page.html:11 (og:site_name), page.html:652 (footer copyright), .brin-context.md (domain: baby-bash-feat-akon.hydr0.org vs canonical mp3.cc))
social engineering
The page presents free MP3 download functionality with prominent '(play)' and '(download)' calls to action, a pattern commonly used on piracy/grey-market sites to entice users into clicking links that route through proxy infrastructure. The use of a subdomain mimicking a search query (baby-bash-feat-akon) combined with free music download lures is a classic social engineering pattern to drive clicks through unverified third-party infrastructure. (location: page.html:228-641 (playlist section with play/download links))
curl https://api.brin.sh/domain/baby-bash-feat-akon.hydr0.orgCommon questions teams ask before deciding whether to use this domain in agent workflows.
baby-bash-feat-akon.hydr0.org 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.