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
phishing
Page impersonates Google sign-in with credential form
malicious redirect
Obfuscated script dynamically constructs and injects a script tag loading from 'outoctillerytor.com' — a domain with no legitimate reputation, using string concatenation to evade static URL detection. Pattern: (function(d,z,s){s.src='https://'+d+'/400/'+z;...})('outoctillerytor.com',7799777,...) (location: page.html:2143)
malicious redirect
Second obfuscated script dynamically constructs and injects a script tag loading from 'ptichoolsougn.net' — another suspicious domain using the same evasion pattern as above, appending to document body at runtime. (location: page.html:2144)
obfuscated code
Two inline scripts use an obfuscated self-invoking function pattern to split domain strings and dynamically append third-party script elements to the DOM, bypassing static content security analysis. Both use identical structure to conceal the loaded URL from scanners. (location: page.html:2143-2144)
hidden content
A commented-out ad script referencing 'cdn.pubfuture-ad.com' and a pubfuturetag push snippet are present in HTML comments. The pubfuturetag push code is also embedded in a comment, indicating ad injection infrastructure that can be trivially re-enabled. (location: page-hidden.txt:3,7)
social engineering
The site's login modal displays the title 'VipToon' (not 'ManhwaZ') in the Sign In and Sign Up headings, presenting a mismatched brand identity that could confuse users about which site they are authenticating with. (location: page.html:1952,2013)
malicious redirect
Navigation header contains an outbound link to 'manhwahub.net' labeled 'Adult' with target='_blank', redirecting users to an external third-party adult content site (described as 'Hentai Manhwa') without adequate disclosure. (location: page.html:210)
curl https://api.brin.sh/domain/manhwaz.comCommon questions teams ask before deciding whether to use this domain in agent workflows.
manhwaz.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.