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
obfuscated code
Large obfuscated JavaScript block using Function() constructor with TextDecoder and base64-decoded Uint8Array payload. The decoded string contains hex-encoded operations with arithmetic shifts and push/pull patterns consistent with environment fingerprinting or anti-bot evasion code executing at runtime without being inspectable in source. Pattern: Function(new TextDecoder('utf-8').decode(new Uint8Array((atob('NzY2...'))... (location: page.html:line 699 — inline <script> block before __cpa.mainAsync.js)
obfuscated code
Cloudflare challenge script injected via hidden 1x1 iframe using dynamic innerHTML assignment to bypass CSP and script nonce restrictions. The iframe is invisible (visibility:hidden, 0 border, absolute position top:0 left:0) and injects a script tag loading '/cdn-cgi/challenge-platform/scripts/jsd/main.js' with encoded parameters r and t. (location: page.html:line 1071 — inline <script> at end of <body>)
hidden content
A 1x1 pixel invisible iframe is injected into the DOM (height=1, width=1, position absolute, visibility hidden) to load and execute Cloudflare challenge scripts. While potentially legitimate bot-mitigation, this pattern is also used for covert fingerprinting, tracking, or exfiltrating user data without user awareness. (location: page.html:line 1071 — iframe created by inline script at bottom of <body>)
social engineering
Prominent infoBar banner fixed to the top of every page view solicits users to register at a third-party site (reflect4.me) by framing it as a free personal proxy configuration offer: 'Configure your personal web proxy for free and share it with friends!' The link goes to reflect4.me/register with a UTM tracking parameter (utm_source=front_top_banner), not to croxyproxy.com, redirecting users off-site to a registration funnel. (location: page.html:lines 1065-1070 — #infoBar div, <a target='_blank' href='https://reflect4.me/register?utm_source=front_top_banner'>)
malicious redirect
The site acts as an open web proxy, routing all user web traffic through its servers. Any URL entered by a user is proxied through CroxyProxy infrastructure (form action='servers'), enabling man-in-the-middle interception of all proxied HTTP/HTTPS traffic, session tokens, cookies, and credentials entered on destination sites. This is an inherent architectural capability for traffic interception. (location: page.html:line 884 — <form method='post' id='request' action='servers'>)
credential harvesting
As an open web proxy, CroxyProxy is architecturally positioned to intercept credentials submitted through proxied sessions. The service explicitly proxies traffic to sites like Facebook, Google, YouTube, and Twitter (listed as quick links). Users entering credentials on these sites via the proxy expose them to the proxy operator. The sign-in modal (#accountModal) loads its form dynamically from /account/session/form, meaning credentials are also submitted to CroxyProxy directly. (location: page.html:lines 736-742 — #accountModal with data-modal-url='/account/session/form'; line 938 — quick links to Facebook, Google, Twitter, Instagram)
social engineering
Multiple browser extension IDs are embedded in a meta tag (extensionOrigins), referencing 5 Chrome extensions associated with CroxyProxy. This encourages users to install browser extensions that would have broad access to all browsing activity, not just proxied sessions. Extension installation is promoted in the page body as well. (location: page.html:line 10 — <meta name='extensionOrigins' content='chrome-extension://lmmpgfjnchldhcieiiegcpdmaidkaanb,...'>; line 943 — browser extension promotion link)
curl https://api.brin.sh/domain/croxyproxy.comCommon questions teams ask before deciding whether to use this domain in agent workflows.
croxyproxy.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.