context safety score
A score of 33/100 indicates multiple risk signals were detected. This entity shows patterns commonly associated with malicious intent.
malicious redirect
script/meta redirect patterns detected in page source
brand impersonation
The site 1377x.to impersonates the well-known torrent index 1337x.to. The domain 1377x.to is a typosquat of 1337x.to (transposing '3' and '7'), using the same site title, layout, branding, logo, and content to deceive users into believing they are on the legitimate 1337x.to site. (location: <title> tag and page content: '1377x | Download torrents | 1337x.to | 1377x.to')
malicious redirect
The page promotes 'alternative domains' and links to 1337xto.to, redirecting users away from any legitimate destination to potentially other typosquat or malicious domains. This creates a chain of redirects through impersonator domains. (location: page.html line 110: <a href="https://1337xto.to">1337xto.to</a>)
hidden content
A Histats.com web analytics tracker is embedded inside a hidden div (display:none), silently collecting visitor data including IP addresses and browsing behavior without user visibility or consent disclosure. (location: page.html lines 241-253: <div style="display:none"><!-- Histats.com --></div>)
hidden content
A 1x1 pixel hidden iframe is dynamically injected via obfuscated JavaScript (Cloudflare challenge script), positioned absolutely at top-left with visibility:hidden. While possibly a Cloudflare bot-check mechanism, the obfuscated inline script creating a hidden iframe is a common vector for covert tracking or payload delivery. (location: page.html line 254: iframe with height=1, width=1, style position absolute, visibility hidden)
obfuscated code
An external script is loaded from the suspicious third-party domain ancientmurine.com (//ey.ancientmurine.com/rgROG7nRWch/VqkjQ). The domain name and randomized path are characteristic of malvertising or adware networks. This script is loaded asynchronously with data-cfasync=false to bypass Cloudflare scanning. (location: page.html line 254: <script data-cfasync="false" async src="//ey.ancientmurine.com/rgROG7nRWch/VqkjQ">)
social engineering
The site presents itself as a trusted torrent community offering login, registration, and upload functionality, mimicking the UX of the legitimate 1337x.to to build false trust and encourage credential submission by deceived users. (location: page.html lines 38-39: Register and Login navigation links on a brand-impersonating site)
curl https://api.brin.sh/domain/1377x.toCommon questions teams ask before deciding whether to use this domain in agent workflows.
1377x.to currently scores 33/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.