Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

175K+ publicly-exposed Ollama AI instances discovered

techradar.com

Post reply on HN
Print view View original

31–40 of 41 posts

Re: 175K+ publicly-exposed Ollama AI instances discovered

#31

Post by vivzkestrel »

driverdan wrote: post #25
vivzkestrel wrote: post #24

- you ll be surprised how many OLLAMA API KEYS [you can find here]( https://github.com/search?q=%22OLLAMA_API_KEY%22&type=code&p... ) its 2026 and this technique still works. I wonder if github supports regex search

I just looked through 2 pages and didn't see any keys, just empty config vars and placeholder values. How many real keys are you actually finding?

well i did not use regex earlier but found some AWS keys https://github.com/search?q=%2F%22AWS_(%5Cw%2B)%22%3D%22(%5C...

these are the same guys that later complain about a 100k$ bill on AWS

also this conversation never happened

Re: 175K+ publicly-exposed Ollama AI instances discovered

#32

Post by [deleted] »

kristopolous wrote: post #26

I tried a few these ... they are pretty slow. If you are looking for free inference you'd have to be pretty desperate. example: $ OLLAMA_HOST= http://47.101.61.248:9000/ ollama run gemma3:27b "outline ww2" Many appear to be proxies. I'm familiar with some "serverless" architectures that do things like this https://www.shodan.io/host/34.255.41.58 ... you can see this has a bunch of ollama ports running really really o…

[deleted]

Re: 175K+ publicly-exposed Ollama AI instances discovered

#33

Post by cyberax »

threecheese wrote: post #7
meltyness wrote: post #6

This is a weakness of docker, a bit, I think. I was rigging this up, myself, and conciscious of the fact that basic docker is "all or none" for container port forwarding because it's for presenting network services, had to dig around with iptables so it'd be similar to binding on localhost. The use case https://github.com/meltyness/tax-pal The ollama container is fairly easy to deploy, and supports GPU inference thro…

Out of curiosity, why would you need to wrap the call to an Ollama modelfile in docker? Does the dockerized ollama client provide some benefit, when it’s shelling down to local Ollama instance anyway? (Wrt tax-pal)

I'm using open-webui project to host a Web UI for Ollama, and Ollama itself in Docker containers. It's super-useful, because I don't have to worry about it blowing up stuff on my system with automatic installations.

Re: 175K+ publicly-exposed Ollama AI instances discovered

#34

Post by chrisjj »

crimsonnoodle58 wrote: post #9
chrisjj wrote: post #4

Earlier quoted context omitted.

The article says no, the default is listening to just localhost. Given the instances in question have been deliberately configured to listen on public ports, calling this misconfiguration seems somewhat unjustified.

Not true for their docker instructions which specify -p 11434:11434 instead of -p 127.0.0.1:11434:11434. [1] Combine that with rootful docker's famous bypass of ufw and you have a publicly exposed ollama, even with a firewall. [2] [1] https://docs.ollama.com/docker [2] https://github.com/moby/moby/issues/4737

Ouch. Thanks.

Re: 175K+ publicly-exposed Ollama AI instances discovered

#35

Post by Tiberium »

vivzkestrel wrote: post #31
driverdan wrote: post #25

Earlier quoted context omitted.

I just looked through 2 pages and didn't see any keys, just empty config vars and placeholder values. How many real keys are you actually finding?

well i did not use regex earlier but found some AWS keys https://github.com/search?q=%2F%22AWS_(%5Cw%2B)%22%3D%22(%5C... these are the same guys that later complain about a 100k$ bill on AWS also this conversation never happened

GitHub sends those keys to Amazon which automatically quarantines them

Re: 175K+ publicly-exposed Ollama AI instances discovered

#36

Post by thehamkercat »

kristopolous wrote: post #26

I tried a few these ... they are pretty slow. If you are looking for free inference you'd have to be pretty desperate. example: $ OLLAMA_HOST= http://47.101.61.248:9000/ ollama run gemma3:27b "outline ww2" Many appear to be proxies. I'm familiar with some "serverless" architectures that do things like this https://www.shodan.io/host/34.255.41.58 ... you can see this has a bunch of ollama ports running really really o…

If someone is that desperate looking for free inference, or just for fun openrouter has many free models

Re: 175K+ publicly-exposed Ollama AI instances discovered

#37

Post by Imustaskforhelp »

thehamkercat wrote: post #36
kristopolous wrote: post #26

I tried a few these ... they are pretty slow. If you are looking for free inference you'd have to be pretty desperate. example: $ OLLAMA_HOST= http://47.101.61.248:9000/ ollama run gemma3:27b "outline ww2" Many appear to be proxies. I'm familiar with some "serverless" architectures that do things like this https://www.shodan.io/host/34.255.41.58 ... you can see this has a bunch of ollama ports running really really o…

If someone is that desperate looking for free inference, or just for fun openrouter has many free models

Arcee AI is currently free on openrouter with some really great speeds and no logs/traning from what I can tell while being completely free till end of feb and its a 500B model.

There are tons of free inference models. I treid to use gemini flash in aistudio + devstral free for agentic tasks but its now deprecated but when it wasn't, it was a really good setup imo. Now I can use arcee but personally ended up buying a 1 month cheap subscription of kimi after haggling it from 19.99 to 1.49$ for first month (could've haggled more too leading to 0.99$ too but yeaaa)

Re: 175K+ publicly-exposed Ollama AI instances discovered

#38

Post by throw20251220 »

cyberax wrote: post #33
threecheese wrote: post #7

Earlier quoted context omitted.

Out of curiosity, why would you need to wrap the call to an Ollama modelfile in docker? Does the dockerized ollama client provide some benefit, when it’s shelling down to local Ollama instance anyway? (Wrt tax-pal)

I'm using open-webui project to host a Web UI for Ollama, and Ollama itself in Docker containers. It's super-useful, because I don't have to worry about it blowing up stuff on my system with automatic installations.

You work with Linux. On a mac, you run ollama on the host because the gpu is not available in the container.

Re: 175K+ publicly-exposed Ollama AI instances discovered

#39

Post by throwaway314155 »

Zambyte wrote: post #22
throwaway314155 wrote: post #13

Earlier quoted context omitted.

How exactly are the ports "exposed" if they can't be bound to an interface?

Binding to 0.0.0.0 means binding to every interface.

That bit hadn’t been edited in when I wrote my comment.

Re: 175K+ publicly-exposed Ollama AI instances discovered

#40

Post by threecheese »

meltyness wrote: post #8
threecheese wrote: post #7

Earlier quoted context omitted.

Out of curiosity, why would you need to wrap the call to an Ollama modelfile in docker? Does the dockerized ollama client provide some benefit, when it’s shelling down to local Ollama instance anyway? (Wrt tax-pal)

It's more of a distribution thing for me really. I'm basically using docker as a package manager since they otherwise distribute through one of those ad-hoc shell scripts that I'd prefer to avoid accidentally breaking Debian with somehow. I've built ollama before too, but, I like that I can cleanly rip it out of my system or upgrade it without handing root off to some shell script somewhere I guess. If anyone's gonna…

Makes sense, thank you!
Post reply on HN