context safety score
A score of 46/100 indicates multiple risk signals were detected. This entity shows patterns commonly associated with malicious intent.
phishing
The page at amcrestcloud.com presents a login form titled 'Secure login' collecting username, password, and an MFA 'Secret Key' field. The domain amcrestcloud.com is separate from the legitimate Amcrest brand domain (amcrest.com). While the domain is 4151 days old and the TLS cert is valid, the TLS certificate expires in only 5 days — an anomaly consistent with a phishing infrastructure that is short-lived or poorly maintained. The page uses a non-standard CMS fingerprint ('Drumlapress') not associated with Amcrest's official platforms. (location: page.html:7, page.html:294, metadata.json (days_until_expiry: 5))
credential harvesting
The login form collects username, password, and a Secret Key (MFA/TOTP code) field (name=secretkey). The MFA field is hidden by default via the HTML 'hidden' attribute on the containing div but is present in the DOM and can be activated client-side. Harvesting all three factors (username + password + live OTP) constitutes a real-time credential relay attack pattern. The preflight authentication check endpoint 'https://www.amcrestcloud.com/?option=com_camcloudauth&task=auth.check' is a non-standard Joomla component that could relay credentials to a third party. (location: page.html:294 (form action=/secure-login, name=secretkey, loginPreflightPath))
brand impersonation
The page impersonates the Amcrest Cloud service using the Amcrest logo (/templates/tpl_amcrest/images/amcrest-logo.png), Amcrest branding, and links to legitimate amcrest.com pages (privacy policy, products, social media). However, the site operates on amcrestcloud.com rather than the official amcrest.com domain, and uses a CMS generator tagged as 'Drumlapress' rather than any known Amcrest technology stack, indicating a spoofed brand portal. (location: page.html:7 (meta name=generator content=Drumlapress), page.html:294 (navbar-brand img src, footer links))
hidden content
The MFA 'Secret Key' input field (id=secretkey, name=secretkey) is rendered inside a div with the HTML 'hidden' attribute, making it invisible to the user on initial page load. This field can be revealed programmatically after a first authentication attempt to silently capture OTP codes, which is a hallmark of real-time phishing proxy kits. The label for this field is also hidden (class=hide). (location: page.html:294 (<div class="form-group mfa-form-group" hidden>))
curl https://api.brin.sh/domain/amcrestcloud.comCommon questions teams ask before deciding whether to use this domain in agent workflows.
amcrestcloud.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.