context safety score
A score of 44/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 piracy/copyright-infringing MP3 download service, distributing tracks from major artists (Alphaville, BTS, BLACKPINK, One Direction, Beyonce, Imagine Dragons, etc.) without authorization. The page explicitly offers free downloads without registration ('бесплатно и без регистрации'), which is used as a lure to attract users to a potentially untrustworthy domain. (location: page.html:183, page-text.txt:139)
malicious redirect
External script loaded from a third-party subdomain 'muzce.39o.ru' (not the main muzce.com domain) with query parameters including a user identifier ('u=eZWL') and platform parameters. This suspicious script host differs from the main domain and could serve as a vector for malicious redirect or tracking injection. (location: page.html:1514)
hidden content
LiveInternet tracking pixel initially set to a 1x1 transparent GIF data URI (data:image/gif;base64,R0lGODlhAQABAIAAAAAAAP///yH5BAEAAAEALAAAAAABAAEAAAIBTAA7) with its src subsequently replaced via JavaScript to ping counter.yadro.ru with full referrer, URL, screen dimensions, and page title. This is a covert user-tracking mechanism invisible to users. (location: page.html:1500-1506)
hidden content
Yandex Metrika tracking with webvisor (session recording) and clickmap enabled, collecting detailed behavioral analytics including mouse movements and clicks without prominent user disclosure. (location: page.html:21-27)
social engineering
The domain name 'forever-young-2-demo.muzce.com' is constructed to look like a legitimate music search result URL for the query 'Forever Young (2.Demo)', which may deceive users and automated agents into treating it as a benign search results page rather than a piracy distribution site. (location: metadata.json, page.html:5)
curl https://api.brin.sh/domain/forever-young-2-demo.muzce.comCommon questions teams ask before deciding whether to use this domain in agent workflows.
forever-young-2-demo.muzce.com currently scores 44/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.