Is aviator-game.co.uk safe?

suspiciousmedium confidence
47/100

context safety score

A score of 47/100 indicates multiple risk signals were detected. This entity shows patterns commonly associated with malicious intent.

identity
100
behavior
100
content
0
graph
66

7 threat patterns detected

critical

brand impersonation

Site hosted at aviator-game.co.uk (a .co.uk domain) presents itself as the official Aviator game platform for Indian players, using the registered trademark symbol (®) and claiming to be 'The №1 Site for Indian Players'. The canonical URL points to isnocon2025.in/en-in/ and an alternate hreflang points to official.aviator-game-in.co.com, neither of which is the actual Spribe Aviator game. The site impersonates the legitimate Aviator crash game brand (by Spribe) to drive traffic to third-party gambling affiliate links. (location: page.html:10-14, meta title and canonical tags)

high

malicious redirect

All primary 'Play Aviator' and 'Download' call-to-action buttons use a JavaScript onclick handler that reads a 'data-href' attribute and sets window.location.href to redirect users. The destination paths (/go/play, /go/play/) are internal redirect endpoints whose final destination is not disclosed in the HTML. Multiple casino 'Play' buttons redirect to third-party affiliate domains: mostbet-global-pro.com, part-global.com, 1win-global-pro.com. These are opaque redirect chains through unverifiable intermediaries. (location: page.html:122-126, 179-182, 235, 251, 267, 283, 299, 315, 331, 389-395)

high

obfuscated code

A runtime JavaScript function named decodeBase64() is injected into the page. It tests all data-href attribute values against a base64 regex pattern and silently decodes them via atob() before the user navigates. This means the actual redirect destination URLs are not present in the static HTML and are only revealed at runtime after base64 decoding. This is a deliberate obfuscation technique to hide redirect targets from static scanners and URL reputation systems. (location: page.html:420-458)

high

social engineering

The page uses multiple deceptive trust signals to manipulate users into clicking gambling affiliate links: (1) Claims 'only trusted casinos with proven payouts, valid licenses' without providing verifiable license numbers; (2) Uses inflated welcome bonus claims (125% to 700% bonuses, up to ₹150,000) to create urgency and false legitimacy; (3) Displays BeGambleAware and 18+ logos as fake regulatory trust badges that link to '#' (dead links), not to actual regulatory bodies; (4) Claims 'Win x1,000,000 Your Bet' in the H1 headline — an extreme and misleading claim designed to lure vulnerable users. (location: page.html:154, 190, 372-378)

high

malicious redirect

The canonical link tag points to https://www.isnocon2025.in/en-in/ and the hreflang alternate points to https://official.aviator-game-in.co.com/en-in/ — both different domains from the serving domain aviator-game.co.uk. This cross-domain canonical/hreflang mismatch is a known SEO cloaking technique used to hijack search ranking signals while funneling actual traffic through the affiliate doorway site. (location: page.html:10-12)

medium

phishing

The site presents itself as an official or authoritative Aviator game portal for India, using .co.uk TLD (British domain) while targeting Indian players and using Indian Rupee (₹) denominated bonuses. The mismatch between the serving domain (aviator-game.co.uk), the canonical domain (isnocon2025.in), and the alternate domain (aviator-game-in.co.com) suggests a network of doorway pages designed to capture users searching for the legitimate Aviator game and redirect them to unregulated gambling operators. (location: page.html:10-12, metadata.json:1)

medium

social engineering

The 'Read Review' links for most casino listings point back to the homepage ('/') rather than to actual review pages, meaning users clicking to do due diligence are returned to the same promotional page. This is a dark pattern designed to prevent users from accessing genuine information about the casinos while giving the appearance of transparency. (location: page.html:221, 237, 253, 269)

API

curl https://api.brin.sh/domain/aviator-game.co.uk

FAQ: how to interpret this assessment

Common questions teams ask before deciding whether to use this domain in agent workflows.

Is aviator-game.co.uk safe for AI agents to use?

aviator-game.co.uk currently scores 47/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.

How should I interpret the score and verdict?

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.

How does brin compute this domain score?

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.

What do identity, behavior, content, and graph mean for this domain?

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.

Why does brin scan packages, repos, skills, MCP servers, pages, and commits?

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.

Can I rely on a safe verdict as a full security guarantee?

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.

When should I re-check before using an entity?

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.

Last Scanned

March 25, 2026

Verdict Scale

safe80–100
caution50–79
suspicious20–49
dangerous0–19

Trust Graph

Disclaimer

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.

start scoring agent dependencies.

integrate brin in minutes — one GET request is all it takes. query the api, browse the registry, or download the full dataset.