Is coki88pas.com safe?

suspiciouslow confidence
36/100

context safety score

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

identity
60
behavior
100
content
0
graph
68

9 threat patterns detected

medium

encoded payload

suspicious base64-like blobs detected in page content

critical

obfuscated code

Heavily obfuscated JavaScript in the page <head> uses hex-encoded array lookups (_0x53d140, _0x4be3, _0x4435), string reversal, and array rotation to conceal its logic. Decoded, it constructs a URL from a reversed string ('piv.sitamoto.51emarfi' reversed = 'iframse15.otamatis.vip'), fetches a remote script at runtime, and injects it into the document <head> via createElement('script'). This is a classic loader/dropper pattern used to deliver malicious payloads while evading static analysis. (location: page.html:57-63, var domainsystem='piv.sitamoto.51emarfi')

critical

malicious redirect

The obfuscated script constructs a fetch URL by reversing the string 'piv.sitamoto.51emarfi' to produce 'iframse15.otamatis.vip' (or similar), appending the 'sga' path segment and a timestamp cache-buster. The fetched payload is then executed by injecting a <script> element into the document head. This constitutes a drive-by remote code execution / redirection mechanism that can silently redirect users or execute arbitrary code from an attacker-controlled domain. (location: page.html:58-62, pathsystem construction and fetch() call)

high

credential harvesting

The page presents a fully functional username/password login form (inputs with data-name='username' and data-name='password') on the landing page of a 119-day-old domain. The login button POSTs to 'https://coki88pas.com/' while the canonical URL and og:url point to the different domain 'coki88best.com'. Credentials submitted here may be harvested by the operator or the injected remote script rather than authenticating to a legitimate service. (location: page.html:124-135, login form with onclick=login(this,'https://coki88pas.com/'))

high

brand impersonation

The site (coki88pas.com) presents itself as 'COKI88' with a canonical link and og:url pointing to a different domain 'coki88best.com', and advertises an alternative link 'https://coki88prize.com/'. The domain is only 119 days old and operates multiple near-identical mirror domains (coki88pas.com, coki88best.com, coki88prize.com, gcr-coki88.pro). This multi-domain impersonation cluster is consistent with an illegal online gambling operation using brand cloning to evade takedowns and blocklists. (location: page.html:22-24 (canonical/og:url), page-text.txt:209 (alternative link announcement))

high

malicious redirect

The page canonical tag points to 'https://coki88best.com/' while the page is served from 'https://coki88pas.com/', and an AMP alternate is declared at 'https://mode-amp-coki88.com/amp/index.html'. Users and crawlers may be silently redirected between these domains. The floating social menu also links to 'https://gcr-coki88.pro//' (double trailing slash, suspicious external domain) labeled 'RTP GACOR', which may redirect to a different gambling or phishing site. (location: page.html:22-23 (canonical/amphtml), page.html:754 (gcr-coki88.pro link))

medium

hidden content

Multiple 1x1 pixel invisible Facebook tracking pixels (display:none) are embedded 9 times with distinct Pixel IDs (1146499510198643, 494246227049077, 1039972278236051, 1026084046353307, 3930887217161786, 1128914089254210, 1800855350776974, 1234017305273848, 877214234999627, 1869154243674420). This mass pixel deployment enables cross-site behavioral tracking of all visitors across multiple Facebook ad accounts without user disclosure, and is consistent with large-scale user profiling for targeted fraud campaigns. (location: page.html:790-985, 9 separate Meta Pixel Code blocks with style='display:none' noscript images)

medium

social engineering

The page displays an animated jackpot counter inflating from IDR 1,001,573,867,734 to IDR 1,007,621,262,934 (over ~1 trillion IDR), fabricated prize tournaments with luxury physical goods (car, motorcycles, iPhone 17 Pro Max), and urgency-driven UI elements ('KLIK INI!', 'HOT GAMES', 'RTP GACOR'). These techniques are designed to manipulate visitors into registering and depositing funds on an unregulated gambling platform. (location: page.html:306, page.html:726, page.html:1129-1131 (SGACounter.countUp with fabricated jackpot range))

medium

phishing

The domain coki88pas.com is 119 days old, has no brand recognition, presents a gambling platform with credential collection, operates mirror domains, and deploys a remote script loader. The combination of a newly registered domain, username/password harvesting form, and injected remote payload is consistent with a phishing infrastructure that may be used to steal credentials from users of legitimate gambling or financial platforms. (location: metadata.json (domain_age_days:119), page.html:124-135 (login form))

API

curl https://api.brin.sh/domain/coki88pas.com

FAQ: how to interpret this assessment

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

Is coki88pas.com safe for AI agents to use?

coki88pas.com currently scores 36/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.

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 5, 2026

Verdict Scale

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

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.