Terabytes of passwords leaked from an AI tool – what every small business must do now

Why this breach matters to your business

A recent supply‑chain attack on the open‑source AI helper LiteLLM leaked terabytes of credentials belonging to more than 2,500 organisations, including big names such as Microsoft and Amazon. Even if you never heard of LiteLLM, the lesson is clear: any third‑party AI library you use can become a shortcut for attackers to steal the keys that keep your systems running. If those keys fall into the wrong hands, they can access your cloud accounts, databases, and even your customers’ data.

For a small‑business owner, the risk is simple but real: an unnoticed secret in an AI tool could give a hacker a back‑door into your online store, booking system, or patient records. The good news is that you can act now, with a short checklist, to make sure your secrets are safe.

What happened? A plain‑language look at the supply‑chain breach

A supply‑chain attack is when attackers compromise a piece of software that many other companies rely on. In this case, the attackers injected malicious code into LiteLLM, a library that developers use to add AI capabilities to their applications. When a developer downloaded the compromised version from the official Python Package Index, the hidden code scraped whatever it could find on the machine—API keys, passwords, SSH keys, and other “secrets”—and sent them to the attackers.

The malicious code was active for only 40 minutes in March. During that brief window, any organisation that ran the infected LiteLLM version exposed its credentials. Security firms discovered the leak by analysing a 195 TB data dump that contained:

• Cloud keys – passwords that let you control services like AWS or Azure.
• Repository tokens – keys that give access to your code stored on GitHub or GitLab.
• SSH keys – the “digital keys” that let you log into servers.
• Kubernetes secrets – credentials used by container orchestration platforms.
• Environment variables – hidden values that applications read at runtime, often containing passwords or API keys.

Because the data was collected from continuous‑integration/continuous‑delivery (CI/CD) pipelines, the breach could affect the entire software‑delivery chain of a business, from development to production.

Key concepts explained in plain language

Term	What it means for you
Supply‑chain attack	Hackers compromise a tool you download, giving them indirect access to your systems.
CI/CD pipeline	An automated process that builds, tests and deploys your software. Think of it as a factory line for code.
API key / token	A secret string that lets one program talk to another (e.g., your website talking to a payment gateway).
Secret	Any credential—password, key, token—that should stay hidden.
Rotate credentials	Replace an old secret with a new one, and make sure the old one can no longer be used.

Immediate action checklist – protect your AI‑related tools today

1. Identify every AI library or service you use
   Make a quick inventory. Look at your code repositories, your website plugins, and any third‑party SaaS tools that claim to use AI (e.g., chatbots, image generators, recommendation engines).

2. Check the version
   If you see LiteLLM, verify the version. The compromised releases were 1.82.7 and 1.82.8. Update to the latest safe version or remove the library if you don’t need it.

3. Rotate all secrets
   For every API key, password, or token that the AI tool can access, generate a new one.

   • Cloud provider keys (AWS, Azure, Google Cloud)
   • Database passwords
   • Third‑party service tokens (payment, email, analytics)
   • SSH keys used for server access

4. Enable secret‑management tools
   Use a dedicated secret‑store (e.g., HashiCorp Vault, Azure Key Vault) that keeps secrets out of code and CI/CD variables. Grant access only to the services that truly need them.

5. Add automated secret‑rotation
   Where possible, schedule regular rotation (monthly or quarterly). Many cloud providers offer built‑in rotation for access keys.

6. Audit your CI/CD pipelines

   • Remove any hard‑coded secrets from configuration files.
   • Use environment variables that are injected at runtime, not stored in the repository.
   • Enable “least‑privilege” permissions: give each pipeline only the rights it absolutely needs.

7. Implement monitoring and alerts
   Set up alerts for unusual activity, such as a sudden spike in API calls or login attempts from unknown IP addresses. Tools like CloudTrail (AWS) or Azure Monitor can help.

8. Document the process
   Keep a simple, up‑to‑date checklist (like this one) in a shared location. When a new tool is added, repeat steps 1‑7.

Frequently asked questions

Q: I don’t develop software myself – do I still need to worry?
A: Absolutely. Even if a developer handles the code, the secrets they use belong to your business. If they are leaked, the attacker can access your online store, booking system, or patient portal. Ask your developer or IT partner to run the checklist for you.

Q: How often should I rotate my secrets?
A: At a minimum once every three months, or immediately after any suspected breach. Automated rotation tools make this easier and reduce the risk of human error.

Q: What if I can’t find a secret that might be exposed?
A: Start by revoking all keys for the affected service and generating new ones. Then, gradually re‑enable the ones you know are still needed. This “reset‑and‑re‑enable” approach ensures no hidden key remains active.

How IT Move NL can help

Dealing with secrets across multiple tools can feel overwhelming, especially when you’re focused on serving customers. Our Security & Protection health‑check is a free, no‑obligation review that:

• Audits every AI‑related library and service you use.
• Identifies exposed credentials and any outdated versions.
• Sets up automated secret‑rotation and continuous monitoring tailored to small‑business needs.

Think of it as a friendly security partner that looks over your shoulder, spots the hidden keys, and helps you lock them away. If you’d like us to take a look, just reach out – we’ll schedule a quick call and get you back to running your business with peace of mind.

---

Sources:

• Terabytes of credentials leaked in massive supply-chain attack
• Mythos ran real-life supply chain attack in AI safety body test
• Logistics firm supply chain breach hits Valve and other customers
• ‘Near-autonomous’ AI agents attack Taiwan’s nuclear safety agency