context safety score
A score of 45/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
The page hosted on downloadwella.com (a file-sharing site) contains an injected promotional banner redirecting users to thenkiri.com, claiming 'NKIRI.COM is now THENKIRI.COM'. This cross-site redirect to an unrelated third-party domain (thenkiri.com) is embedded directly in the page HTML and is completely unrelated to the downloadwella.com service, indicating unauthorized content injection or a hijacked/compromised page being used to funnel traffic to another site. (location: page.html:351-356, .moved-banner div, <a href="https://thenkiri.com" class="visit-btn">)
social engineering
The injected 'Website Move Notice' banner uses persuasive social engineering techniques: urgency framing ('Big News!'), authoritative tone ('We've moved'), brand trust transfer ('NKIRI.COM is now THENKIRI.COM'), and a professionally styled animated CTA button to convince visitors to navigate away from downloadwella.com to thenkiri.com. The banner is visually designed to appear legitimate and trustworthy, mimicking an official site migration notice. (location: page.html:278-357, .moved-banner section)
brand impersonation
The injected banner impersonates the brand identity of NKIRI.COM by claiming it has rebranded/moved to THENKIRI.COM. This leverages the established reputation of NKIRI.COM (a known media streaming/download site) to drive users to thenkiri.com. Users familiar with nkiri.com may trust the redirect, not realizing the claim is injected content on an unrelated file-hosting domain. (location: page.html:352, text: 'NKIRI.COM is now THENKIRI.COM')
hidden content
The footer CSS sets 'footer .container1{display:none;}' hiding the footer container from view. Additionally, the hosting infrastructure is flagged as 'Bulletproof' hosting — a category associated with hosting providers that resist takedown requests — which combined with injected third-party content suggests the site may be intentionally used to serve hidden or malicious payloads. (location: page.html:258, CSS: footer .container1{display:none;}, metadata.json hosting.reputation=Bulletproof)
curl https://api.brin.sh/domain/downloadwella.comCommon questions teams ask before deciding whether to use this domain in agent workflows.
downloadwella.com currently scores 45/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.