context safety score
A score of 42/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
js obfuscation
JavaScript uses Function constructor for runtime code generation
prompt injection
Hidden HTML element contains AI-targeting instructions
malicious redirect
An open redirect vulnerability exists in a script at the bottom of the page body. The script reads a URL-encoded value from the query parameter 'page' (?page=...), decodes it with decodeURIComponent, and redirects the browser unconditionally via window.location.href = decodedUrl. The only guard checks if the decoded URL contains 'accessnewswire.com' to add a 'www.' prefix, but it does NOT restrict the redirect to the same domain. An attacker can supply any arbitrary external URL (e.g., ?page=https://evil.com) and the script will redirect the visitor there, enabling phishing, credential harvesting, and drive-by-download attacks. (location: page.html:3648-3669)
social engineering
A modal popup ('We've got your back!') is triggered after the user scrolls 500px. It uses a Marketo form that collects business email addresses and explicitly rejects Gmail addresses. While technically standard marketing, the popup is scroll-triggered and appears without user initiation, pressuring visitors to submit contact details. The form submits to //gomq.accessnewswire.com (a subdomain), and on success stores a 'subscribed' flag in localStorage to suppress future display — a pattern that can suppress detection on repeated visits by security scanners. (location: page.html:2539-2632)
hidden content
An HTML comment block near line 1193 contains a commented-out script block that configures a 'SAChatWidgetConfig' with an agentId. This dead code is immediately followed by a Reddit Pixel comment marker, suggesting the comment delimiter was intentionally malformed or the block was left partially visible. The chatbot agent configuration (agentId: 'vjmnmwww') embedded inside a broken comment could be an attempt to conditionally activate an AI chat agent without full disclosure. (location: page.html:1193-1201)
hidden content
Excessive whitespace padding is present throughout inline script blocks in the HTML, spanning dozens of blank lines between short functional code segments (e.g., lines 757-851, 860-928, 940-1006). This pattern is consistent with whitespace obfuscation to push visible content far apart and complicate static analysis or diff-based review. (location: page.html:755-1006)
curl https://api.brin.sh/domain/accessnewswire.comCommon questions teams ask before deciding whether to use this domain in agent workflows.
accessnewswire.com currently scores 42/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.