context safety score
A score of 26/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 contains heavy hex-escape encoding typical of obfuscation
js obfuscation
JavaScript uses Function constructor for runtime code generation
brand impersonation
The site operates as kaskusacc.com (80 days old) but presents itself as 'KASKUSTOTO' and 'KASKUSCAIR', impersonating Kaskus, a well-known Indonesian internet forum/brand. The domain name embeds 'kaskus' to deceive users into believing this is an official or affiliated Kaskus property, while it is actually an unlicensed online gambling operation. (location: page.html:<title>, metadata.json:domain, page.html:line 374, footer text)
phishing
The site presents a login form with username and password fields directly in the navbar. The canonical URL redirects to kaskuscair.com, but the site domain is kaskusacc.com — a pattern where users believe they are logging into a familiar branded platform but are submitting credentials to an impostor domain. The 'Lupa Password' (Forgot Password) link is dynamically hijacked via JavaScript to redirect to a Telegram channel (https://t.me/CSKASKUS1) instead of a legitimate password recovery flow. (location: page.html:lines 25-33, 335-349)
credential harvesting
Login form collects username and password. Password is processed through a custom MD5 hashing script (/js/vbulletin_md5.js) before submission. The 'forgot password' link is overridden by JavaScript to route users to a Telegram channel (https://t.me/CSKASKUS1), bypassing any account recovery mechanism and directing victims to an attacker-controlled channel where credentials or personal data can be collected socially. (location: page.html:lines 25-33, 335-349, 3349)
malicious redirect
The page sets two canonical URLs pointing to kaskuscair.com (lines 4 and 21), while the actual serving domain is kaskusacc.com. Navigation links in the footer also direct users to kaskuscair.com and kaskusapp.com. The amphtml link points to kaskusapp.pages.dev. These cross-domain redirects funnel users between multiple attacker-controlled domains, obscuring the true origin and fragmenting user tracking/attribution. (location: page.html:lines 4, 21, 208, 2099-2107, 3337)
obfuscated code
Multiple large blocks of heavily obfuscated JavaScript are present, using hex-encoded variable names (_0x13f34d, _0x48ca53, etc.), string-shuffling self-executing arrays, and encoded string literals. These blocks are attributed to 'TIGER_DEVS' via ASCII-art comments. The obfuscation hides the true behavior of the scripts, which manipulate the DOM, inject banners, display fake withdrawal/deposit notifications, and potentially perform actions not visible in source review. (location: page.html:lines 523-536, 534-535, 1330, 2296)
social engineering
The site displays fake real-time transaction notifications (snackbar-mobile) with randomly generated usernames and randomized withdrawal amounts (generated client-side in obfuscated JS), creating a false impression of high activity and large payouts to pressure visitors into registering and depositing. Fake online user counts (minuseronline: 50000, maxuseronline: 100000) and a fabricated jackpot amount ('4,131,665,972 IDR') are injected dynamically via the desktopIdn configuration object. (location: page.html:lines 1335-1338, 2119-2283)
hidden content
A 1x1 pixel invisible iframe is injected at the bottom of the page via inline script to load Cloudflare challenge scripts. While Cloudflare itself is legitimate, the pattern of injecting hidden iframes is also used for covert tracking or fingerprinting. Additionally, seven separate Facebook Meta Pixel IDs and three TikTok Pixel IDs are loaded, enabling cross-site behavioral tracking of visitors across unrelated platforms without visible disclosure. (location: page.html:lines 44-168, 1349-1407, 3362)
social engineering
The site loads a third-party CSS/JS resource from a GitHub repository belonging to user 'zombief1206' (https://cdn.jsdelivr.net/gh/zombief1206/file-css@main/splide.css and splide.js). Using a personal GitHub CDN for production assets is a supply-chain risk: the repository owner can push malicious code that would be served to all site visitors without any code review or integrity check (no SRI hashes present). (location: page.html:lines 512, 518)
curl https://api.brin.sh/domain/kaskusacc.comCommon questions teams ask before deciding whether to use this domain in agent workflows.
kaskusacc.com currently scores 26/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.