context safety score
A score of 28/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
obfuscated code
Large heavily obfuscated JavaScript block using percent-encoded string decoding, character shifting cipher (charCode offset rotation mod 95), and dynamic function/URL assembly. The decoded content constructs ad network URLs and behavioral tracking logic at runtime, making static analysis impossible. Located at page.html line 99 inside a data-cfasync='false' script tag. (location: page.html:99)
malicious redirect
Third-party ad script loaded from //cupbearergrowllurch.com/on.js — a non-reputable, suspicious domain with an animal-nonsense name pattern commonly associated with malvertising networks. Loaded with data-cfasync='false' to bypass Cloudflare bot filtering, and fires btabbuqd() callbacks on both load and error events, indicating active payload delivery hooks. (location: page.html:100)
malicious redirect
Third-party ad script loaded from //lf.enrolcopals.com/sg3Dl3b7ENrLJ/137104 — an unfamiliar domain with randomized path segments typical of malvertising redirect chains or tracking pixels used in ad fraud ecosystems. (location: page.html:179)
malicious redirect
Third-party ad library loaded from //acscdn.com/script/aclib.js which triggers aclib.runBanner({zoneId:'11004342'}) — a third-party ad CDN with no recognizable affiliation. Combined with the other suspicious ad scripts on the page, this contributes to a multi-layered malvertising stack. (location: page.html:170)
social engineering
Notification box instructs users that if they cannot access the website to instead visit dualeotruyenKY.COM — a different domain (dualeotruyenky.com vs the scanned dualeotruyenyk.com). This redirects users to an alternate domain under operator control, potentially a newer or different infrastructure, bypassing any blocklisting of the current domain. (location: page.html:168-169)
malicious redirect
The canonical URL and og:url meta tags both point to https://dualeotruyenky.com/ while the page is served from https://dualeotruyenyk.com — a domain mismatch. The footer links and tag-container anchors all link to dualeotruyenky.com, indicating the scanned domain may be a shadow clone or redirect farm pointing traffic to the primary domain. (location: page.html:18,36,989,1046)
credential harvesting
Login and registration modals collect username, password, and email directly via plain modal forms (box_pop_login, box_pop_register, box_pop_password). The reCAPTCHA integration is commented out (lines 1103-1105), removing bot protection. Credentials are submitted via JavaScript to /process.php with no visible CSRF token or visible transport security enforcement at the form level. (location: page.html:1083-1225)
hidden content
Registration form contains a commented-out reCAPTCHA v2 block with a hardcoded sitekey (6Lf4zAQqAAAAABnP5eFgvQELXCKMl5Ylixs3G1Ns). Disabling CAPTCHA on an account creation form removes automated abuse protection and may be intentional to allow bulk account creation or credential stuffing infrastructure. (location: page.html:1103-1105)
curl https://api.brin.sh/domain/dualeotruyenyk.comCommon questions teams ask before deciding whether to use this domain in agent workflows.
dualeotruyenyk.com currently scores 28/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.