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.
encoded payload
suspicious base64-like blobs detected in page content
malicious redirect
The scanned URL (bad-meets-evil-fast-lane-ft-eminem-royce-da-5-9.hydr0.org) is a subdomain typosquat/clone that mirrors content from mp3.cc, with a canonical tag redirecting to https://mp3.cc/t/125012762-bad-meets-evil-fast-lane-ft-eminem-royce-da-5-9/. The page was reached via hydr0.org but presents itself as mp3.cc, constituting a redirect/impersonation setup. The brin-context also confirms 1 redirect was detected. (location: page.html:9 - canonical href and domain mismatch (hydr0.org vs mp3.cc))
brand impersonation
The page fully impersonates the legitimate MP3.cc website — replicating its branding, logo, layout, CSS/JS assets loaded directly from mp3.cc, and OG metadata claiming site_name=MP3.cc. The actual serving domain is hydr0.org, not mp3.cc, creating a deceptive brand impersonation. All stylesheets and scripts are pulled from https://mp3.cc/i/css/_main_min.css and https://mp3.cc/i/js/_main_min.js while the page is served from a different domain. (location: page.html:5,11,18,19,33 - title, og:site_name, assets, and logo all reference MP3.cc while served from hydr0.org)
malicious redirect
All MP3 audio files are served through a third-party proxy domain 'fine.sunproxy.net' rather than directly. The data-url attributes on play links point to https://fine.sunproxy.net/file/[base64-encoded-path], meaning all audio streaming is routed through an intermediary proxy that can track, intercept, or serve malicious payloads. This is consistent with the 12 suspicious base64 blobs flagged in the pre-scan context. (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 attributes pointing to fine.sunproxy.net)
hidden content
The 12 suspicious base64 blobs flagged in the pre-scan are the encoded file paths embedded in data-url attributes on all playlist play links (e.g., NDgwdkFuTUxJZ0tH...). These encode opaque parameters passed to the sunproxy.net intermediary. While they appear to be obfuscated file retrieval tokens rather than injected payloads, the encoding obscures the actual resource paths and proxy parameters from inspection. (location: page.html:228,247,266 etc. - data-url base64 strings in playlist-play anchor tags)
social engineering
The site operates as an unauthorized MP3 download portal serving copyrighted music (Eminem, Royce Da 5'9) for free download, luring users with pirated content. The hydr0.org domain is branded as a proxy/mirror of mp3.cc. Users seeking free music downloads are directed through a third-party proxy (sunproxy.net) with no indication of the actual file origin, creating a social engineering vector where trust in the MP3.cc brand is exploited to drive traffic through the hydr0.org/sunproxy.net infrastructure. (location: page.html:224-623 - full playlist section with download links; footer hydrofm@yandex.com contact)
curl https://api.brin.sh/domain/bad-meets-evil-fast-lane-ft-eminem-royce-da-5-9.hydr0.orgCommon questions teams ask before deciding whether to use this domain in agent workflows.
bad-meets-evil-fast-lane-ft-eminem-royce-da-5-9.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.
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.