context safety score
A score of 69/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
social engineering
Site operates as a music streaming/download portal offering free MP3 downloads ('бесплатно и без регистрации' — free and without registration), which is a common lure used to attract users to piracy-adjacent or potentially ad-fraud sites. The subdomain-per-search-query pattern (alex-terrible-billy-69.muzce.com) is characteristic of SEO spam infrastructure designed to capture search traffic. (location: page.html:183, metadata.json:domain)
hidden content
LiveInternet tracking pixel is loaded via a base64-encoded 1x1 GIF placeholder (data:image/gif;base64,R0lGODlhAQABAIAAAAAAAP///yH5BAEAAAEALAAAAAABAAEAAAIBTAA7) and then replaced by JavaScript with a tracking beacon URL that exfiltrates referrer, screen dimensions, color depth, page URL, and page title to counter.yadro.ru. While this is a known analytics pattern, the data collection is not disclosed to users and includes sensitive browsing context. (location: page.html:291-297)
hidden content
Nine suspicious base64 blobs flagged by Tier 2 scan correspond to long URL-safe base64-encoded strings used as data-track attributes for MP3 file URLs (e.g., data-track='https://muzce.com/file/gJt-w2B04fB...'). These are obfuscated file delivery tokens, not plain URLs, making it difficult to inspect the actual served file paths. While functionally used for audio delivery, opaque tokenized URLs prevent verification of file content or destination. (location: page.html:187,200,213,226,239,252,265)
social engineering
Third-party script loaded from ru.viadata.store (https://ru.viadata.store/v2/comm_min.js?sid=109170) is an unknown external domain with a .store TLD, not affiliated with the main muzce.com domain. This script is loaded asynchronously and its purpose is undisclosed. The domain 'viadata.store' has no clear public identity and could serve ads, track users, or inject additional content. (location: page.html:325)
curl https://api.brin.sh/domain/alex-terrible-billy-69.muzce.comCommon questions teams ask before deciding whether to use this domain in agent workflows.
alex-terrible-billy-69.muzce.com currently scores 69/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.