context safety score
A score of 36/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
brand impersonation
The page is hosted on a third-party subdomain (bad-meets-evil-bruno-mars.hydr0.org) but presents itself entirely as MP3.cc, including the MP3.cc logo, branding, copyright notice, and canonical URL pointing to mp3.cc. The hydr0.org domain is impersonating/mirroring the MP3.cc brand without being the legitimate MP3.cc domain. (location: page.html:5,9,11,14,33-36,671 - title, canonical, og:site_name, logo, footer copyright)
malicious redirect
The canonical link tag redirects to https://mp3.cc/t/4089202352-bad-meets-evil-bruno-mars/ on a different domain. The page was reached via hydr0.org but all canonical and og:url metadata point to mp3.cc, indicating a redirect/mirror relationship where users land on hydr0.org but content claims to originate from mp3.cc. (location: page.html:9 - <link rel="canonical" href="https://mp3.cc/t/4089202352-bad-meets-evil-bruno-mars/">)
malicious redirect
All MP3 audio files are served through fine.sunproxy.net, a third-party proxy domain. Users clicking play or download are routed through fine.sunproxy.net which intercepts all file requests. This proxy layer could be used for traffic interception, malware delivery, or tracking. (location: page.html:228,247,266,285,304,323,342,361,380,399,418,437,456,475,494,513,532,551,570,589,608,627 - data-url attributes pointing to fine.sunproxy.net)
brand impersonation
All static assets (CSS, JS, fonts, images) are loaded from mp3.cc (e.g., https://mp3.cc/i/css/_main_min.css, https://mp3.cc/i/js/_main_min.js), while the page is served from hydr0.org. This creates a convincing clone of MP3.cc without authorization, constituting brand impersonation of the legitimate mp3.cc service. (location: page.html:18,19 - stylesheet and script src pointing to mp3.cc)
social engineering
One track listing includes 'eminem50cent.ru' embedded directly in the song title text ('Lighters feat Bruno Mars)(eminem50cent.ru'), which is a known technique to promote third-party piracy sites by embedding domain names in music metadata displayed to users. (location: page.html:552,557 - playlist item title containing eminem50cent.ru domain reference)
hidden content
12 suspicious base64 blobs were flagged by heuristic analysis (per .brin-context.md). The base64 strings in data-url attributes of audio play links (e.g., NDgwdkFuTUxJZ0tHbEJUVFE0QUZzMjJBeit2dnUv...) are opaque encoded file paths routed through fine.sunproxy.net. While these appear to be encoded audio file paths, the encoding obscures the true destination URLs from casual inspection. (location: page.html:228,247,266,285,304,323,342,361,380,399,418,437,456,475,494,513,532,551,570,589,608,627 - base64-encoded path segments in fine.sunproxy.net URLs)
curl https://api.brin.sh/domain/bad-meets-evil-bruno-mars.hydr0.orgCommon questions teams ask before deciding whether to use this domain in agent workflows.
bad-meets-evil-bruno-mars.hydr0.org currently scores 36/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.