context safety score
A score of 37/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
phishing
1 deceptive links where visible host does not match destination host
cloaking
Page loads content in transparent or zero-size iframe overlay
obfuscated code
The mng_admiral_script block uses double-encoded URI obfuscation (decodeURI(decodeURI(...))) to conceal the variable name 'admiral' and then dynamically injects an external script from thebestpaints.com — a domain entirely unrelated to ocregister.com. The obfuscation is layered (%25%36%31%64%256d%2569r%2561%25%36c decodes to 'admiral') and is specifically designed to evade static pattern matching. This technique is commonly used to hide malicious or unauthorized third-party script injection. (location: page.html, line 17, script id='mng_admiral_script')
malicious redirect
A script is dynamically loaded from https://thebestpaints.com/j/k8mi18z8dzn8.app.js — an unrelated third-party domain injected into the page of a major news site via obfuscated JavaScript. This external script has full DOM access and could perform redirects, credential harvesting, or other malicious actions. The domain name (thebestpaints.com) has no apparent relationship to the OC Register or its ad/analytics vendors. (location: page.html, line 17, A.src='https://thebestpaints.com/j/k8mi18z8dzn8.app.js')
obfuscated code
The second statement in mng_admiral_script uses double-encoded URI obfuscation to reference 'googletag' and a long obfuscated localStorage key string. The obfuscated key (_a + decodeURI(decodeURI('%51S%25%330%2532...'))) is used to read targeting data from localStorage and pass it to Google Ad Manager pubads(). While the googletag integration may be legitimate, the extreme obfuscation of the localStorage key name is anomalous and obscures what data is being read and exfiltrated. (location: page.html, line 18, script id='mng_admiral_script')
curl https://api.brin.sh/domain/ocregister.comCommon questions teams ask before deciding whether to use this domain in agent workflows.
ocregister.com currently scores 37/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.