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
exfiltration
JavaScript intercepts form submissions to exfiltrate data
brand impersonation
The site uakinogo.online presents itself as the 'official' KinoGo (КиноГо) streaming service, explicitly using the title 'KinoGo.online смотреть фильмы и сериалы онлайн на официальном КиноГо' and branding, while operating on a different domain (uakinogo.online vs kinogo.biz/kinogo.ec). The ad injection element references 'data-cp-host' pointing to kinogo.biz, and the nav bar links to kinogo.ec as 'КиноГо / Топ', indicating this is an unofficial clone impersonating the legitimate KinoGo brand. (location: page.html:5-6, line 70, line 1392)
malicious redirect
A dynamic script loader fetches and executes JavaScript from two suspicious third-party domains — cvt-s1.agl010.pro and cvt-s1.agl008.shop — using an obfuscated fallback chain. These domains are not recognizable CDN or analytics providers; the pattern (short-lived .pro/.shop TLDs, opaque hash-named JS files, silent fetch-and-eval) is characteristic of adware or malvertising redirect chains. Scripts are fetched at runtime and injected directly into the document head without any integrity check. (location: page.html:1751-1754)
obfuscated code
The dynamic script loader uses a self-invoking obfuscated function with minified variable names and a two-URL fallback pattern to silently fetch and eval remote JavaScript (cvt-s1.agl010.pro and cvt-s1.agl008.shop). The fetched content is set as textContent of a script element and appended to document.head, then immediately removed — a classic technique to evade static analysis and inject arbitrary code without leaving persistent DOM traces. (location: page.html:1750-1755)
hidden content
All script tags on the page use a non-standard type attribute 'f94f667192f96a93522e824a-text/javascript' instead of the standard 'text/javascript'. This causes browsers to skip native execution of these scripts, while Cloudflare Rocket Loader (rocket-loader.min.js, data-cf-settings matching the same token) re-executes them selectively. This technique obscures which scripts run and in what order from static analysis tools and security scanners. (location: page.html:1477, 1534-1535, 1575, 1738, 1750)
hidden content
An invisible 1x1 iframe is injected into the document body via inline JavaScript. The iframe is positioned absolutely at top:0/left:0 with visibility:hidden and no border, and a script is written into its document that loads '/cdn-cgi/challenge-platform/scripts/jsd/main.js'. While this is a Cloudflare bot-detection pattern, the technique of using a hidden iframe to load and execute scripts is also a common method for covert content injection and tracking. (location: page.html:1759)
brand impersonation
The ad branding element injects an ad network tag (class '604c7625') with data-cp-host referencing 'kinogo.biz', while the actual page domain is uakinogo.online. This cross-domain ad injection leverages the KinoGo brand identity to serve third-party ads without the legitimate brand owner's evident control, potentially exposing users to malvertising under a trusted brand name. (location: page.html:70)
social engineering
The site presents itself as a free, unlimited, registration-free movie streaming platform ('дивитися фільми онлайн безкоштовно та без будь-яких обмежень', 'без реєстрації та відправки смс') while simultaneously providing a login/registration form that collects username and password. This creates a false sense of no-registration-required safety to lower user guard before prompting credential entry. (location: page.html:1480-1491, page-text.txt:1416-1426)
credential harvesting
The site hosts a login form that submits credentials (login_name, login_password) via POST to the same page (action='') on an unofficial clone domain (uakinogo.online). Users who believe they are logging into the legitimate KinoGo service may instead be submitting credentials to an unaffiliated operator. The login hash 'dle_login_hash' is also exposed in JavaScript on the page. (location: page.html:1483-1489, 1539)
hidden content
The DNS prefetch directives in the page head reference four external domains (cdn77.aj2517.bid, cdn77.srv224.com, v206.cinemap.cc, video.cinemap.cc) that are not visibly referenced elsewhere in the HTML. The .bid TLD domain (cdn77.aj2517.bid) is particularly associated with ad networks and malvertising infrastructure. These prefetches establish early network connections to third-party ad/video CDN hosts before any visible content loads. (location: page.html:59-62)
curl https://api.brin.sh/domain/uakinogo.onlineCommon questions teams ask before deciding whether to use this domain in agent workflows.
uakinogo.online 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.