context safety score
A score of 38/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
malicious redirect
JavaScript code checks if the user is on rutor.is or rutor.info and silently redirects them to http://6tor.org via a JSONP callback. The redirect is triggered without user consent based on an IPv6 probe to an external domain, replacing the current host with 6tor.org. This is a covert, script-driven redirect to a third-party domain. (location: page.html:75-80)
obfuscated code
A deferred script loader uses a randomized interval polling loop to check for a geolocation variable (ec592524fc_country) set by an external script, then dynamically injects a script from a domain stored in ec592524fc_domain (not defined in-page, set by a prior external script). The variable name ec592524fc is an obfuscated identifier. The injected script path '/bens/vinos.js' with numeric ID parameter suggests ad-fraud, malware delivery, or tracking payload. The data-cfasync='false' attribute bypasses Cloudflare bot protection. (location: page.html:494-516)
malicious redirect
External script loaded from deltarockme.com at page body open: <script src='https://deltarockme.com/services/?id=144655'>. This is an unknown third-party domain injecting executable JavaScript with a numeric campaign ID, consistent with malvertising or drive-by download infrastructure. Loaded synchronously at body start, giving it full DOM access before page renders. (location: page.html:14)
obfuscated code
External script loaded from vak345.com (/s.js?v=ea59f7a89d04d570fbb4ef98a8a1693c) with a long hex fingerprint parameter. vak345.com is an unrecognized domain with a fingerprint-style query string, consistent with tracking/analytics obfuscation or payload delivery. Loaded async at page bottom. (location: page.html:518)
hidden content
A LiveInternet analytics counter script is wrapped in HTML comment tags (<!-- ... -->) to hide it from casual HTML inspection while still executing in browsers that process script blocks. The counter beacon exfiltrates the full document.URL and document.referrer to counter.yadro.ru, a Russian analytics service, without any user disclosure. (location: page.html:473-481)
malicious redirect
The cookie-based message injection block reads a cookie named 'msg' and injects its raw value directly into the DOM via .html(), with only a weak replace of quote characters. This is a stored XSS vector: if the 'msg' cookie is set by a malicious script (e.g., from deltarockme.com or 6tor.org), it can inject arbitrary HTML/JS into the page. (location: page.html:83-95)
social engineering
The site openly distributes cracked/repack versions of commercial software (VMware Workstation Pro, Internet Download Manager, Telegram Desktop, Half-Life: Alyx, Assassin's Creed Mirage, Resident Evil 2, etc.) as torrents. These repacked executables are a common vector for bundled malware, keyloggers, and trojans targeting users who believe they are downloading legitimate software. (location: page.html:283-291, page-text.txt:271-280)
curl https://api.brin.sh/domain/rutor.infoCommon questions teams ask before deciding whether to use this domain in agent workflows.
rutor.info currently scores 38/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.