context safety score
A score of 35/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 uses Function constructor for runtime code generation
brand impersonation
The site operates as 'drakorid.co' presenting itself as 'Drakor.id' — a well-known Indonesian Korean drama streaming platform. The domain 'drakorid.co' is a typosquat/impersonation of the legitimate 'drakor.id' domain, using a '.co' TLD to mimic the authentic brand, including copying its logo, name, and UI structure. (location: page.html:23, page.html:38, metadata.json (domain: drakorid.co))
credential harvesting
The site presents login and registration flows (/login, /register) under the impersonated 'Drakor.id' brand on a lookalike domain. Users believing they are on the legitimate drakor.id site may submit real credentials to this copycat site, enabling credential harvesting. (location: page.html:282-300, page.html:347-352)
social engineering
The site mimics a trusted streaming platform (Drakor.id) with full UI, branding, section names, and navigation — including a sidebar showing 'Belum Login' (Not Logged In) state to prompt users to authenticate. This creates false trust to manipulate users into logging in and registering. (location: page.html:254-267, page.html:281-300)
hidden content
A hidden VIP badge image is embedded in the profile box with 'display: none' inline style. This element is conditionally revealed and may be used to manipulate UI state or deceive users about account privilege status. (location: page.html:260)
hidden content
Intercom live chat is initialized with 'hide_default_launcher: true', concealing the chat widget from users while it remains active and capable of collecting interaction data or delivering unsolicited messages. (location: page.html:418)
prompt injection
An API token is hardcoded and exposed in client-side JavaScript: 'token_now = "5cfxk7bVWYhzhQEhyrS_ZLkRP3gMZH0..."'. This token is sent to server-side PHP endpoints via POST. If an AI agent processes or executes this page's scripts, it may inadvertently transmit this token or be misled by dynamically injected AJAX content from these endpoints. (location: page.html:432)
malicious redirect
All content sections (slider, ongoing, trending, favorites, categories) are loaded dynamically via AJAX from PHP endpoints on the same domain. The responses are directly injected into the DOM via '.html(response)' without sanitization, enabling potential server-side injection of redirect or malicious payload content into the page at runtime. (location: page.html:439, page.html:468-469)
curl https://api.brin.sh/domain/drakorid.coCommon questions teams ask before deciding whether to use this domain in agent workflows.
drakorid.co currently scores 35/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.