context safety score
A score of 30/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
A dynamically injected script loads from '//precious-primary.com/cwD-9.6-bq2R5mlRSfWxQU9/Nsj/Ql3IOyTTg/5XNrib0U2INTDeck5-OVDmka3x' — an obfuscated path on an unknown third-party domain. The script is appended to the DOM at runtime using document.createElement and insertBefore, bypassing static analysis. This pattern is consistent with malvertising, drive-by redirect, or payload delivery infrastructure. (location: page.html:lines 37-44 (footer script block); page-text.txt:lines 10-18)
obfuscated code
All inline and external scripts use a non-standard MIME type 'eb063a9e5211998ce2869277-text/javascript' instead of 'text/javascript'. This is a Cloudflare Rocket Loader obfuscation technique that defers script execution, but it also masks the true type and execution timing of scripts — including the malicious precious-primary.com loader — making detection harder. (location: page.html: multiple script tags with type='eb063a9e5211998ce2869277-text/javascript')
malicious redirect
The page is served from gomuraw.blog but all canonical links, og:url, structured data, and asset URLs point to gomuraw.art. This domain mismatch means the .blog domain likely serves as a traffic entry point or shadow domain that silently redirects or mirrors content from gomuraw.art, obscuring the true origin and enabling evasion of blocklists targeting the primary domain. (location: page.html:line 1 (canonical: https://gomuraw.art, og:url: https://gomuraw.art); metadata.json (url: https://gomuraw.blog))
brand impersonation
The site impersonates well-known manga brands and titles including 'Naruto' (ナルト), 'Jujutsu Kaisen' (呪術廻戦), and 'Kingdom' (キングダム) to attract users searching for legitimate licensed content. The site openly identifies itself as 'mangaraw' / '漫画raw', a known piracy brand, and uses keywords like 'manga1001' — all associated with unauthorized redistribution of copyrighted Japanese manga. (location: page.html:line 1 (meta keywords); page-text.txt:line 3 (content listings); page-text.txt:line 9 (footer disclaimer))
social engineering
The footer disclaimer states 'Mangaraw はサーバー上にファイルを保存せず、サードパーティのサービスでホストされているメディアにリンクしているだけです' (Mangaraw does not store files on its servers, only links to media hosted on third-party services). This is a classic legal deflection tactic used by piracy sites to mislead users about liability and to falsely legitimize the service, encouraging continued engagement. (location: page-text.txt:line 9)
hidden content
The Cloudflare Rocket Loader script (rocket-loader.min.js) uses the custom data-cf-settings attribute value 'eb063a9e5211998ce2869277-|49' as a nonce/token that also appears as the fake MIME type prefix on all deferred scripts. This mechanism hides the actual script content and execution from standard page inspection until Rocket Loader decodes and fires them, which can conceal the malicious precious-primary.com loader from passive scanners. (location: page.html:line 45 (rocket-loader script tag); all script tags with type containing 'eb063a9e5211998ce2869277')
curl https://api.brin.sh/domain/gomuraw.blogCommon questions teams ask before deciding whether to use this domain in agent workflows.
gomuraw.blog currently scores 30/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.