context safety score
A score of 36/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
credential harvesting
credential form posts to an off-domain endpoint (may be legitimate SSO/OAuth)
cloaking
Page conditionally redirects based on referrer or user-agent
js obfuscation
JavaScript uses Function constructor for runtime code generation
malicious redirect
The domain viadeo.com silently redirects visitors to viadeo.journaldunet.com via a canonical tag and meta 'atm' property containing a Base64-encoded URL (aHR0cDovL3ZpYWRlby5qb3VybmFsZHVuZXQuY29tLw== decodes to http://viadeo.journaldunet.com/). Users and agents navigating to viadeo.com are transparently sent to a third-party domain operated by CCM Benchmark Group / Groupe Le Figaro, which is not the original Viadeo professional network. (location: page.html line 15: <meta property="atm" content="aHR0cDovL3ZpYWRlby5qb3VybmFsZHVuZXQuY29tLw=="> and <link rel="canonical" href="https://viadeo.journaldunet.com/">)
brand impersonation
The site presents itself using the Viadeo brand identity (logo, name, professional networking messaging) but is operated by CCM Benchmark Group under the journaldunet.com domain. The original Viadeo social network ceased operations; this site reuses the brand to drive registrations and data collection for a different corporate entity (CCM Benchmark / Groupe Le Figaro), misleading users who expect the original Viadeo service. (location: page.html lines 13, 52-53, 157-158, 178 — Viadeo branding served from viadeo.journaldunet.com)
credential harvesting
A login form (email + password) posts credentials to https://viadeo.journaldunet.com/p/secure_login. Given that the Viadeo brand is being reused by a different entity and users may believe they are logging into the original Viadeo network, this form harvests credentials under a false brand context. The login endpoint is on a third-party domain, not viadeo.com. (location: page.html lines 208-232: <form method="post" action="https://viadeo.journaldunet.com/p/secure_login"> with txtMail and pwdPassAuth fields)
social engineering
The registration form collects extensive PII including full name (first, last, maiden name), date of birth, city, country, email, password, and mobile phone number. The data is explicitly stated to be shared with advertising partners, data partners, and the broader Groupe Le Figaro ecosystem for commercial profiling. Users registering under the Viadeo brand may not expect this level of data sharing with a media conglomerate. (location: page.html lines 240-426: registration form and RGPD disclosure text; page-text.txt lines 362-382)
hidden content
An invisible tracking pixel is loaded as an absolutely positioned image with no dimensions: <img alt="logo" src="https://akm-static.ccmbg.com/a/aHR0cHM6Ly92aWFkZW8uam91cm5hbGR1bmV0LmNvbS8=/alpha.png" style="position: absolute;">. The src path contains a Base64-encoded URL string, obfuscating the actual tracking target. This is a covert beacon that fires on page load. (location: page.html line 44: <img alt="logo" src="https://akm-static.ccmbg.com/a/aHR0cHM6Ly92aWFkZW8uam91cm5hbGR1bmV0LmNvbS8=/alpha.png" style="position: absolute;">)
curl https://api.brin.sh/domain/viadeo.comCommon questions teams ask before deciding whether to use this domain in agent workflows.
viadeo.com currently scores 36/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.