AI Infrastructure Theft: Hackers Resell Computing Power

Criminals Are Monetizing Stolen AI Compute Power: A New Threat Landscape

For years, Chief Information Security Officers (CISOs) have diligently defended against the unauthorized use of their IT infrastructure for cryptocurrency mining. Now, a far more sophisticated and lucrative threat is emerging: the hijacking and resale of access to corporate artificial intelligence (AI) infrastructure. A new report reveals a burgeoning criminal network actively stealing credentials and computational resources, then profiting from their illicit gains.

Researchers at Pillar Security unveiled findings on Wednesday detailing large-scale campaigns targeting exposed large language model (LLM) and Model Context Protocol (MCP) endpoints – often found in seemingly innocuous applications like AI-powered customer support chatbots. This isn’t opportunistic hacking; it’s a fully-fledged business.

“The scale and organization of this activity are deeply concerning,” says Ariel Fogel, co-author of the Pillar Security report. “We’re witnessing a criminal ecosystem where actors are systematically stealing the ability to utilize LLMs and compute power, and then reselling that access on the dark web.”

Eilon Cohen, also a report co-author, emphasizes the urgency. “Depending on your application and the data your LLMs access, you need to act swiftly to mitigate this threat. Protecting your expensive AI resources from unauthorized use is paramount, especially if those resources handle sensitive information.”

Kellman Meghu, Chief Technology Officer at DeepCove Security, warns that this campaign is poised for significant growth, potentially leading to catastrophic consequences. “The ease with which these attacks can be executed is particularly alarming. The technical barrier to entry is surprisingly low.”

Recent data from Pillar Security’s honeypots paints a stark picture: over 35,000 attack sessions targeting exposed AI infrastructure in just the past two weeks. This isn’t a one-time event; it’s a sustained, organized operation.

The motivations behind these attacks are multifaceted. Threat actors aim to steal compute resources for unauthorized LLM inference, resell API access at discounted rates through clandestine marketplaces, exfiltrate sensitive data from LLM context windows and conversation histories, and leverage compromised MCP servers as pivot points to infiltrate internal systems.

Operation Bizarre Bazaar and the Expanding Attack Surface

Pillar Security has identified two primary campaigns: “Operation Bizarre Bazaar,” focused on exploiting unprotected LLMs, and a second campaign targeting Model Context Protocol (MCP) endpoints. The accessibility of these targets is a key factor in the campaigns’ success. Attackers are leveraging readily available tools like the Shodan and Censys IP search engines to identify vulnerable systems.

Organizations at risk include those running self-hosted LLM infrastructure – such as Ollama, vLLM, and local AI implementations – as well as those deploying MCP servers for AI integrations. Specific vulnerabilities include:

  • Exposed endpoints utilizing default ports for common LLM inference services.
  • Unauthenticated API access lacking proper access controls.
  • Development and staging environments with publicly accessible IP addresses.
  • MCP servers connecting LLMs to critical file systems, databases, and internal APIs.

Common misconfigurations that attackers are exploiting include Ollama instances running on port 11434 without authentication, OpenAI-compatible APIs on port 8000 exposed to the internet, MCP servers accessible without access controls, and production chatbot endpoints lacking authentication or rate limiting.

George Gerchow, Chief Security Officer at Bedrock Data, highlights the evolving nature of the threat. “Operation Bizarre Bazaar signifies a shift in attacker behavior. They’re no longer simply experimenting with LLM abuse; they’re treating exposed AI infrastructure as a fully monetizable attack surface. The increasing reliance on the Model Context Protocol (MCP) adds another layer of complexity, as these integration points can become pathways to internal systems if not properly secured.”

Defenders must adopt a security posture comparable to that applied to APIs and databases, prioritizing authentication, telemetry, and proactive threat modeling throughout the development lifecycle. Securing MCP interfaces, not just model access, is now a critical imperative.

The Pillar Security report details three core components of the Bizarre Bazaar campaign:

  • The Scanner: A distributed botnet systematically probes the internet for exposed AI endpoints, cataloging vulnerable Ollama instances, unauthenticated vLLM servers, and accessible MCP endpoints. Exploitation attempts often begin within hours of discovery.
  • The Validator: Once targets are identified, infrastructure linked to a criminal marketplace validates the endpoints through API testing, assessing model capabilities and response quality.
  • The Marketplace: Discounted access to over 30 LLM providers is being sold on a site called The Unified LLM API Gateway, hosted on resilient infrastructure in the Netherlands and promoted on Discord and Telegram.

