context safety score
A score of 41/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 the subdomain 'feel-it-michele-morrone.hydr0.org' but presents itself as 'MP3.cc', with canonical URLs, all internal links, CSS, and JS pointing exclusively to mp3.cc. The subdomain acts as a shadow/mirror site that impersonates the legitimate MP3.cc service while operating under the unrelated hydr0.org domain. A redirect (1 detected in Tier 2) leads users from the typosquat/shadow domain to the branded MP3.cc experience. (location: page.html:9 (canonical), page.html:5 (title), metadata.json (domain: feel-it-michele-morrone.hydr0.org))
brand impersonation
The site fully impersonates MP3.cc — including its logo, branding, site name, navigation, footer copyright '© 2017–2026 MP3.cc', and all resource URLs — while being served from the unrelated domain 'feel-it-michele-morrone.hydr0.org'. This constitutes unauthorized brand impersonation of MP3.cc on a third-party domain. (location: page.html:5 (title tag), page.html:11 (og:site_name), page.html:33-36 (logo), page.html:633 (footer copyright))
malicious redirect
All MP3 audio file play links route through 'fine.sunproxy.net', a third-party proxy/relay domain not affiliated with MP3.cc. Audio streams are proxied through this intermediary, which could be used for traffic interception, logging, or serving malicious files. The data-url values contain long base64-encoded path segments routed through fine.sunproxy.net. (location: page.html:228 (data-url attributes on playlist-play links), e.g. https://fine.sunproxy.net/file/YVlGMWFT...)
hidden content
12 suspicious base64 blobs were flagged in Tier 2 pre-scan. These correspond to the obfuscated file paths in the 'data-url' attributes of playlist play links, all routed through fine.sunproxy.net. While they appear to be encoded file paths rather than injected payloads, the encoding obscures the actual destination file paths from casual inspection. (location: page.html:228,247,266,285,304,323,342,361,380,399,418,437 (data-url base64 encoded paths in playlist-play anchors))
social engineering
The site presents a fully functional music streaming and download interface (free MP3 downloads) that lures users into interacting with a shadow domain. The deceptive link count of 1 noted in Tier 2 likely corresponds to the sidebar 'Online Radio' link pointing to 'https://looz.net/' — an off-brand external site embedded among legitimate-looking genre navigation links, potentially used to drive traffic to an unrelated third-party site. (location: page.html:204 (looz.net link in sidebar navigation))
curl https://api.brin.sh/domain/feel-it-michele-morrone.hydr0.orgCommon questions teams ask before deciding whether to use this domain in agent workflows.
feel-it-michele-morrone.hydr0.org currently scores 41/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.