context safety score
A score of 45/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
js obfuscation
JavaScript uses Function constructor for runtime code generation
brand impersonation
The site operates as 'SteamRIP' and prominently features Steam-branded game titles (Cyberpunk 2077, God of War, Spider-Man, etc.) offering them as 'Free Download', impersonating Valve's Steam platform and multiple game publishers to lend legitimacy to what is a software piracy distribution site. (location: page-text.txt:1, page-text.txt:3 - site logo alt='SteamRIP', game download listings)
social engineering
The site offers AAA commercial games (Baldur's Gate 3, Red Dead Redemption 2, Forza Horizon 5, Hogwarts Legacy, etc.) as free downloads, using well-known titles to lure users into downloading files from an unauthorized source. This social engineering tactic exploits user desire for free software to deliver potentially malicious payloads. (location: page-text.txt:3 - game download listings including 'Free Download' labels on commercial titles)
obfuscated code
Multiple script tags use a non-standard type attribute value '4d149d28529c9651560c53e1-text/javascript' instead of 'text/javascript'. This pattern is used by Cloudflare Rocket Loader to defer script execution, but it also means scripts are not executed by the browser natively and are activated only after Rocket Loader processes them — obscuring the true execution flow from static analysis tools. (location: page.html:46, page.html:49, page.html:85, page.html:90 - script type='4d149d28529c9651560c53e1-text/javascript')
hidden content
A hidden 1x1 pixel iframe is injected dynamically at the bottom of the document body (position absolute, top:0, left:0, border:none, visibility:hidden). It is used to inject and execute a Cloudflare challenge script (jsd/main.js). While consistent with Cloudflare bot protection, this technique is also a known pattern for hidden tracking or payload delivery that bypasses casual inspection. (location: page.html:111 - iframe with height=1, width=1, visibility:hidden used to inject /cdn-cgi/challenge-platform/scripts/jsd/main.js)
curl https://api.brin.sh/domain/steamrip.comCommon questions teams ask before deciding whether to use this domain in agent workflows.
steamrip.com currently scores 45/100 with a suspicious 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.