context safety score
A score of 37/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
malicious redirect
Two external scripts loaded from third-party ad/tracking domains 'curiarawolfkin.com' and 'warkheels.com' with obfuscated path identifiers. These domains are not CDNs or known legitimate ad networks; curiarawolfkin.com in particular matches patterns associated with aggressive ad injection and malvertising redirect chains. Scripts are loaded async with data-cfasync='false' to bypass Cloudflare bot protection. (location: page.html:1322-1323)
malicious redirect
All audio file streaming URLs route through 'fine.sunproxy.net', a third-party proxy service. Users clicking play have their audio requests proxied through this external domain, which could log user behavior, inject content, or redirect streams. The proxy uses base64-encoded opaque path tokens concealing the actual resource routing. (location: page.html:61,84,107 (all data-url attributes))
social engineering
Site offers free MP3 downloads of copyrighted commercial music (Adele, Elton John, Dua Lipa, Stray Kids, etc.) without authorization. This is a classic lure to attract users who then become exposed to the malvertising scripts and ad-injection infrastructure embedded in the page. The footer claims licensing agreements but the scope and legitimacy are unverifiable. (location: page.html:58, page-text.txt:36)
hidden content
The 'Сейчас слушают' (Currently listening) sidebar block contains a large block of seemingly auto-generated or injected search tag strings including garbled text ('йгшйыеуз', 'xn--c1aegfb5d6aza') and unusual keyword combinations. This tag soup can serve SEO poisoning purposes and may contain encoded or obfuscated strings not immediately visible to users. (location: page.html:1225, page-text.txt:1198)
obfuscated code
Audio streaming URLs use long base64-encoded opaque tokens within the sunproxy.net path (e.g., 'T1ZXdFhRdW5YOVR0bGE3TVFEbHlqZkh4aEllS3BIM2FGbTJFUzg4ak5ZN2FQbEd4dTc3bjMxSndpQlR5WWc2...'). This obfuscation hides the actual destination of audio requests, preventing inspection of where data is sent and what tracking may occur. (location: page.html:61 (all data-url attributes throughout playlist))
brand impersonation
The site uses IDN (Internationalized Domain Name) punycode subdomains to represent artist names (e.g., xn--niletto-----6ijab5aj7a2den2ajisd7b9f7i0j.skysound7.com, xn----7sbbdfc5a1a0ag7c2f.skysound7.com) to impersonate legitimate artist pages. These synthetic artist subdomains create an appearance of official artist-affiliated pages while being entirely controlled by this site. (location: page.html:134,146,226,238,295,307 (multiple IDN subdomain links))
curl https://api.brin.sh/domain/skysound7.comCommon questions teams ask before deciding whether to use this domain in agent workflows.
skysound7.com currently scores 37/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.