context safety score
A score of 24/100 indicates multiple risk signals were detected. This entity shows patterns commonly associated with malicious intent.
cloaking
page appears to serve substantially different content by user-agent
obfuscated code
Script uses String.fromCharCode() to obfuscate variable names and a third-party script URL. Decoded: variable 'push_url' and 'wpnConfig' are constructed character-by-character, then a remote script at 'https://tuhesok.com/58854.js' is dynamically loaded. This pattern is used to hide malicious push-notification or ad-injection payloads from static scanners. (location: page.html:833-852)
malicious redirect
An obfuscated script block dynamically injects an external script from 'https://tuhesok.com/58854.js' with mode 'strict_native' and utm_campaign=342805. The domain 'tuhesok.com' is an unrecognized third-party ad/push network. Combined with the obfuscation, this is a strong indicator of a drive-by redirect or push-notification abuse campaign targeting visitors. (location: page.html:833-852)
malicious redirect
A second third-party script is loaded from '//rkgwzfwjgk.com/i/npage/1861886/code.js' — a randomly-named domain consistent with ad-fraud or malvertising infrastructure. It is injected into a hidden div ('fmfg46f9f7ff1068') and loaded asynchronously with data-cfasync=false to bypass Cloudflare bot protection. (location: page.html:1096)
hidden content
The canonical URL and home link in the page head point to 'https://ru.obmenvsems.com/' — a different domain than the actual site 'obmenvsem.cc'. This cross-domain canonical tag may be used to transfer SEO authority to a related but distinct domain, and indicates the .cc domain is a shadow/redirect copy of another site. (location: page.html:22-23)
hidden content
Yandex Metrika noscript tracking pixel is positioned off-screen at 'left:-9999px' to silently track users even when JavaScript is disabled, without any visible disclosure to the user. (location: page.html:1128)
obfuscated code
The 'show_ads' function in the inline script uses dynamically created DOM elements and references hidden div IDs ('fmfg28d8589f480f', 'fmfg46f9f7ff1068') with randomized-looking names, which is a common technique to evade content security policy scanners and ad blockers when injecting third-party ad content. (location: page.html:830)
social engineering
The site presents itself as a legitimate Russian-language file-sharing portal (WAP file exchanger) and claims to be 'a new address for the former sasisa.org exchanger', which may be used to lure users familiar with the original service into trusting this domain, while actually running ad-injection and push-notification abuse scripts in the background. (location: page.html:1057-1064, page-text.txt:202-207)
curl https://api.brin.sh/domain/obmenvsem.ccCommon questions teams ask before deciding whether to use this domain in agent workflows.
obmenvsem.cc currently scores 24/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.