context safety score
A score of 31/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 conditionally redirects based on referrer or user-agent
js obfuscation
JavaScript uses Function constructor for runtime code generation
brand impersonation
The domain nephobox.com presents itself as TeraBox (a legitimate cloud storage service by Flextech Inc./ByteDance), using TeraBox branding, TeraBox CDN assets (teraboxcdn.com), TeraBox descriptions, and TeraBox meta titles, while operating under a different domain. This is a pattern consistent with a shadow/mirror domain impersonating a known brand. (location: page.html: <title>, og:title, og:description, meta name=description, og:site_name, CDN links to teraboxcdn.com)
obfuscated code
JavaScript uses eval(decodeURIComponent(...)) to execute URL-encoded code at runtime. The decoded payload sets window.jsToken to a long hex string. This obfuscation technique hides the actual executed code from static analysis and is a known technique used to conceal credential harvesting or token exfiltration logic. (location: page-text.txt line 1: eval(decodeURIComponent(`function%20fn%28a%29%7Bwindow.jsToken%20...`)))
credential harvesting
The obfuscated eval block sets window.jsToken to a 128-character hex value. Combined with the brand impersonation of TeraBox (a service requiring login), this pattern is consistent with session token harvesting or injecting a pre-set token to hijack or monitor authentication flows on a fake login page. (location: page-text.txt line 1: fn('5B95C0CEAF14C0945E686EA09C5FF4F3...'))
malicious redirect
The page dynamically appends an external script from teraboxcdn.com CDN with a randomized cache-busting query string (?v=Math.random()). This pattern can be used to load different payloads on each visit, evading caching and static scanning, and could redirect users or load phishing content dynamically. (location: page-text.txt lines 49-53: script.src = 'https://s5.teraboxcdn.com/general-conf/ymg/2068/abclite-2068-s.js?v=' + Math.random())
phishing
nephobox.com impersonates the TeraBox brand (including login flows, app download prompts, and cloud storage interface) while not being the official TeraBox domain (terabox.com). Users arriving at this domain may be deceived into submitting credentials believing they are on the legitimate TeraBox platform. (location: page.html: og:url=https://www.nephobox.com, canonical href=https://www.nephobox.com, title and description match TeraBox official branding)
curl https://api.brin.sh/domain/nephobox.comCommon questions teams ask before deciding whether to use this domain in agent workflows.
nephobox.com currently scores 31/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.