context safety score
A score of 40/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
All casino listing 'Play Now' and image links use href='#' as the visible href but carry a base64-encoded redirect URL in the data-trrrfrwo attribute (e.g., /out/aHR0cHM6Ly90cmFmLWh1Yi5jb20vY2I0Z2w5ay5waHA_a2V5PXhrdXN3dmFqcmFoamUzeXIxbzBp). Decoded, this resolves to https://traf-hub.com/cb4gl9k.php?key=xkuswvajrahje3yr1o0i — a third-party traffic broker/redirect intermediary. All eight casino entries and the sticky CTA button funnel clicks through this single obfuscated affiliate redirect hub, masking the true destination from users and security tools. (location: page.html lines 138, 163, 182, 207, 226, 251, 270, 295, 314, 339, 358, 383, 402, 427, 446, 471, 594, 701, 811)
obfuscated code
Redirect URLs are base64-encoded and stored in a custom data attribute (data-trrrfrwo) rather than the standard href. The href is set to '#' to suppress visibility. A plugin (wp-tt-second-offer-links/script.js) is loaded specifically to decode and execute these redirects at runtime, deliberately obfuscating the true destination from static analysis, browser previews, and AI agents. (location: page.html lines 138, 163, 820 (wp-tt-second-offer-links/script.js))
social engineering
The site employs multiple high-pressure and trust-fabrication tactics: inflated scores (9.3–9.8/10 for all 8 casinos), fake 'likes' counts (90–115) manipulated via AJAX to admin-ajax.php, exaggerated bonus claims ('200$ No Deposit Bonus', '120 Free Spins', '£1 Free with 10x Multiplier'), and repeated urgency language ('Play For Real Money Now'). These patterns are designed to psychologically manipulate users into clicking affiliate redirect links. (location: page.html lines 145-157, 192-203, 277-290, 594-596, 699-703; page-text.txt lines 710-714)
hidden content
Multiple elements are hidden from users via style='display:none;' including share tracking spans (e.g., class='js-share' with data-link attributes) used to silently track and share page interaction data. Additionally, the data-trrrfrwo redirect attribute is invisible to users since href='#' is displayed while the real destination is only activated by JavaScript. (location: page.html lines 116, 601, 708, 788)
social engineering
Page-text.txt contains malformed shortcode artifacts (')' float="r"]' and ')' float="l"]') appearing as visible text on lines 455 and 511, indicating poorly sanitized content likely copied from another CMS. While not directly harmful, it suggests low-quality, potentially scraped or auto-generated content used to lend false legitimacy to the gambling affiliate site. (location: page-text.txt lines 455, 511)
curl https://api.brin.sh/domain/realmoneyslots-mobile.comCommon questions teams ask before deciding whether to use this domain in agent workflows.
realmoneyslots-mobile.com currently scores 40/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.