Tuesday, August 11, 2026
LIVEThe Unrelenting Cyber Battle: Hacking Threats and the Imperative of Robust Data Protection///Navigating the Cyber Labyrinth: Bolstering Defenses Against Evolving Hacking Threats///The Dual Front War: Battling Hacking and Bolstering Data Protection in the Digital Age///The Ever-Evolving Cyber Threat Landscape: Navigating Hacking and Fortifying Data Protection///The Unseen Battle: Fortifying Data in an Age of Relentless Hacking///The Unseen War: Hacking's Relentless Advance and the Imperative of Data Protection///The Evolving Threat Landscape: Hacking, Data Protection, and the Imperative for Proactive Security///Navigating the Digital Minefield: Bolstering Data Protection in an Era of Relentless Hacking///The Dual Fronts of Digital Defense: Combating Hacking and Fortifying Data Protection///Hacking's New Frontier: Fortifying Data Protection in the Age of Advanced Cyber Threats///The Dual Front: Navigating Hacking Threats and Fortifying Data Protection in the Digital Age///Navigating the Digital Gauntlet: The Evolving Nexus of Hacking and Data Protection///The Unrelenting Cyber Battle: Hacking Threats and the Imperative of Robust Data Protection///Navigating the Cyber Labyrinth: Bolstering Defenses Against Evolving Hacking Threats///The Dual Front War: Battling Hacking and Bolstering Data Protection in the Digital Age///The Ever-Evolving Cyber Threat Landscape: Navigating Hacking and Fortifying Data Protection///The Unseen Battle: Fortifying Data in an Age of Relentless Hacking///The Unseen War: Hacking's Relentless Advance and the Imperative of Data Protection///The Evolving Threat Landscape: Hacking, Data Protection, and the Imperative for Proactive Security///Navigating the Digital Minefield: Bolstering Data Protection in an Era of Relentless Hacking///The Dual Fronts of Digital Defense: Combating Hacking and Fortifying Data Protection///Hacking's New Frontier: Fortifying Data Protection in the Age of Advanced Cyber Threats///The Dual Front: Navigating Hacking Threats and Fortifying Data Protection in the Digital Age///Navigating the Digital Gauntlet: The Evolving Nexus of Hacking and Data Protection///
Subscribe
Cyber Security
Independent · Digital
Thehackingpost
CybersecurityAI-assisted

Over 1,100 Ollama AI Servers Found Online, 20% at Risk

Recent investigations have identified more than 1,100 instances of Ollama, a framework for running large language models (LLMs) locally, accessible on the public internet. Approximately 20% of these instances are hosting vulnerable models, posing…

Recent investigations have identified more than 1,100 instances of Ollama, a framework for running large language models (LLMs) locally, accessible on the public internet. Approximately 20% of these instances are hosting vulnerable models, posing significant risks of exploitation by unauthorized entities.

Cisco Talos researchers conducted a rapid Shodan scan, uncovering 1,140 internet-facing Ollama endpoints. Of these, around 228 lacked necessary access controls or authentication mechanisms, exposing them to potential adversaries. This exposure allows attackers to query models, extract sensitive metadata, reverse-engineer model weights, or inject malicious code. Such vulnerabilities threaten intellectual property, infrastructure integrity, and user privacy.

Publicly accessible Ollama instances present several security risks:

Model Extraction: Adversaries can approximate internal model weights by querying the LLM API, compromising competitive advantages and exposing confidential data. Jailbreaking and Malicious Content Generation: Models such as GPT-4 or LLaMA variants can be manipulated to produce harmful outputs without enforced guardrails. Backdoor Injection and Model Poisoning: Vulnerable APIs may allow unauthorized model alterations, enabling attackers to implant backdoors or modify model behavior.

Although 80% of the identified servers were inactive, they remain exploitable due to outdated patches and potential vulnerabilities. These servers can be targeted through Denial of Service (DoS) attacks, configuration tampering, or loading malicious model assets. Leaked metadata can also aid attackers in broader infrastructure breaches.

Approximately 20% of these instances are hosting vulnerable models, posing significant risks of exploitation by unauthorized entities.
Kyle Mercer · Thehackingpost

Geographical Distribution and Challenges

The United States hosts the largest share of exposed Ollama servers (36.6%), followed by China (22.5%) and Germany (8.9%). This reflects a global trend of deploying LLMs without adhering to essential cybersecurity practices such as perimeter isolation, authentication enforcement, and incident response planning.

Ollama deployments frequently occur outside traditional IT governance, bypassing security audits and oversight. The prevalence of OpenAI-compatible APIs increases risks, enabling threat actors to scale attacks across platforms with minimal modifications.

Cisco Talos suggests several corrective measures:

Advertisement

Establish Security Standards: Develop and adopt industry-wide guidelines for LLM deployment, including access controls, encryption, and continuous monitoring. Automate Auditing: Utilize automated tools to detect misconfigurations, missing authentication, and exposed endpoints. Implement Detailed Deployment Playbooks: Provide best practices for secure local hosting of LLMs, focusing on network segmentation, API throttling, and robust default configurations.

Moreover, Cisco emphasizes that Shodan scans provide only a partial view of the AI threat landscape. To ensure comprehensive security, new scanning methodologies should be developed, including adaptive server identification and active probing of alternative frameworks like Hugging Face, Triton, and vLLM. Enhanced visibility is crucial to protect AI infrastructures from increasingly sophisticated adversaries.

Based on reporting by GBHackers.

AI transparency. This article was produced with the assistance of artificial intelligence and published under human editorial oversight. AI systems can make mistakes. Read how we use AI (EU AI Act, Art. 50).
Related Stories