context safety score
A score of 34/100 indicates multiple risk signals were detected. This entity shows patterns commonly associated with malicious intent.
cloaking
Page conditionally redirects based on referrer or user-agent
brand impersonation
The page is hosted on bodegaaurrera.com.mx but uses Walmart/Bodega Aurrera branding assets (Walmart font 'Bogle' from walmartimages.com, Bodega Aurrera SVG logo via inline SVG with id 'd_header-login-bodega_red'), Walmart analytics namespace (window.walmart), and Adobe DTM tag for Walmart. The domain bodegaaurrera.com.mx is not an official Walmart-owned domain for this brand, indicating impersonation of the Bodega Aurrera (Walmart Mexico) brand. (location: page.html:8-11, page.html:29)
phishing
The page title is 'Verify Your Identity' (English) while the page language is set to Spanish ('lang=es') and the visible content says 'Verifica tu identidad' / 'Mantén presionado el botón para confirmar que no eres un robot.' This is a fake identity verification/CAPTCHA page pattern commonly used in phishing flows to intercept users and harvest credentials or personal data under the guise of bot protection. (location: page.html:2, page-text.txt:1)
social engineering
The page uses a fake CAPTCHA/bot-protection challenge ('Mantén presionado el botón para confirmar que no eres un robot') powered by PerimeterX (PXAFlYiz9n) to manipulate users into interacting with the page. The challenge is styled to resemble a legitimate bot check but is served from a suspicious domain to build false trust and lower user defenses before credential harvesting. (location: page-text.txt:1, page.html:29)
prompt injection
The page injects JavaScript via a dynamically constructed script src using unvalidated URL parameters: 'var hc=getUrlParam("g","a"); var captchajs="/px/"+window._pxAppId+"/captcha/captcha.js?a=c&m=0&g="+hc; document.getElementById("blockScript").src=captchajs;'. An attacker controlling the 'g' query parameter can influence the script URL loaded, enabling parameter-based injection. Similarly, the uuid parameter is reflected into the DOM via innerHTML, which could enable XSS/injection if sanitization is bypassed. (location: page-text.txt:1, page.html:2-6)
malicious redirect
The page dynamically loads an external script from assets.adobedtm.com (Adobe DTM/Launch) using a hardcoded launch ID (ENb669ecb013cf4aa89de0580c69e13c1a) set via launchScript.src on a non-official domain. This Adobe DTM script, if the launch property is controlled by an attacker, can execute arbitrary JavaScript and perform redirects. Combined with the suspicious hosting domain, this creates a potential malicious redirect vector. (location: page.html:9)
hidden content
The page contains a script block that is invisible to the user but sets up PerimeterX telemetry and CAPTCHA configuration (window._pxAppId, window._pxJsClientSrc, window._pxHostUrl, locale, challenge translations) entirely in JavaScript without any visible disclosure. The Walmart analytics dataLayer is also silently populated with cookies (walmart.id), referrer, and host data, exfiltrating user session information without consent notice. (location: page.html:8-9, page-text.txt:1)
curl https://api.brin.sh/domain/bodegaaurrera.com.mxCommon questions teams ask before deciding whether to use this domain in agent workflows.
bodegaaurrera.com.mx currently scores 34/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.