context safety score
A score of 43/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
cloaking
Page loads content in transparent or zero-size iframe overlay
js obfuscation
JavaScript contains heavy hex-escape encoding typical of obfuscation
obfuscated code
A large heavily obfuscated JavaScript block using the _0x4a95 array-rotation pattern is present at the bottom of the page, loaded from the page itself. The obfuscation uses string-array rotation with hex-encoded identifiers, a common technique to hide malicious payloads such as ad-fraud scripts, cryptominers, or redirect logic from static analysis. The function name _0x4a95 and its companion decoder are classic fingerprints of tools like javascript-obfuscator used for malicious purposes. (location: page.html:1456-1458, page-text.txt:1354-1356)
malicious redirect
External ad iframes are loaded from cdn.sinparty.com (an adult affiliate network) directly inside the page body. Three separate iframes with tracking parameters (linkId, sourceId, tenantId, affS1, affS2) are embedded. Additionally, multiple outbound links use an opaque kaotic.com redirect/hash URL pattern (data-link-hash containing a base64-like token at https://kaotic.com/AOxMDN|...) before forwarding to efukt.com, obscuring the final destination from users and security tools. (location: page.html:852,858,863,866,868,1288,1294,1299,1302,1304,1343,1352,1360)
hidden content
Multiple JavaScript blocks for ad iframes (sinparty.com banners) contain a 'return 1;' statement immediately after the function opening, which dead-codes the iframe-injection logic in those script blocks. The iframes are instead loaded via inline HTML. This dual-path pattern (dead JS + live HTML) is a technique to confuse automated scanners that analyse only JS-driven DOM manipulation while the actual content is delivered via static HTML, partially obscuring ad-network telemetry. (location: page.html:1344-1350, 1353-1359, 1362-1367)
obfuscated code
A third-party JavaScript file is loaded from adsmediabox.com (https://adsmediabox.com/ads.js?z=233&ad_height=300), a domain not affiliated with kaotic.com. This is an external ad-serving script with no subresource integrity (SRI) check, meaning its contents can be changed at any time by the third party to deliver malicious payloads including drive-by downloads, cryptominers, or browser exploits. (location: page.html:1455)
curl https://api.brin.sh/domain/kaotic.comCommon questions teams ask before deciding whether to use this domain in agent workflows.
kaotic.com currently scores 43/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.