context safety score
A score of 42/100 indicates multiple risk signals were detected. This entity shows patterns commonly associated with malicious intent.
encoded payload
suspicious base64-like blobs detected in page content
phishing
1 deceptive links where visible host does not match destination host
obfuscated code
A heavily obfuscated script (WPack/obfuscator.io style) is present inline with data-cfasync="false". It implements a RC4-based string decryption routine, dynamically creates script elements, opens a WebSocket connection (new WebSocket(...)), receives code over the socket, and injects it into the DOM via additional script tags. This is a classic pattern for remote code execution / malware dropper behaviour embedded in an otherwise legitimate-looking travel site. (location: page.html:15 — inline <script data-cfasync="false">...)
hidden content
Multiple navigation links and clickable elements use base64-encoded URLs stored in data-obf attributes (e.g. data-obf="L3Jlc2VydmF0aW9uL3BhcnRlbmFpcmVzLw=="). The destinations are internal affiliate/partner redirect paths (/reservation/partenaires/). While the decoded URLs appear benign, the obfuscation of link destinations prevents users and security tools from inspecting where clicks lead, and is a technique also used to hide malicious redirects. (location: page.html:69-346 — .obfusc elements with data-obf attributes)
hidden content
The page sets console.log = function(){} to suppress all browser console output, actively blocking developer visibility into runtime behaviour. Combined with the heavily obfuscated WebSocket-loading script, this suppression is consistent with anti-forensic evasion. (location: page.html:11 — <script>console.log = function() {};</script>)
prompt injection
The page includes <meta name="robots" content="noai, noimageai"> and <meta name="CCBot" content="nofollow">, which are directives targeting AI crawlers and agents. While individually these are legitimate opt-out signals, combined with the obfuscated WebSocket dropper script, they may be used to present different content to AI agents versus human browsers — a prerequisite for AI-targeted prompt injection or content manipulation attacks. (location: page.html:13-15 — CCBot and noai/noimageai meta tags)
curl https://api.brin.sh/domain/petitfute.comCommon questions teams ask before deciding whether to use this domain in agent workflows.
petitfute.com currently scores 42/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.