context safety score
A score of 46/100 indicates multiple risk signals were detected. This entity shows patterns commonly associated with malicious intent.
phishing
4 deceptive links where visible host does not match destination host
malicious redirect
The page is hosted on a subdomain (dr-alban-let-the-beat.hydr0.org) that mimics the MP3.cc service brand while all canonical links, CSS, JS, and navigation point to mp3.cc. The subdomain uses a redirect to serve mp3.cc content, creating a domain-spoofing proxy. The canonical tag explicitly declares the true origin as https://mp3.cc/t/1819812777-dr-alban-let-the-beat/, confirming this is a mirrored/proxied copy on a different domain. (location: page.html:9 - <link rel="canonical" href="https://mp3.cc/t/1819812777-dr-alban-let-the-beat/">)
brand impersonation
The site at hydr0.org fully replicates the MP3.cc brand identity including logo, site name, navigation, footer copyright ('© 2017 – 2026 MP3.cc'), and all UI elements. All resources (CSS, JS, fonts) are loaded from mp3.cc. The domain hydr0.org is unrelated to mp3.cc but presents itself as if it were the legitimate MP3.cc service. This constitutes brand impersonation of MP3.cc. (location: page.html:5,18,19,33,628-633)
malicious redirect
All audio file play URLs route through fine.sunproxy.net, a third-party proxy domain not affiliated with mp3.cc. The sunproxy.net domain intercepts all media requests, enabling potential traffic interception, data collection, or substitution of malicious payloads for audio files. Users believe they are interacting with mp3.cc but media is proxied through an unknown third-party intermediary. (location: page.html:228,247,266,285,304,323,342,361,380,399,418,437,456,475,494,513,532,551,570,589,608 - data-url="https://fine.sunproxy.net/file/...")
obfuscated code
All 20 audio file URLs routed through fine.sunproxy.net contain long Base64-encoded path segments (e.g. YVlGMWFTTXN3M0VjVThHdEhvZHd2aEUvN0prK0gveUhuWkRVNlhBOTBn...). These blobs are opaque and cannot be inspected to verify the actual file destination, consistent with the 12 suspicious base64 blobs flagged in the Tier 2 scan. This obfuscation hides the true file endpoints. (location: page.html:228,247,266,285,304,323,342,361,380,399,418,437,456,475,494,513,532,551,570,589 - data-url base64 path segments in fine.sunproxy.net URLs)
social engineering
The page presents free MP3 downloads of copyrighted music (Dr. Alban tracks) to lure users into interacting with the site. This is a common social engineering lure used to drive traffic and clicks through piracy content, potentially exposing users to unwanted third-party intermediary domains (sunproxy.net) under the guise of a legitimate music service. (location: page.html:224 - playlist of copyrighted music offered for free download)
curl https://api.brin.sh/domain/dr-alban-let-the-beat.hydr0.orgCommon questions teams ask before deciding whether to use this domain in agent workflows.
dr-alban-let-the-beat.hydr0.org currently scores 46/100 with a suspicious 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.