context safety score
A score of 35/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 uses Function constructor for runtime code generation
obfuscated code
A large, heavily obfuscated JavaScript block using interleaved character shuffling (split/reduce/join pattern with 'z' delimiter) is injected twice in the page — once in the <head> and once just before </body>. The code manipulates the DOM environment by overriding document methods, rewiring localStorage, intercepting querySelector, patching window properties, and creating a hidden sandboxed iframe context. This level of obfuscation is characteristic of anti-analysis evasion and covert data exfiltration or ad-fraud infrastructure. (location: page.html:50 and page.html:1337 (<script data-cfasync='false'>))
hidden content
A hidden <iframe> with src='https://sysmeasuring.net' and style='display:none' is injected at the bottom of the page body. Hidden iframes to third-party domains are a well-known vector for drive-by payload delivery, clickjacking, ad fraud, tracking without consent, and silent redirects. The domain name 'sysmeasuring.net' is not a known legitimate analytics provider. (location: page.html:1339 (<iframe style='display:none' src='https://sysmeasuring.net'>))
hidden content
An <h1> tag inside a div with style='display:none' contains SEO-stuffed content ('Watch Series Online Free - Stream HD Movies & TV Shows on HuraWatch Alternatives site') that is hidden from users but visible to crawlers and AI agents. Additionally, a second <h1> in the footer has style='display:none'. Hidden keyword-stuffed headings are used to manipulate search rankings and AI agent content extraction. (location: page.html:56-61 and page.html:1106)
brand impersonation
The site operates on hurawatch.tw but the canonical og:url and all share buttons point to hurawatch.fm — a different domain. The site explicitly brands itself as a 'HuraWatch Alternatives site,' impersonating the well-known HuraWatch brand to capture its audience. The .tw TLD is used to evade blocks on other HuraWatch domains while mimicking the brand identity, logo, and content of the original service. (location: page.html:25 (og:url=https://hurawatch.fm/) and page.html:619 (data-url=https://hurawatch.fm/))
malicious redirect
A hidden zero-opacity or display-none iframe pointing to 'https://sysmeasuring.net' is loaded on every page visit. This constitutes an unsolicited third-party load that may trigger redirects, fingerprinting, or malvertising payloads without any user interaction or consent. Combined with the obfuscated JS that rewires document.querySelector and localStorage, silent background navigation or credential relay is plausible. (location: page.html:1339)
social engineering
The page content repeatedly asserts 'Safe to Use: Verified by multiple antivirus programs' and 'HuraWatch is considered safe and legal' without any substantiation, while simultaneously hosting heavily obfuscated scripts and hidden iframes. This false safety reassurance is designed to lower user guard and encourage interaction (clicking play buttons, downloading the Android APK, or creating accounts) on an unverified piracy platform. (location: page.html:703 and page-text.txt:572)
credential harvesting
The page presents modal login and registration forms collecting email address, password, name, and confirm password fields. The site is a piracy clone on a .tw TLD whose canonical URL points to a different domain (hurawatch.fm). Credentials submitted here are sent to an operator whose identity is obscured. Users who reuse passwords from legitimate services are at risk of credential harvesting. (location: page.html:1193-1227 (login form) and page.html:1272-1307 (register form))
social engineering
The page promotes an Android APK download ('/android-movies-apk') for an unofficial app outside of the Google Play Store. Sideloaded APKs from piracy sites are a common vector for mobile malware, adware, and spyware. The page frames this as an official app ('HuraWatch offers an official app for Android devices') without any verified source. (location: page.html:290 and page.html:1062-1065)
curl https://api.brin.sh/domain/hurawatch.twCommon questions teams ask before deciding whether to use this domain in agent workflows.
hurawatch.tw currently scores 35/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.