SearXNG Metasearch

Security checks across malware telemetry and agentic risk

Overview

This is a coherent SearXNG setup and usage guide, with a few configuration choices users should secure before exposing it beyond their own machine.

Before installing, change the placeholder secret key, consider pinning the Docker image version, bind the service to localhost or restrict port 8080 unless remote access is intentional, and raise safe_search if unfiltered results are not appropriate.

SkillSpector

By NVIDIA

Vulnerability Patterns

Data ExfiltrationExternal Transmission, Env Variable Harvesting, File System Enumeration
Prompt InjectionInstruction Override, Hidden Instructions, Exfiltration Commands
Privilege EscalationExcessive Permissions, Sudo/Root Execution, Credential Access
Supply ChainUnpinned Dependencies, External Script Fetching, Obfuscated Code
Excessive AgencyUnrestricted Tool Access, Autonomous Decision Making, Scope Creep

Findings (2)

Missing User Warnings

Medium

Confidence: 96% confidence
Finding: The setup instructs users to bind SearXNG to 0.0.0.0, which exposes the service on all network interfaces rather than localhost only. In the context of a self-hosted search service with a JSON API and no accompanying warning about authentication, firewalling, or reverse-proxy protection, this can unintentionally make the instance reachable by other hosts on the LAN or internet and enable unauthorized use, scraping, or abuse.

Missing User Warnings

Low

Confidence: 84% confidence
Finding: The configuration explicitly sets safe_search: 0, disabling filtering of explicit or potentially unsafe content without warning the user. This is not a system-compromise issue, but it can cause the skill to return NSFW or otherwise inappropriate results unexpectedly, which is more concerning in a general-purpose search skill likely to be used in varied environments.

VirusTotal

66/66 vendors flagged this skill as clean.

View on VirusTotal