context safety score
A score of 52/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
brand impersonation
The page is hosted on a subdomain of hydr0.org (back-staba-israel-vibration-instrumental.hydr0.org) but impersonates MP3.cc — all canonical links, og:url, logo, CSS, JS, and content point to mp3.cc. The site presents itself as MP3.cc while operating under a different domain, deceiving users about the true origin of the content and downloads. (location: page.html:5,9,14,18,19,33)
malicious redirect
The page includes a single redirect (flagged in Tier 1/2 pre-scan). The canonical URL points to https://mp3.cc/t/3719894276-back-staba-israel-vibration-instrumental/ while the actual serving domain is hydr0.org — indicating the site may redirect users or was reached via a redirect from the legitimate mp3.cc domain. (location: .brin-context.md:19, page.html:9)
malicious redirect
MP3 file download and play links use a third-party proxy domain 'fine.sunproxy.net' with base64-encoded URL parameters. These obfuscated URLs route audio file requests through an intermediary proxy, which could serve malicious files, track users, or redirect to unintended destinations. The filenames in the URLs embed 'Hydr0.org' branding, confirming the proxy is controlled by the site operator. (location: page.html:228,247)
hidden content
Two suspicious base64 blobs were flagged by Tier 2 analysis. The data-url attributes on play links contain long base64-encoded strings passed to fine.sunproxy.net, obfuscating the actual file paths and destinations. While decoded filenames appear benign (mp3 files), the encoding hides the true resource locations from casual inspection. (location: page.html:228,247)
social engineering
The page presents itself as a legitimate MP3 download service (MP3.cc) but is served from a typosquat-style subdomain on hydr0.org. The contact email 'hydrofm@yandex.com' in the footer and 'Hydr0.org' embedded in download filenames reveal the true operator identity, while the UI fully mimics MP3.cc to build false trust and induce users to download files from unverified proxy sources. (location: page.html:272,228,247)
curl https://api.brin.sh/domain/back-staba-israel-vibration-instrumental.hydr0.orgCommon questions teams ask before deciding whether to use this domain in agent workflows.
back-staba-israel-vibration-instrumental.hydr0.org currently scores 52/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.