context safety score
A score of 62/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 site operates on a subdomain 'blue-billie-eilish.muzce.com' engineered to rank for searches related to artist Billie Eilish. It uses the artist's name in the domain, page title, metadata, and structured data (schema.org MusicRecording) to impersonate an official or authorized music distribution platform. The site offers free MP3 downloads of copyrighted tracks attributed to Billie Eilish without authorization, exploiting the artist's brand identity. (location: domain: blue-billie-eilish.muzce.com; page title; meta keywords; schema.org JSON-LD structured data)
social engineering
The page actively encourages users to download copyrighted MP3 files ('бесплатно и без регистрации' — free and without registration) using the artist's name and music catalog to lure users into downloading files from an untrusted third-party server (muzce.com/file/...). The obfuscated/tokenized file URLs prevent inspection of actual file contents prior to download, and files are served from a different domain than the site itself. (location: page.html lines 183-184; all data-track attributes pointing to https://muzce.com/file/)
hidden content
The Yandex Metrika noscript tracking pixel is positioned off-screen using 'position:absolute; left:-9999px;' — a standard technique for hiding tracking elements from visual display. While common for analytics, this is a known method for invisible user tracking without consent disclosure. (location: page.html line 28: <img src='https://mc.yandex.ru/watch/103572704' style='position:absolute; left:-9999px;'>)
hidden content
A LiveInternet/Yadro counter script is rendered inline in page-text.txt at the footer and dynamically sets the src of an element with id 'licntC87E', sending referrer, screen dimensions, color depth, URL, and page title to counter.yadro.ru — a Russian analytics/tracking service. This data exfiltration to a third-party tracking domain is embedded without visible disclosure to users. (location: page-text.txt lines 913-917)
curl https://api.brin.sh/domain/blue-billie-eilish.muzce.comCommon questions teams ask before deciding whether to use this domain in agent workflows.
blue-billie-eilish.muzce.com currently scores 62/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.