context safety score
A score of 39/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
cloaking
Page loads content in transparent or zero-size iframe overlay
social engineering
TraffMonetizer is a residential proxy network that monetizes users' internet bandwidth by routing third-party traffic through their devices. The site uses persuasive language ('passive income', 'completely safe and secure', 'win-win-win') to downplay significant risks: user devices become exit nodes for unknown third-party traffic including web scraping, ad fraud, and location-based data collection. The business model inherently turns users into unwitting proxies for activities they cannot audit or control, despite claims of KYC compliance. (location: page.html:1044-1051, page.html:1431-1432, page-text.txt:694-696)
social engineering
The FAQ section answers 'Is it legal?' and 'Is it safe?' with unverified absolute assurances ('100% legal and compliant', 'completely safe and secure') to pre-empt user skepticism. These blanket safety claims are designed to overcome user hesitation without providing verifiable third-party audits or transparent disclosure of what traffic actually flows through devices. (location: page.html:1563-1570, page.html:1621-1628)
social engineering
The site offers USDT TRC20 (Tron Network) cryptocurrency as primary withdrawal method and only supports wire transfer for amounts over $1,000. Crypto-only payouts at low thresholds ($10 minimum) are a pattern associated with fraudulent passive-income schemes that may not pay out reliably, and reduce traceability of fund flows. (location: page.html:1530-1533, page-text.txt:795-797)
malicious redirect
The FAQ 'How to start earning?' section contains a sign-up link pointing to 'https://app.traffomonetizer.com/register' — note the extra 'o' in 'traffomonetizer' — which is a typosquatted domain distinct from the legitimate 'app.traffmonetizer.com' used throughout the rest of the site. This mismatched URL could redirect users to a credential-harvesting or phishing page. (location: page.html:1511)
credential harvesting
A hidden popup form (pum-11288, slug 'sdk-apply-popup') collects name, email, OS type, and app store links via Contact Form 7. The popup has no visible trigger configured (triggers:[]) and is rendered hidden in the DOM. While it may be a developer SDK application form, the combination of hidden-trigger popup, personal data collection (name, email), and no visible disclosure of data handling raises credential/PII harvesting risk. (location: page.html:1704-1790)
hidden content
The Akismet anti-spam honeypot field contains a hidden textarea and dynamically set timestamp input rendered with 'display:none' styling. While standard WordPress anti-spam practice, the hidden form fields (including _wpcf7_ak_hp_textarea and ak_js_1) are invisible to users and could mask additional data collection beyond their stated anti-spam purpose. (location: page.html:1774)
hidden content
A Tidio live chat script is loaded from an external third-party domain (code.tidio.co) at the very end of the page body. Tidio can track visitor behavior, collect chat inputs including personal data, and load additional scripts from its CDN. No disclosure of this third-party data collection is visible to users on the page. (location: page.html:1983)
curl https://api.brin.sh/domain/traffmonetizer.comCommon questions teams ask before deciding whether to use this domain in agent workflows.
traffmonetizer.com currently scores 39/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.