context safety score
A score of 46/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
hidden content
Browser fingerprinting script using FingerprintJS silently collects a unique visitor ID and stores it in a cookie (fp_fpid) and submits it as a hidden form field (fpId). This enables persistent cross-session tracking without user disclosure. (location: page.html:371-388, hidden input name='fp' id='fpId' at line 370)
hidden content
LiveInternet analytics counter image is initially hidden (display:none) and its src is dynamically set via JavaScript to transmit referrer, screen dimensions, color depth, page URL, and page title to counter.yadro.ru — a Russian analytics service. Data exfiltration occurs invisibly to the user. (location: page.html:436-463)
social engineering
Third-party push notification script dynamically injected from cdn.speraspace.com with encoded parameters (htext is base64: 'Разрешите, чтобы скачать' — 'Allow to download'). This pattern is commonly used to socially engineer users into granting browser push notification permissions under the guise of a download action. (location: page.html:478-486, src URL parameter htext=0KDQsNC30YDQtdGI0LjRgtC1LCDRh9GC0L7QsSDRgdC60LDRh9Cw0YLRjA%3D%3D)
malicious redirect
Third-party ad script loaded from jsc.adskeeper.co.uk (loaded twice, in both left and right ad panels). adskeeper is a known ad network that can serve malvertising and redirect users to unwanted or malicious destinations. The script is loaded async without integrity checks. (location: page.html:56, page.html:409)
hidden content
Pixel beacon loaded from u.fastpic.org/p/JCSXGetcs — an undocumented tracking endpoint on a subdomain. No visible attribution or disclosure, consistent with a silent tracking pixel pattern. (location: page.html:30)
curl https://api.brin.sh/domain/fastpic.ruCommon questions teams ask before deciding whether to use this domain in agent workflows.
fastpic.ru currently scores 46/100 with a suspicious 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.