context safety score
A score of 43/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
cloaking
Page checks user-agent for bot/crawler strings to serve different content
cloaking
Page conditionally redirects based on referrer or user-agent
js obfuscation
JavaScript uses Function constructor for runtime code generation
js obfuscation
Very long base64 or hex string assigned in JavaScript — likely encoded payload
prompt injection
Hidden HTML element contains AI-targeting instructions
brand impersonation
The site operates as 'SteamUnlocked' and explicitly markets itself as 'the official site for downloading free pre-installed PC games,' directly impersonating or trading on the Steam brand identity. Steam is a registered trademark of Valve Corporation; this site distributes pirated/cracked games under a name designed to evoke legitimacy and association with Valve's Steam platform. (location: page.html:15-16, page.html:26 (LD+JSON schema), page-text.txt:28, page-text.txt:308)
social engineering
The footer widget explicitly claims 'SteamUnlocked.org is the only official SteamUnlocked site. Any other domain is not affiliated with us.' This is a classic social engineering trust anchor used by piracy/malware distribution sites to establish false authority, deter users from recognizing the site itself as inauthentic, and discourage visiting legitimate alternatives. The claim of being 'official' for an inherently unofficial piracy operation is deceptive. (location: page.html:543, page-text.txt:308)
social engineering
The site promotes free downloads of paid, copyrighted commercial games (e.g., Assassin's Creed Mirage, ARK: Survival Ascended, Dead Space Remake, Sonic Frontiers) as 'pre-installed' and 'safe.' This lures users to download executable game files from a third-party piracy site, presenting a high risk of malware bundled in game installers/archives. The messaging 'No setup, no hassle — just extract and play' is designed to reduce user friction and security hesitation. (location: page.html:249, page.html:541-543, page-text.txt:28, page-text.txt:306-308)
hidden content
The search plugin configuration data is stored in a hidden div with style='display:none !important;' containing a large base64-encoded data attribute ('data-asldata'). While this is a standard Ajax Search Lite plugin pattern, the base64 blob embeds site configuration that is not visible to users and could theoretically be used to smuggle data or instructions past content scanners. (location: page.html:271 (div.asl_init_data, data-asldata attribute))
hidden content
Multiple elements use 'display:none !important;' and 'visibility:hidden' to suppress content from view, including post-view counters (.single-post .post-views), search settings forms, and internal plugin metadata. While individually these are normal WordPress patterns, they collectively represent non-rendered content surface area that warrants awareness. (location: page.html:173, page.html:270, page.html:273, page.html:277-278)
curl https://api.brin.sh/domain/steamunlocked.orgCommon questions teams ask before deciding whether to use this domain in agent workflows.
steamunlocked.org currently scores 43/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.