context safety score
A score of 43/100 indicates multiple risk signals were detected. This entity shows patterns commonly associated with malicious intent.
brand impersonation
Page explicitly impersonates Bank of America's EDD (Employment Development Department) service with the heading 'Please Wait... Redirecting you to BOFA EDD', designed to deceive victims into believing they are being sent to a legitimate BofA government benefits portal. (location: page.html:3, page-text.txt:2)
malicious redirect
Obfuscated JavaScript fetches commands from a Telegram bot (bot token: 6252937309:AAFfH3t3WtK9bBg72bIQkzcnvR0R2gSDRA8) via the Telegram API and uses the bot's latest message text as a redirect URL. If the message starts with 'http', the victim is redirected to that attacker-controlled URL; otherwise redirected to a decoy Google search. This is a live, remotely-controlled redirect mechanism allowing the attacker to change the phishing destination at any time. (location: page.html:6-21)
obfuscated code
JavaScript uses array-based string obfuscation (_0x3587) to obscure method calls such as 'location', 'replace', 'startsWith', 'then', 'ok', 'json', and Telegram API endpoints. This technique is used to evade static analysis and security scanners while dynamically constructing the malicious redirect logic. (location: page.html:9-21)
phishing
The site is a phishing landing page targeting victims of BofA EDD (bank unemployment/benefits card) fraud. The domain name 'web-activateddcard.web.app' mimics EDD card activation flows. Combined with the BofA EDD impersonation and dynamic Telegram-controlled redirect, this is a credential-harvesting phishing kit delivery mechanism aimed at benefits card holders. (location: metadata.json:1, page.html:3)
credential harvesting
The Telegram bot acts as a command-and-control channel: the attacker sends a phishing URL as a Telegram message, and any visitor to this page is silently redirected to that URL. This infrastructure is consistent with credential harvesting operations where victims are sent to fake BofA EDD login or card activation pages to steal account credentials and card details. (location: page.html:11-21)
social engineering
The page uses a fake loading/redirect message ('Please Wait... Redirecting you to BOFA EDD') to create the illusion of a legitimate automated redirect, reducing victim suspicion while the malicious JavaScript executes and fetches the attacker's target URL from Telegram. (location: page.html:3, page-text.txt:2)
curl https://api.brin.sh/domain/web-activateddcard.web.appCommon questions teams ask before deciding whether to use this domain in agent workflows.
web-activateddcard.web.app currently scores 43/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.