context safety score
A score of 40/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
js obfuscation
JavaScript uses Function constructor for runtime code generation
social engineering
Site uses pervasive fear-based and urgency-laden headlines to manipulate readers into emotional responses and drive engagement, product purchases, and newsletter signups. Headlines include 'We Must Now Prepare for the Possibility of Nuclear War and Total Supply Chain Collapse', 'The Unthinkable Is Imminent: Why I Believe a Radiological False Flag Is Being Prepared for American Soil', 'HIGH RISK of Radiological False Flag Attack in CONUS', and 'The Apocalypse Pantry: Grow your own pharmacy before the supply chain collapses'. This fear-amplification pattern is directly linked to commercial upselling of survival/prepping products via the Health Ranger Store. (location: page.html:308-334, page-text.txt:174-199, 513-518)
social engineering
Email newsletter signup forms (form IDs _form_172_ and _form_98_) use urgency framing ('Get 100% real, uncensored news delivered straight to your inbox', 'Subscribe Today') combined with distrust-of-mainstream-media rhetoric throughout the site to pressure users into surrendering email addresses. The forms submit to healthrangerstore.activehosted.com, a third-party CRM platform, which users may not be aware of. (location: page-text.txt:1660-1662, 2341, page.html (form submission to healthrangerstore.activehosted.com))
hidden content
Article preview descriptions in category sections (Clean Food, Politics, Culture, Health & Medicine, Prepping & Survival, Finance & Economy) contain injected text from an unrelated article ('China is rapidly building advanced nuclear submarines. This new fleet can target the U.S. from Chinese coastal waters.') as the description snippet for articles that have no thematic connection to that content (e.g., fiber/grains article, hemp seeds, fermented cabbage). This appears to be a content injection anomaly or template bug where one article's body text is being incorrectly populated as the description for multiple unrelated articles, creating misleading context for users and potentially for AI content scrapers. (location: page.html:1253-1286, 1326-1357; page-text.txt:1119-1152)
prompt injection
The page embeds an AI chatbox interface (BrightAnswers.ai widget) directly on the homepage with an open free-text prompt input. The surrounding editorial content is saturated with conspiratorial and politically charged narratives (radiological false flags, deep state, bioweapons cover-ups). Any AI agent crawling this page would ingest this adversarial framing alongside the AI widget, creating conditions for prompt-context poisoning. The widget loads external JS from brightanswers.ai and the AI.js script from the site's own theme, with no visible input sanitization described. (location: page.html:845-861, lines 45-46 (AI.css, AI.js))
social engineering
Affiliate tracking links to the Health Ranger Store are embedded throughout the page using referral parameters (rfsn=, utm_source=HR_Affiliate, utm_campaign=, utm_affiliate=). The site conflates editorial health content with commercial product promotion without clear disclosure, constituting deceptive commercial social engineering. Users (and AI agents summarizing content) may not distinguish between editorial health advice and affiliate-driven product placement. (location: page.html:247, 692, 696, 702)
hidden content
CSS style definitions are rendered as visible plain text in the page-text.txt output (lines 422-437), indicating style blocks are not properly scoped and their content leaks into the text layer. While this is likely a rendering artifact, it means CSS content (including class behavior and link color definitions) is exposed as readable text to scrapers and AI agents processing the text layer. (location: page-text.txt:422-437)
social engineering
The site lists a raw backup IP address (http://45.89.97.6) in the footer as an explicit fallback access point, framed under an 'Onion Site' and censorship-resistance narrative. This pattern is used to condition users to bypass normal DNS resolution and trust direct-IP access, which reduces security indicators users would normally rely on to verify site authenticity. (location: page-text.txt:2151)
curl https://api.brin.sh/domain/naturalnews.comCommon questions teams ask before deciding whether to use this domain in agent workflows.
naturalnews.com currently scores 40/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.