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
phishing
1 deceptive links where visible host does not match destination host
hidden content
Six gambling/slot site banner ads are embedded in a CSS-hidden div (class 'blox mlb kln' styled with 'display: none'). The links point to akseskaiko.cam/login, menujupenta.site/login, goid.space/login, injd.site/login, kegz.site/login, and goratu.site/login — all leading to /login endpoints on unrelated third-party domains. These are invisible to normal users but present in the DOM and fully crawlable/clickable by automated agents. (location: page.html line 211, CSS style block lines 154-158: '.blox.mlb.kln, #close-teaser, .kln { display: none; }')
malicious redirect
Hidden gambling banners link directly to /login pages on six external domains: akseskaiko.cam, menujupenta.site, goid.space, injd.site, kegz.site, goratu.site. These are credential-harvesting login pages for online gambling operations embedded invisibly within a legitimate-appearing anime fansub site. (location: page.html line 211)
credential harvesting
All six hidden banner links target /login endpoints (e.g. akseskaiko.cam/login, menujupenta.site/login, goid.space/login, injd.site/login, kegz.site/login, goratu.site/login) on third-party gambling domains. Users or agents following these links would be directed to login/registration forms on unrelated gambling platforms. (location: page.html line 211)
social engineering
The site announcement banner uses urgency framing ('ANICHIN.DATE KENAK BLOK, ANTISIPASI BLOK JANGAN LUPA DIBOOKMARK') to pressure users into bookmarking the domain and visiting anichin.team and anichin.watch as fallback domains. This social engineering tactic drives users to alternative domains that may not be controlled by the same operators. (location: page.html line 214, page-text.txt line 44)
hidden content
A script tag loads 'disable-devtool' from cdn.jsdelivr.net with the attribute 'disable-devtool-auto url=https://anichin.team', which actively suppresses browser developer tools on the page. This is a deliberate anti-analysis measure designed to prevent users and security researchers from inspecting the page's hidden content, including the concealed gambling ads. (location: page.html lines 159-163)
curl https://api.brin.sh/domain/anichin.cafeCommon questions teams ask before deciding whether to use this domain in agent workflows.
anichin.cafe 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.