context safety score
A score of 46/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
JavaScript contains heavy hex-escape encoding typical of obfuscation
obfuscated code
Heavily obfuscated JavaScript present in the page head. The script uses a string-array rotation pattern (a0_0x38f7/a0_0x38e6), numeric hex arithmetic obfuscation, and a Unicode symbol string ('h') as an initial encoded payload. This is a classic JavaScript obfuscation technique (similar to obfuscator.io output) used to hide the true intent of code from static analysis. The obfuscated block generates and injects CSS dynamically, but the full decoded behavior cannot be verified without execution. (location: page.html:70-73 (<script> block in <head>))
hidden content
The page sets a long-lived tracking cookie (expires 2031) via inline JavaScript before the DOM loads: document.cookie='tv=1772640060; expires=Wed, 28 May 2031 11:37:01 GMT; domain=.alohatube.com; path=/;'. This cookie is set silently with no user consent notice, persists for ~5 years, and is scoped to the entire .alohatube.com domain. Combined with the 'pGetACookie' and 'mbv' cookie-checking functions, this enables persistent cross-session user tracking without disclosure. (location: page.html:26 (inline <script> in <head>))
malicious redirect
The iframe ad units load content from a1tb.com (a CDN/ad domain closely tied to alohatube.com) with the sandbox attribute including 'allow-popups' and 'allow-popups-to-escape-sandbox'. The 'allow-popups-to-escape-sandbox' permission explicitly allows popups spawned by the iframe to break out of the sandbox context, enabling unrestricted navigation or popup windows that could redirect users to third-party destinations outside the sandbox's security restrictions. (location: page.html:138-143 (three <iframe> ad units in .advbox))
hidden content
The inline script at line 38 contains a frame-busting check: 'this.top.location !== this.location && (this.top.location = this.location)'. While a common anti-clickjacking technique, it can also be used to forcibly escape iframe embedding, which in adversarial contexts can redirect the top-level browsing context to the current page URL, overriding any parent frame navigation controls. (location: page.html:38 (inline <script> in <head>))
curl https://api.brin.sh/domain/alohatube.comCommon questions teams ask before deciding whether to use this domain in agent workflows.
alohatube.com currently scores 46/100 with a suspicious verdict and medium 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.