Risks AI tool supply chain

High

High: attackers have taken over real internet-facing AI servers for mining and further attacks, and it applies to organizations that run their own AI servers. How we rate severity

Exposed AI infrastructure: internet-facing AI servers hijacked for mining and scanning

Two research teams report campaigns taking over internet-exposed AI servers for cryptomining and further attacks. Put AI tools in your attack-surface inventory.

What happened

Two research reports describe attackers taking over exposed AI infrastructure, meaning AI servers and tools that can be reached from the internet.

On November 18, 2025, Oligo Security reported an active campaign it calls ShadowRay 2.0. It exploits CVE-2023-48022 in Ray, an open-source framework for running AI workloads, which Oligo says allows unauthenticated remote code execution through Ray’s Jobs API. Oligo notes the flaw is “disputed” because Ray’s maintainers say Ray isn’t intended for use outside a “strictly-controlled network environment,” and it says there is no specific version to upgrade to. Oligo reports that attackers turned exposed clusters into a self-spreading cryptomining botnet, and says its analysis shows they “leveraged LLM-generated payloads.” It says the attackers capped CPU use at about 60% to avoid detection, and that “evidence suggests” the operation could have been active since September 2024. The report gives figures of both “more than 230,000” and “over 200,000” Ray servers exposed to the internet. Oligo says the campaign is unrelated to the paid products of Anyscale, the company that develops Ray.

On October 7, 2026, Lumen’s Black Lotus Labs described PoeLLM, malware it has tracked since April 2026. Lumen says most victims “appear to be running vulnerable versions of open-source AI/LLM services, such as LiteLLM and Ollama.” It says the malware installs cryptocurrency miners and turns infected servers into scanners and exploit servers to find more victims. Lumen says the malware has impacted “more than 3,400 victim servers,” with peak activity “exceeding 800 active servers per day.” Elsewhere it says the campaign involved “almost 2,200 affected servers” at its mid-June peak, “with nearly 800 active per day.”

Why it matters to leaders (our analysis)

Lumen notes that as AI infrastructure grows, “new tools often go unmonitored for vulnerabilities despite access to powerful compute and valuable enterprise data.” Both reports point to the same result: servers with valuable compute and data, reachable from the internet, that attackers can find and use automatically. In Ray’s case, the maintainers’ position is that security has to be enforced around the cluster, so exposure is a deployment decision rather than something a patch fixes.

The response is ordinary attack-surface management applied to a newer class of system: know what you expose, put authentication and network controls in front of it, and watch for compute you didn’t schedule.

What to tell your board

Internet-facing AI servers are being taken over and misused, so we are adding them to our asset inventory, requiring sign-in for every AI service, and patching them promptly.

What your board will ask

  1. Do we know every AI server, model host, and AI gateway we run that can be reached from the internet?
  2. Who set those systems up, and were they reviewed like other internet-facing services?
  3. Which of them hold credentials, data, or expensive GPU capacity an attacker would want?
  4. Would we notice if one of our AI servers started mining cryptocurrency or scanning other networks?

Controls that help

  • Add AI compute clusters, model servers, and AI gateways to the external attack-surface inventory, and scan for them regularly. NIST CSF 2.0 — ID.AM
  • Keep AI frameworks that aren't designed for public exposure on private networks, and require authentication in front of every AI service. ISO/IEC 27001:2022 A.8.22 Segregation of networks
  • Patch internet-facing AI services quickly, and retire unused test deployments. ISO/IEC 27001:2022 A.8.8 Management of technical vulnerabilities
  • Monitor AI hosts for unexpected CPU or GPU use, new outbound connections, and scanning activity. NIST CSF 2.0 — DE.CM

Sources

  1. ShadowRay 2.0: Attackers Turn AI Against Itself in Global Campaign that Hijacks AI Into Self-Propagating Botnet — Oligo Security · Nov 18, 2025
  2. Canto incognito: tracking the PoeLLM malware — Lumen Black Lotus Labs · Oct 7, 2026

Published Oct 17, 2026 · Last updated Oct 17, 2026

Change log

  • Oct 17, 2026. First published.

All AI tool supply chain risks

ModelsOther systems

Coming soon

The weekly AI security briefing

The five AI risks security leaders should know, with the questions your board will ask. Signups open soon.

Signups open soon. We'll never share your email. See our Privacy Policy. Privacy Policy

Sponsored

Your logo here: sponsor us →