Splunk

Ollama Abnormal Network Connectivity

Last updated 2 days ago on 2026-11-21

About

Detects repeated Ollama warning-level network errors, such as DNS lookup failures, TCP connection issues, or host resolution problems. These events can indicate a connectivity issue and warrant investigation, but do not by themselves establish unauthorized access or reconnaissance.
Platform
Splunk
Tags
Data Source: SplunkDomain: ApplicationRule Type: QueryOS: Any
Severity
medium
Risk Score
47
References
https://github.com/rosplk/ta-ollama(external, opens in a new tab or window)
False Positives
Legitimate remote access from authorized users or applications connecting from non-localhost addresses, temporary network infrastructure issues causing DNS resolution failures, firewall or network configuration changes resulting in connection timeouts, cloud-hosted Ollama instances receiving valid external API requests, or intermittent connectivity problems during network maintenance may trigger this detection during normal operations.
Source
View on GitHub(external, opens in a new tab or window)

Definition

Rule Language
SPL
Rule Type
query
text code block:
`ollama_server` level=WARN msg IN ( "*connection*", "*dial tcp*", "*failed*", "*lookup*", "*network*", "*no such host*", "*refused*", "*timeout*", "*unreachable*" ) | eval dest=coalesce(dest, host) | bin _time span=5m | stats count as incidents values(msg) as warning_messages latest(_time) as last_incident by _time dest | where incidents > 3 | eval last_incident=strftime(last_incident, "%Y-%m-%d %H:%M:%S") | eval severity="medium" | eval attack_type="Abnormal Network Connectivity" | table last_incident dest incidents warning_messages severity attack_type | `ollama_abnormal_network_connectivity_filter`

View this rule on Splunk

This rule was sourced from the official Splunk public repository. View the original rule on GitHub(external, opens in a new tab or window).