Early buyers of this access appear to be individuals building their own AI infrastructure to reduce costs, as well as those involved in online gaming. However, the potential for more malicious actors to leverage this access is significant.

The threat extends beyond fully developed applications. Even developers prototyping AI applications, who may inadvertently leave servers unsecured, are vulnerable to credential theft and exploitation.

Joseph Steinberg, a US-based AI and cybersecurity expert, emphasizes that this report underscores the need for new security solutions tailored to the unique risks posed by artificial intelligence. Steinberg argues that traditional IT controls are often insufficient to address these emerging threats.

Do organizations have the in-house expertise to securely deploy and protect AI projects, or should they consider outsourcing to specialized providers? This is a critical question CSOs must address.

Pro Tip: Regularly scan your external-facing infrastructure, including AI endpoints, using vulnerability scanners and penetration testing to identify and remediate potential weaknesses.

Mitigating the Risk: Immediate Steps for Security Teams

Pillar Security recommends the following actions for organizations with externally-facing LLMs and MCP servers:

  • Enable Authentication: Implement robust authentication mechanisms on all LLM endpoints to eliminate opportunistic attacks. Verify that services like Ollama and vLLM require valid credentials for all requests.
  • Audit MCP Server Exposure: Ensure that MCP servers are never directly accessible from the internet. Review firewall rules, cloud security groups, and authentication requirements.
  • Block Malicious Infrastructure: Add the 204.76.203.0/24 subnet to deny lists and block AS135377 ranges for MCP reconnaissance campaigns.
  • Implement Rate Limiting: Deploy Web Application Firewall (WAF) and Content Delivery Network (CDN) rules to mitigate burst exploitation attempts and enforce traffic patterns specific to AI applications.
  • Audit Chatbot Exposure: Secure all customer-facing chatbots, sales assistants, and internal AI agents with appropriate security controls to prevent abuse.

Despite the growing number of reported AI vulnerabilities, abandoning AI development isn’t the answer. Kellman Meghu advocates for a balanced approach: “Don’t ban AI outright; instead, bring it into the light, educate your users about the risks, and empower them to use AI/LLM safely and effectively.”

“Dedicated training on AI usage and risk is now essential. Solicit feedback from users on how they interact with AI services and proactively address their concerns. Ignoring user needs can drive AI adoption into the shadows, creating even greater security risks.”

What new security frameworks will be necessary to adequately protect AI infrastructure? And how can organizations foster a culture of AI security awareness among their employees?

Frequently Asked Questions About AI Infrastructure Security

  • What is LLMjacking and why is it a concern?
    LLMjacking refers to the unauthorized use of large language models (LLMs) by malicious actors, typically to steal compute resources or resell access. It’s a concern because it can lead to financial losses, data breaches, and reputational damage.
  • How can I determine if my LLM endpoints are vulnerable to attack?
    You can use vulnerability scanners and penetration testing to identify exposed endpoints and misconfigurations. Regularly auditing your infrastructure and implementing strong authentication measures are also crucial.
  • What is the Model Context Protocol (MCP) and why is it a target for attackers?
    The Model Context Protocol (MCP) is an emerging standard for securely connecting LLMs to data sources and tools. Attackers target MCP servers because they can provide access to sensitive internal systems.
  • What are some common misconfigurations that attackers exploit in AI infrastructure?
    Common misconfigurations include running Ollama without authentication, exposing OpenAI-compatible APIs to the internet, and leaving MCP servers accessible without access controls.
  • Is outsourcing AI development a viable security strategy?
    Outsourcing AI development to a provider with specialized security expertise can be a viable strategy, particularly if your organization lacks the necessary in-house skills.
  • How can rate limiting help protect against AI infrastructure attacks?
    Rate limiting can prevent attackers from overwhelming your systems with a large number of requests, mitigating the impact of burst exploitation attempts.
  • What role does employee training play in securing AI infrastructure?
    Employee training is crucial for raising awareness about AI security risks and promoting safe usage practices. Educated employees are less likely to fall victim to phishing attacks or inadvertently expose sensitive data.

Share this article with your network to help raise awareness about this critical emerging threat. Join the conversation in the comments below – what steps is your organization taking to secure its AI infrastructure?

Related reading


Discover more from Archyworldys

Subscribe to get the latest posts sent to your email.