context safety score
A score of 47/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 on baddies-only-lil-cake-albert-breaker-feat-tayson-kryss.hydr0.org but the canonical URL, all navigation links, stylesheets, and scripts point to mp3.cc. The scanned domain acts as a redirect/mirror that funnels users to mp3.cc, confirmed by the single redirect detected in Tier 2 signals. The relationship between the hydr0.org subdomain operator and mp3.cc is opaque. (location: page.html:9 (canonical link), page.html:18-19 (external resources from mp3.cc))
brand impersonation
The site fully clones the MP3.cc brand — logo, title tag, meta og:site_name, footer copyright '© 2017–2026 MP3.cc', and all navigation links — while being served from a completely different domain (hydr0.org). Users and AI agents have no indication they are not on the legitimate mp3.cc domain. (location: page.html:5 (title), page.html:11 (og:site_name), page.html:310 (footer copyright))
hidden content
Four suspicious base64 blobs are embedded in the data-url attributes of playlist-play anchor tags (e.g., data-url values pointing to fine.sunproxy.net/file/<long-base64-string>/). These base64 strings are opaque encoded paths used to route MP3 file requests through the sunproxy.net proxy, obscuring the true origin and destination of served media files. (location: page.html:228, page.html:247, page.html:266, page.html:285 (data-url attributes))
malicious redirect
All audio file play requests are proxied through fine.sunproxy.net rather than served directly. The sunproxy.net domain acts as an intermediary for media delivery, which could be used to track users, serve malicious payloads, or redirect to alternate content. The base64-encoded path segments obscure the actual file routing logic. (location: page.html:228 (data-url https://fine.sunproxy.net/file/NDgwdk...))
social engineering
The deceptive link flagged in Tier 2 corresponds to the 'Online Radio' sidebar link pointing to looz.net (an external third-party domain), presented within the navigation as if it were part of the MP3.cc service. The link opens in a new tab (_blank) and is styled identically to internal genre links, making it appear as a native feature. (location: page.html:204 (a href='https://looz.net/' class='z__important no-ajax' target='_blank'))
curl https://api.brin.sh/domain/baddies-only-lil-cake-albert-breaker-feat-tayson-kryss.hydr0.orgCommon questions teams ask before deciding whether to use this domain in agent workflows.
baddies-only-lil-cake-albert-breaker-feat-tayson-kryss.hydr0.org currently scores 47/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.