context safety score
A score of 40/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
malicious redirect
Obfuscated third-party script loaded from stylish-airport.com with a heavily encoded path, injected dynamically via document.createElement. The script binds to all anchor clicks via class 'click_hilltop_click' (added to every <a> tag on the page by inline JS), enabling click-hijacking/redirect on any user interaction. The domain 'stylish-airport.com' is unrelated to manga content and is a known pattern for ad-fraud/malicious redirect networks. (location: page.html:86-94, page.html:4182-4186)
malicious redirect
Obfuscated third-party ad script dynamically injected from shortterm-result.com with a heavily encoded URL path. Domain name is deceptive (mimics legitimate short-term/result services) and the encoded path conceals the true payload. Loaded asynchronously with no-referrer-when-downgrade policy to reduce traceability. (location: page.html:531-541)
obfuscated code
Two separate inline script blocks use the same self-invoking function pattern to dynamically inject external scripts with heavily encoded/obfuscated src paths (stylish-airport.com and shortterm-result.com). The paths use forward-slash escaping (\/) to evade static analysis and string matching. Both scripts are injected by inserting before the last script element rather than using standard script tags, a common evasion technique. (location: page.html:86-94 (stylish-airport.com), page.html:531-541 (shortterm-result.com))
prompt injection
The page injects the class 'click_hilltop_click' onto every anchor element on the page via JavaScript loop, then the stylish-airport.com script binds to that class. An AI agent crawling or interacting with this page would have all its link-click actions intercepted and potentially redirected through the third-party script's logic before navigation occurs. (location: page.html:4182-4187, page.html:86-94)
hidden content
Multiple ad network script blocks are commented out in the HTML (realsrv.com/ad-provider.js, quaternnerka.com, thulrlidos.com, hd.yappedperlid.com, duamilsyr.com) but one realsrv.com ad script remains active (line 732). The commented-out scripts reference domains associated with aggressive/malicious ad networks. Their presence in commented form suggests prior use or staged deployment. (location: page.html:67-71, page.html:83, page.html:496)
social engineering
The site prominently offers free adult/18+ manga content with login/register prompts, creating a credential-harvesting context. Users are incentivized to register accounts on a domain using a .club TLD with adult content, which is a common pattern for harvesting email addresses and passwords that users reuse from other services. (location: page.html:122-124, page.html:466-471)
malicious redirect
Client-side JavaScript rewrites all links matching 'https://mangaclan.net/dis.html?url=' by extracting the 'url' parameter and replacing the href. This is a URL-unwrapping redirect pattern that may be used to route users through tracking or malicious intermediary pages before reaching the final destination. (location: page.html:4190-4198)
curl https://api.brin.sh/domain/manga18.clubCommon questions teams ask before deciding whether to use this domain in agent workflows.
manga18.club currently scores 40/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.