context safety score
A score of 45/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
malicious redirect
script/meta redirect patterns detected in page source
cloaking
Page conditionally redirects based on referrer or user-agent
phishing
Page impersonates Google sign-in with credential form
social engineering
Site prominently uses urgency and trust-building language ('We've been paying out for 10 years', '$2000 Weekly Prize', 'Sound too good to be true? Sign Up and let us prove you wrong!', 'Start Earning Instantly') consistent with get-paid-to (GPT) scam patterns that harvest personal data and email credentials under the guise of earning opportunities. (location: page.html:261, page-text.txt:25,542-543)
credential harvesting
Login form collects email and password fields and submits them via AJAX POST to a relative action.php endpoint without any visible server-side domain binding in the client code. The Google OAuth flow also routes through a first-party intermediary (action.php?action=getGoogleUrl) before redirecting, meaning Google OAuth tokens pass through the site's own backend rather than directly to Google, creating an opportunity to intercept OAuth codes. (location: page.html:286-291, page.html:187-195)
credential harvesting
During signup, the dosignup() function makes a cross-origin POST to https://ipv6.freeprize.world/lib/scripts/php/ipv6.php before submitting the signup form. User signup data (including email) is tied to a response from this third-party domain ('freeprize.world'), which is a suspicious domain name unrelated to timebucks.com and could be used to correlate or exfiltrate user registration data. (location: page.html:882-893, page-text.txt:642)
hidden content
A 1x1 pixel hidden iframe is injected dynamically by Cloudflare's challenge platform script to load /cdn-cgi/challenge-platform/scripts/jsd/main.js with inline script execution inside the iframe. While this is a known Cloudflare bot-detection technique, it represents hidden content executing scripts invisible to users. (location: page.html:1195)
hidden content
The login form div (#login) is initialized with style='display:none;' and the additional signup fields div (#additional-signup-fields) is also hidden by default (display:none), meaning credential collection fields are hidden from users until interacted with, which can mask their existence from automated scanners. (location: page.html:266, page.html:612)
curl https://api.brin.sh/domain/timebucks.comCommon questions teams ask before deciding whether to use this domain in agent workflows.
timebucks.com currently scores 45/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.