context safety score
A score of 58/100 indicates minor risk signals were detected. The entity may be legitimate but has characteristics that warrant attention.
encoded payload
suspicious base64-like blobs detected in page content
credential harvesting
A JWT bearer token is hardcoded and written to localStorage via inline JavaScript on every page load: localStorage.setItem('expToken', '<JWT>'). The token encodes sub:48496 with an expiry of 1806067938 (approx. 1 year from issuance) and is subsequently read back and injected as an Authorization header in all API calls to mesa-backend-prod. Any script on the page (including third-party trackers) can read localStorage and exfiltrate this token. (location: page.html:423 / page-text.txt:347)
credential harvesting
The JWT token stored in localStorage is directly retrieved and inserted as a Bearer token in axios Authorization headers for API calls (ecommerce and banners endpoints). This pattern exposes the credential to XSS attacks and to all JavaScript executing on the page, including Facebook Pixel and Google Tag Manager scripts. (location: page.html:1070 / page-text.txt:1070)
hidden content
Google Tag Manager noscript iframe is rendered with style='display:none;visibility:hidden', making it invisible to users. While GTM itself is common, the hidden iframe executes tracking in a non-transparent manner and could be abused to load additional payloads if the GTM container (GTM-MBCZVRV2) were compromised. (location: page.html:76-78)
social engineering
Footer links under 'Acerca de MESA 24/7' and 'Más información' all point to mesa247.pe (Peru domain) while the page is served from experiencias.mesa247.co (Colombia domain). This domain mismatch could confuse users about which entity they are interacting with and may indicate an inconsistently maintained clone of a Peru-origin site deployed to a 65-day-old Colombia subdomain. (location: page.html:232-244)
curl https://api.brin.sh/domain/experiencias.mesa247.coCommon questions teams ask before deciding whether to use this domain in agent workflows.
experiencias.mesa247.co currently scores 58/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.