context safety score
A score of 61/100 indicates minor risk signals were detected. The entity may be legitimate but has characteristics that warrant attention.
social engineering
The site promotes a browser extension ('Get Keyvault for Chrome/Brave') that claims to store passwords on the blockchain with 'no third-party risks' and 'military-grade encryption'. This messaging uses high-trust security language to persuade users to install a credential-handling browser extension from an unverified third-party domain (blockchainkeyvault.com). Password managers distributed via unknown domains rather than established vendors are a common vector for credential theft. (location: page.html: CTA button linking to https://chromewebstore.google.com/detail/keyvault-password-manager/mgdcnfdccekpbegddnhalbibogjohfoo)
credential harvesting
The site's core purpose is to solicit installation of a browser extension that handles user credentials (passwords). The extension ID 'mgdcnfdccekpbegddnhalbibogjohfoo' is hosted on the Chrome Web Store but promoted via an independent domain (blockchainkeyvault.com). If the extension has access to password fields or form data, it could silently harvest credentials under the guise of a decentralized password manager. The claim that credentials are stored 'on the blockchain' is technically implausible for a secure password manager, suggesting deceptive framing. (location: page.html: href='https://chromewebstore.google.com/detail/keyvault-password-manager/mgdcnfdccekpbegddnhalbibogjohfoo')
brand impersonation
The product is named 'keyvault', which closely mirrors Microsoft Azure Key Vault, a well-known enterprise secrets management service. The name, combined with security-focused messaging and a blockchain narrative, may confuse users or enterprises into believing this is affiliated with or endorsed by Microsoft or another established security vendor. (location: page.html: <title>keyvault</title> and header logo link text 'keyvault')
social engineering
The page uses persuasive but unverifiable security claims: 'Military-Grade Encryption', '256-bit AES-GCM', 'You have the only copy of your encryption key', and 'no central authority, no trust issues'. These are classic social engineering trust-building phrases used to lower user defenses and encourage installation of a credential-handling extension. The claim of blockchain-based credential storage is technically dubious and may be designed to sound innovative rather than be accurate. (location: page.html: feature cards section with headings 'Decentralized', 'You Own the Key', 'Military-Grade Encryption')
curl https://api.brin.sh/domain/blockchainkeyvault.comCommon questions teams ask before deciding whether to use this domain in agent workflows.
blockchainkeyvault.com currently scores 61/100 with a caution 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.