context safety score
A score of 42/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
js obfuscation
Obfuscated document.write with encoded content
obfuscated code
Two base64-encoded script payloads are injected via document.write(atob(...)) at page bottom. First decodes to a Matomo/Piwik analytics tracker pointing to //user.mangafreak.me/freakyand loading freaky.js — sets cookie domain to *.ww1.mangafreak.me and tracks all page views/link clicks. Second decodes to a third-party script loaded from //bushsurprising.com/ff/20/65/ff20651b55bc5878e9f82126c1547a2b.js — 'bushsurprising.com' is an unrelated, suspicious domain with no apparent connection to the site, commonly associated with ad-fraud or malware delivery networks. (location: page.html:2100-2101, page-text.txt:2047-2048)
malicious redirect
The page is served on mangafreak.me but all canonical URLs, og:url, twitter:url, and resource references point to ww2.mangafreak.me. The canonical tag redirects crawlers and agents to a different subdomain (ww2.mangafreak.me) than the URL being scanned (mangafreak.me). This subdomain mismatch can be used to silently shift users/bots to a different host for tracking or serving different content. (location: page.html:12, 15, 18)
hidden content
Social sharing links in the footer (Facebook, Twitter, Tumblr, Pinterest, Reddit, Instagram) all point to href='/' rather than actual social media profiles. These are non-functional placeholder links that misrepresent site legitimacy and social presence, a common pattern on piracy/content-scraping sites to create a false appearance of an established brand. (location: page.html:2082-2087)
obfuscated code
Third-party script loaded from the suspicious domain //bushsurprising.com — this domain is unrelated to manga content and is known in threat intelligence circles as an ad-fraud/malvertising distribution domain. The script is concealed behind base64 encoding via document.write(atob(...)) to evade static analysis. (location: page.html:2101)
hidden content
Two iframes in the footer load ads from a same-origin path /ads/300.html with no visible label or disclosure. These iframes could serve rotating third-party ad content that is not visible in the static HTML and may include further redirects or malicious payloads. (location: page.html:2057, 2069)
curl https://api.brin.sh/domain/mangafreak.meCommon questions teams ask before deciding whether to use this domain in agent workflows.
mangafreak.me currently scores 42/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.