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
malicious redirect
script/meta redirect patterns detected in page source
cloaking
Page conditionally redirects based on referrer or user-agent
cloaking
Page loads content in transparent or zero-size iframe overlay
js obfuscation
JavaScript uses Function constructor for runtime code generation
social engineering
Online gambling site (F999.game) targeting Bangladeshi users with false legitimacy framing via PAGCOR (Philippine gaming regulator) license claims, combined with aggressive referral incentives ('invite friends to win ৳999'). Site operates in Bangladesh where online gambling is illegal, using a Philippine regulatory reference to lend false credibility and pressure users into KYC data submission within 72 hours under threat of account freeze. (location: page.html: meta tags, KYC config block containing legalUserEkycTips and legalUserFreezeTips with pagcor.ph links)
credential harvesting
Site implements full account registration/login with KYC document collection (face scan, government ID), withdrawal passwords, bank account details, Google OAuth integration, and device fingerprinting via FingerprintJS (publicKey: cIMrDd2qJKZFByajXD7O). Password-protected APK downloads use MD5 hashes as 'passwordHost' tokens. Extensive identity data is collected from users in a jurisdiction where the service is illegal. (location: page.html: fingerprintJS config, kyc fields (legalUserEkycDoc, legalUserEkycFace), deviceIdSecurityVerify block, withdrawPasswd fields)
malicious redirect
Page contains a banner/popup element with jumpUrl redirecting to https://www.999bd2.com/?id=758873355 — an affiliate tracking link to a separate gambling domain. The redirect is embedded in minified JS config data with jumpAction:1, obscuring the redirect from casual inspection. Additionally, window.location.href redirect to /pages/browser/index.html encodes the originating URL for tracking. (location: page.html: JS config object containing jumpUrl:"https://www.999bd2.com/?id=758873355" with jumpAction:1)
obfuscated code
Multiple layers of Base64 obfuscation used to conceal real domain names and CDN endpoints. The string array c=[] contains Base64-encoded values: 'c2NyaXB0' (script), 'd2hhbnd6LTE3MDYtcHBw' (whanwz-1706-ppp), 'b3NzLWFjY2VsZXJhdGUuYWxpeXVuY3MuY29t' (oss-accelerate.aliyuncs.com). URLs are constructed at runtime via window.atob() to prevent static analysis. GTM tag ID is also Base64-encoded inline. The technique is consistent with evasion of security scanners. (location: page.html: inline script blocks using window.atob() and base64-encoded URL fragments like 'aHR0cHMlM0ElMkYlMkZ3aGFud3otMTcwNi1wcHAub3NzLWFjY2VsZXJhdGUuYWxpeXVuY3MuY29t')
malicious redirect
Preconnect and dns-prefetch links point to 'https://pubsgppp.c1oudfront.com/' — a domain using '1' (digit one) in place of 'l' in 'cloudfront', typosquatting Amazon CloudFront. This domain serves as a CDN/asset proxy, masking the true origin of resources loaded on the page and potentially intercepting requests. (location: page.html: <link rel=preconnect href=https://pubsgppp.c1oudfront.com/> and <link rel=dns-prefetch href=https://pubsgppp.c1oudfront.com/>)
social engineering
Site promotes sideloaded Android APK downloads (bypassing Google Play Store security review) hosted on AWS S3: bync0r-1706-ppp.s3-accelerate.amazonaws.com. Three APK variants are offered (sn, nn_v3, nn64_v3 for version 6.3.5). The iOS app is disguised as 'Virelia Match3 Game' (id6751177232) on the Apple App Store — a puzzle game facade concealing a gambling application, with a backup iOS download at ios.f999app1.com. (location: page.html: downloadList config containing APK URLs on S3 and Apple App Store link for 'virelia-match3-game')
hidden content
An 'antiban' overlay mechanism is embedded with z-index:99999 that can cover the entire viewport (position:fixed, full coverage). This element appears designed to display alternative content or forward users to a different URL when anti-gambling enforcement tools or bots are detected, effectively serving different content to security scanners vs. real users. (location: page.html: <style>.antiban{position:fixed;left:0;right:0;top:0;bottom:0;background-color:#fff;z-index:99999} with .antiban-forward button)
obfuscated code
Google Tag Manager (GTM-5BMJWJV5) and Google Analytics (G-1CEWQDVW69) tags are injected with the 'script' tag name Base64-encoded as 'c2NyaXB0' within HTML-entity-encoded inline script content, obfuscating the tracking instrumentation from static analysis tools. The GTM container could be used to inject additional payloads dynamically without modifying the page HTML. (location: page.html: HTML-entity-encoded script block containing GTM-5BMJWJV5 with c2NyaXB0 obfuscation)
curl https://api.brin.sh/domain/f999.comCommon questions teams ask before deciding whether to use this domain in agent workflows.
f999.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.