context safety score
A score of 37/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
cloaking
Page conditionally redirects based on referrer or user-agent
js obfuscation
JavaScript uses Function constructor for runtime code generation
obfuscated code
The page contains an inline script that hooks (monkey-patches) the browser's localStorage API — overriding Storage.prototype.setItem, getItem, and removeItem — and mirrors all read/write operations into an in-memory copy. The code includes Chinese-language comments explicitly stating 'hijack localStorage' (劫持到数据setItem/getItem/removeItem) and 'start hijacking localStorage' (开始劫持localStorage). This intercepts all tokens, session data, and auth credentials stored in localStorage by any script on the page, including third-party widgets. (location: page.html:lines 13-109, inline <script> block immediately after <head>)
credential harvesting
The localStorage hook silently captures every key-value pair written to localStorage across the entire page session, including authentication tokens, session identifiers, and user credentials. The intercepted data is queued in a taskQueue and asynchronously replayed to the real localStorage via setInterval(processTaskQueue, 500), meaning an attacker can read all stored values from the localStorageData object before they are committed, enabling silent exfiltration of session and auth data. (location: page.html:lines 39-108, Storage.prototype.setItem/getItem overrides)
obfuscated code
A minified, single-line iTrace/WPK monitoring bundle is injected inline. While telemetry scripts are common on e-commerce platforms, this particular bundle redefines window.__wpk, intercepts window.onerror, and queues all JS errors and API calls into window.__iTraceLogQueue before the real monitoring library loads. The inline bootstrap is heavily minified with no source map reference, making it difficult to audit what data is collected and where it is sent. (location: page.html:lines 910-911 (itrace inline bootstrap), also page-text.txt:lines 650-651)
curl https://api.brin.sh/domain/daraz.lkCommon questions teams ask before deciding whether to use this domain in agent workflows.
daraz.lk currently scores 37/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.