Is baur-afro-bled.hydr0.org safe?

cautionmedium confidence
58/100

context safety score

A score of 58/100 indicates minor risk signals were detected. The entity may be legitimate but has characteristics that warrant attention.

identity
100
behavior
60
content
37
graph
71

5 threat patterns detected

high

phishing

1 deceptive links where visible host does not match destination host

medium

malicious redirect

The subdomain baur-afro-bled.hydr0.org serves content cloned from mp3.cc (canonical URL, CSS, JS, and all links point to mp3.cc), while the canonical tag redirects to https://mp3.cc/t/1547423351-baur-afro-bled/. The hydr0.org domain acts as a shadow host that proxies/mirrors mp3.cc content under a different domain, confirmed by the 1 redirect detected in Tier 2 signals. (location: <link rel='canonical' href='https://mp3.cc/t/1547423351-baur-afro-bled/'> and domain baur-afro-bled.hydr0.org)

medium

brand impersonation

The page fully impersonates MP3.cc — including its logo, branding, site name in og:site_name, copyright notice '© 2017–2026 MP3.cc', and all navigation/content — while being hosted on the unrelated domain hydr0.org. This constitutes brand impersonation of MP3.cc on a third-party domain. (location: page.html: <title>, og:site_name, #foo-copyright, all href links pointing to mp3.cc)

medium

malicious redirect

All audio file download/play URLs route through fine.sunproxy.net, a third-party proxy domain not affiliated with mp3.cc. The data-url attributes for every playlist item use base64-encoded paths on fine.sunproxy.net. This intermediary proxy could redirect users, serve malware, or track user behaviour. 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: data-url='https://fine.sunproxy.net/file/<base64>...')

low

social engineering

The page presents itself as a legitimate music streaming/download service (MP3.cc) to encourage users to click play/download links that are proxied through fine.sunproxy.net, a third-party domain. This pattern is consistent with deceptive content delivery designed to funnel user traffic through an untrusted intermediary. (location: page.html: all playlist-play and playlist-down links using fine.sunproxy.net and mp3.cc respectively)

API

curl https://api.brin.sh/domain/baur-afro-bled.hydr0.org

FAQ: how to interpret this assessment

Common questions teams ask before deciding whether to use this domain in agent workflows.

Is baur-afro-bled.hydr0.org safe for AI agents to use?

baur-afro-bled.hydr0.org currently scores 58/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.

How should I interpret the score and verdict?

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.

How does brin compute this domain score?

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.

What do identity, behavior, content, and graph mean for this domain?

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.

Why does brin scan packages, repos, skills, MCP servers, pages, and commits?

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.

Can I rely on a safe verdict as a full security guarantee?

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.

When should I re-check before using an entity?

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.

Last Scanned

March 25, 2026

Verdict Scale

safe80–100
caution50–79
suspicious20–49
dangerous0–19

Trust Graph

Disclaimer

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.

start scoring agent dependencies.

integrate brin in minutes — one GET request is all it takes. query the api, browse the registry, or download the full dataset.