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
A script block labeled 'mng_admiral_script' uses double-nested percent-encoding obfuscation to hide its variable name ('admiral') and dynamically injects an external script from 'thebestpaints.com/static/js/n4t2wvt/pkbuh.module.js' — an entirely unrelated domain with no affiliation to twincities.com or any known ad/analytics vendor. The script is loaded asynchronously and inserted before the first existing script tag. The obfuscation pattern (double decodeURI on split percent-encoded strings) is a hallmark of malicious script injection designed to evade static analysis. (location: page.html line 17, <script id='mng_admiral_script'>)
malicious redirect
An injected script from 'thebestpaints.com/static/js/n4t2wvt/pkbuh.module.js' is loaded into the legitimate twincities.com (Pioneer Press) page. This external domain has no legitimate relationship to the news publisher. Such injections are commonly used to serve malicious redirects, credential harvesting overlays, or drive-by download payloads to site visitors. The script executes with full page context and DOM access. (location: page.html line 17, src='https://thebestpaints.com/static/js/n4t2wvt/pkbuh.module.js')
obfuscated code
A second obfuscated block in the same 'mng_admiral_script' tag uses double-decoded percent encoding to hide references to 'googletag', 'getItem', and a localStorage key ('_aQS02OEVGQTIzNzJFODI0QTAxMTQ4Njc3MUItNzY'). It reads localStorage data and passes it to Google Publisher Tag ad targeting via 'setTargeting'. While ad targeting via localStorage is not inherently malicious, the heavy obfuscation of standard API calls is anomalous and conceals the full scope of data being exfiltrated to the ad network. (location: page.html line 18, second IIFE in <script id='mng_admiral_script'>)
brand impersonation
The page presents as the legitimate Twin Cities Pioneer Press news site (twincities.com, 27-year-old domain, valid TLS, real editorial content). The injected malicious script from thebestpaints.com exploits the brand's trusted reputation — users and AI agents interacting with what appears to be a legitimate news site would not expect malicious script execution. This constitutes weaponized brand trust to deliver a payload. (location: page.html line 17, injected into https://www.twincities.com)
curl https://api.brin.sh/domain/twincities.comCommon questions teams ask before deciding whether to use this domain in agent workflows.
twincities.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.