context safety score
A score of 39/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
brand impersonation
The site sells top-ups and gift cards for OpenAI services alongside Steam, Discord, YouTube, Xbox, Netflix, Spotify and PS Network, presenting itself as an authorized marketplace for these platforms. No affiliation with OpenAI or any of these brands is disclosed, creating a false impression of authorization and enabling credential/payment harvesting under trusted brand names. (location: page-text.txt line 9; page.html line 116 (services grid listing OpenAI, Steam, Discord, etc.))
credential harvesting
The site collects payment credentials (card/account top-ups) and user login tokens under the guise of a digital goods marketplace, targeting accounts for Steam, OpenAI, YouTube, Netflix, Spotify, PS Network, Xbox, Discord and Telegram. The backend API endpoint is 'https://steam.kupikod.com/backend/api' and user auth tokens are tracked in client-side state (window.__NUXT__ 'token' field). This pattern is consistent with a phishing storefront that harvests payment details and possibly account credentials. (location: page-text.txt line 9; page.html line 117 (__NUXT__ state with token/user fields))
phishing
kupikod.com operates as a Russian-language digital goods reseller selling top-ups for services unavailable in Russia ('Недоступные в РФ'), including OpenAI, PS Network, Xbox, Netflix and Spotify. This targets users in sanctioned regions seeking workarounds, a well-known phishing vector where fake or fraudulent top-up codes are sold and payment data is collected. (location: page-text.txt line 9 ('Недоступные в РФ'); page.html line 104 (meta description))
hidden content
A debug/internal state string 'false - isStageValue456' is rendered as visible page text within the main content area. This appears to be an unintended leak of internal environment flag logic into the rendered DOM, which could indicate template injection, misconfigured server-side rendering, or an attempt to embed machine-readable signals in page text. (location: page-text.txt line 9 ('false - isStageValue456'); page.html line 116)
obfuscated code
An external script is loaded from 'https://kupikod.id/tracker.js' — a different TLD domain (kupikod.id vs the main kupikod.com). The .id TLD is unrelated to the .com brand domain and could represent a shadow tracking domain. Additionally, a script named 'lm-id-gemerator-v1-1.js' (note the misspelling 'gemerator' instead of 'generator') is loaded from 'https://cdn-v2.kupikod.com/scripts/'. Misspelled obfuscated script names are a common tactic to evade automated scanning. (location: page.html lines 52-53)
social engineering
The site employs urgency and reward manipulation tactics common in social engineering: 'Ежедневный бонус — Каждый день испытывай удачу' (Daily bonus — try your luck every day), cashback incentives requiring registration, and gamified loyalty mechanics. These are designed to drive user account registration and repeat payment behavior. (location: page-text.txt line 9 (daily bonus, cashback registration sections))
curl https://api.brin.sh/domain/kupikod.comCommon questions teams ask before deciding whether to use this domain in agent workflows.
kupikod.com currently scores 39/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.