context safety score
A score of 61/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 on a subdomain (esdeekid-warmin-up.muzce.com) structured to appear as a dedicated artist/track page, offering free MP3 downloads 'without registration' to lure users into downloading files from obfuscated signed URLs. The download links use long opaque token-based paths that obscure the actual file destination. (location: page.html:187-223, data-track attributes)
hidden content
LiveInternet tracker pixel uses a base64-encoded GIF placeholder (data:image/gif;base64,R0lGODlhAQABAIAAAAAAAP///yH5BAEAAAEALAAAAAABAAEAAAIBTAA7) that is replaced at runtime via JavaScript to send referrer, screen resolution, color depth, page URL, and page title to counter.yadro.ru — a behavioral tracking/exfiltration endpoint invisible to users. (location: page.html:238-245)
hidden content
External script loaded from a third-party domain 'ru.viadata.store' (https://ru.viadata.store/v2/comm_min.js?sid=109170) with unknown ownership. This domain is not affiliated with muzce.com and the script is loaded asynchronously with no integrity check (no SRI hash), allowing arbitrary code execution from an unverified third party. (location: page.html:273)
malicious redirect
Script loaded from 'https://muzce.39o.ru/muzce.yan?u=eZWL&pt1=muzce.com&pt2=510&pt3=php' — a subdomain of 39o.ru, not muzce.com. This is a suspicious cross-domain script load with query parameters suggesting ad/redirect brokering. The domain '39o.ru' is unrelated to muzce.com and could serve malicious redirects or ad injection via the deferred script. (location: page.html:253)
social engineering
Page advertises free MP3 downloads at 320kbps without registration, a common lure used on piracy/malware distribution sites to encourage users to click download links that may deliver malicious payloads instead of or in addition to music files. (location: page.html:183, page-text.txt:139)
curl https://api.brin.sh/domain/esdeekid-warmin-up.muzce.comCommon questions teams ask before deciding whether to use this domain in agent workflows.
esdeekid-warmin-up.muzce.com currently scores 61/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.