context safety score
A score of 47/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
credential harvesting
The page contains an inline login form (username/password fields) that submits via POST to login.php. The site uses a .to TLD (Tonga ccTLD) rather than the well-known .me domain (nnm-club.me), suggesting this may be an alternate/mirror domain collecting credentials. The form action is relative (login.php) and operates under the nnmclub.to domain rather than the canonical nnm-club.me. (location: page.html:215-228, <form method='post' action='login.php'>)
brand impersonation
The site presents itself as 'NNM-Club' (Russian torrent tracker) but operates on the domain nnmclub.to rather than the established nnm-club.me. The HTML references assets from nnmstatic.win, Yandex interaction URLs pointing to nnm-club.me, and Google Analytics configured for domain 'nnm-club.me' (UA-1886062-1), while the page canonical URL is nnmclub.to. This domain discrepancy indicates either a mirror or impersonation of the original brand. (location: page.html:8, 17-18, 1040 — base href nnmclub.to/forum, canonical nnmclub.to, GA domain nnm-club.me)
malicious redirect
A dynamically injected script loads an ad/tracking resource from nnmstatic.win at a path with a fingerprinted filename (eb927f21fc.2407b.js) appended with Math.random(). This pattern of dynamically appending a script element at runtime with a cache-busting random query string is commonly used to load obfuscated or rotating payloads that evade static analysis. (location: page.html:974-983, script src='https://nnmstatic.win/forum/ads/eb927f21fc.2407b.js')
hidden content
Several data values are embedded in hidden spans with display:none, including vote ratings (VR) and vote counts (VC) for torrent entries. While likely functional UI state, these hidden numeric values are injected into the DOM invisibly and could be used to pass data to scripts without user visibility. (location: page.html:390-391, 464-466, 491-493, and multiple similar patterns throughout)
hidden content
A commented-out HTML block exists containing an April Fools div with an image reference and Russian text, as well as a commented-out external pixel tracker (<img src='http://maxplan.ru:40001/px.jpg' style='display:none;'>). The pixel tracker uses plain HTTP (not HTTPS) and an unusual port (40001), indicating a potential tracking beacon from a third-party server. (location: page.html:1016-1020, 1051 — <!--<img src='http://maxplan.ru:40001/px.jpg' style='display:none;'>-->)
social engineering
The site distributes pirated commercial software (VueScan Pro, YT Downloader, OCCT, Shotcut repacks, game repacks) via torrent. Repackaged software from unofficial sources is a common vector for bundled malware. Users are encouraged to download executable repacks from third-party packagers (elchupacabra, SE7EN, Let'sPlay) whose integrity cannot be verified from the page alone. (location: page.html:589-968, torrent listings for VueScan Pro RePack, YT Downloader RePack, game Repacks)
curl https://api.brin.sh/domain/nnmclub.toCommon questions teams ask before deciding whether to use this domain in agent workflows.
nnmclub.to currently scores 47/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.