context safety score
A score of 46/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
social engineering
Site operates as a music streaming/download portal offering copyrighted ZZ Top tracks ('бесплатно и без регистрации' — free and without registration), enticing users to download MP3 files. This is a common lure used to drive traffic to ad-heavy or potentially malicious download pages. (location: page.html:183, page-text.txt:139)
hidden content
LiveInternet tracking pixel is loaded via a base64-encoded blank GIF (data:image/gif;base64,R0lGODlhAQABAIAAAAAAAP///yH5BAEAAAEALAAAAAABAAEAAAIBTAA7) and then dynamically replaced with a remote tracking URL via inline JavaScript. This invisibly exfiltrates the page URL, referrer, screen dimensions, and page title to counter.yadro.ru without user awareness. (location: page.html:342-349)
hidden content
External script loaded from a third-party domain 'ru.viadata.store' (https://ru.viadata.store/v2/comm_min.js?sid=109170) with async attribute. This domain is unrelated to the site's primary domain (muzce.com) and the script purpose is opaque — consistent with ad injection, data harvesting, or browser fingerprinting scripts embedded invisibly on the page. (location: page.html:377)
hidden content
Yandex Metrika tracking with webvisor:true and clickmap:true enabled, recording full user interaction including mouse movements and clicks, sent to mc.yandex.ru. Combined with the yadro.ru pixel, multiple overlapping trackers silently collect behavioral data. (location: page.html:22-27)
brand impersonation
The subdomain esther-be.muzce.com is structured to appear as a dedicated artist page, mimicking a legitimate music distribution site. The site uses Warner Bros. Records track metadata and ZZ Top branding without authorization, creating a false impression of official content. (location: page.html:5, page.html:319-324)
curl https://api.brin.sh/domain/esther-be.muzce.comCommon questions teams ask before deciding whether to use this domain in agent workflows.
esther-be.muzce.com currently scores 46/100 with a suspicious 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.