context safety score
A score of 76/100 indicates minor risk signals were detected. The entity may be legitimate but has characteristics that warrant attention.
credential harvesting
The GIGYA_URL is malformed: 'https://gigya-prod-eu1./js/gigya.js' — the hostname is incomplete (missing the TLD after 'gigya-prod-eu1.'), which could cause authentication tokens and session credentials to be sent to an unresolvable or potentially hijackable domain. The Gigya SSO integration handles user authentication (login, registration, password reset) for the Renault platform. (location: page.html:108, window.GIGYA_URL)
hidden content
Three suspicious base64 blobs were flagged by Tier 2 heuristics. One confirmed base64 value found in APP_CONFIG: the evsmartrouting API key 'UmVuYXVsdFdlYnNpdGU6WTBITTVxTnI3MktxWGZUVXBWeTI=' decodes to 'RenaultWebsite:Y0HM5qNr72KqXfTUpVy2', which is a plaintext Basic Auth credential (username:password) embedded in the page source and exposed to all clients. (location: page.html:37, window.APP_CONFIG.api.evsmartrouting.key)
credential harvesting
API keys and secrets are exposed in plaintext in client-side JavaScript: Google Maps API key ('AIzaSyCAPAp5G88iHILzULTPHRsqcn_FbB-z-Kg'), Google reCAPTCHA site key ('6LcygSoaAAAAAMBmkQItlJmAk3gyhT5wXFEqg2JD'), reCAPTCHA Enterprise key ('6LdJ4aAfAAAAAM4havYH4OwOvzZmUyqIvCtM0wUr'), and a Basic Auth credential for the EV smart routing API embedded as base64 ('RenaultWebsite:Y0HM5qNr72KqXfTUpVy2'). These allow abuse of Renault's third-party service integrations. (location: page.html:37, window.APP_CONFIG)
malicious redirect
The redirectOld() function conditionally redirects users to '/oldbrowser.html' based on user-agent string inspection. The redirect is bypassed only if the user-agent contains 'bot' or 'Preview', meaning automated scanning agents without those strings in their UA would be redirected. This is a bot/agent evasion technique that could mask different content served to real users versus scanners. (location: page.html:74-92, redirectOld() function)
curl https://api.brin.sh/domain/cdn.group.renault.comCommon questions teams ask before deciding whether to use this domain in agent workflows.
cdn.group.renault.com currently scores 76/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.