context safety score
A score of 46/100 indicates multiple risk signals were detected. This entity shows patterns commonly associated with malicious intent.
js obfuscation
JavaScript contains heavy hex-escape encoding typical of obfuscation
hidden content
JavaScript at end of page attempts to manipulate a DOM element with obfuscated ID 'wede2f34gt65651sdf5664asdad' (document.getElementById('wede2f34gt65651sdf5664asdad').style.width = '100%'; height = '100%') but no such element exists in the visible HTML. This pattern is consistent with a hidden off-screen element being resized to cover the full viewport, potentially for clickjacking or ad fraud. (location: page.html:963-966)
obfuscated code
Commented-out JavaScript block uses hex-encoded strings (\x3c, \x2f, \x3e, etc.) to construct iframe markup pointing to pokoran.com, obfuscating the actual content being injected. This is a common technique to evade static content filters while still rendering ad iframes with device-specific targeting. (location: page.html:159-173 and 194-208)
malicious redirect
Multiple external ad scripts loaded from third-party domains (pokoran.com, fam-ad.com, img.ad-nex.com, smanavi.net, javym.net, erry.one, sugirl.info) without subresource integrity checks. These scripts have full DOM access and can redirect users or inject content. The 'erry.one' and 'javym.net' domains are particularly low-reputation short domains loading executable JavaScript. (location: page.html:157, 191, 226, 730, 840, 864, 888, 918)
hidden content
Dynamic article injection via externally-loaded JavaScript arrays (javymArray, erryArray, sugirlArray) from //javym.net/video.js, //erry.one/video_2.js, and //sugirl.info/link/video.js. These scripts populate article links and hrefs entirely from external data, allowing arbitrary URL injection into page content with no sanitization visible in the page source. (location: page.html:840-911)
social engineering
Site promotes content with titles depicting non-consensual sexual scenarios tagged with 'レイプ' (rape), '盗撮' (voyeurism/hidden camera), '痴漢' (groping), and '近親相姦' (incest), including content tagged 'ロリ' (loli) combined with '女子校生' (schoolgirl) and 'レイプ'. This constitutes potentially illegal content promotion that may be used to lure and socially manipulate users. (location: page.html:658-666, category tags throughout)
curl https://api.brin.sh/domain/nukistream.comCommon questions teams ask before deciding whether to use this domain in agent workflows.
nukistream.com currently scores 46/100 with a suspicious verdict and medium 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.