What AI security looks when it doesn't work:
https://www.reddit.com/r/LocalLLaMA/comments/1s2fch0/developing_situation_litellm_compromised/
The thing is that downside potential is way bigger than upside. The most recent example of things going bad is here:
In March 2026, the popular AI tool LiteLLM (used by millions to connect different AI models) was hit by a major security breach. This wasn't a standard "hack" into their servers; it was a supply chain attack that turned a security tool into a weapon.
Here is a breakdown of what happened, how their security tools failed, and the role of "OpenClaw."
1. What actually happened?
On March 24, 2026, two "poisoned" versions of LiteLLM (1.82.7 and 1.82.8) were uploaded to PyPI (the official Python package library). Anyone who downloaded or updated LiteLLM during a roughly three-hour window unknowingly installed a credential stealer.
- The Payload: The malware was designed to quietly steal API keys (OpenAI, Anthropic), cloud passwords (AWS, Azure), and SSH keys.
- The "Fork Bomb": The hack was only discovered because the attackers made a mistake. Their malicious code caused an infinite loop (a "fork bomb") that crashed developers' computers by using up all their RAM, forcing them to investigate.
2. How the "Security" tool caused the problem
The LiteLLM maintainers used a well-known security scanner called Trivy to check their code for vulnerabilities. Ironically, the attackers broke into LiteLLM by first breaking into Trivy.
- The Mistake: The LiteLLM team had their automated system set to always download the "latest" version of the Trivy security scanner instead of a specific, "pinned" version number.
- The Breach: Attackers (a group called TeamPCP) compromised Trivy’s own update system. When LiteLLM ran its "security scan," it pulled the poisoned Trivy tool.
- The Result: Instead of scanning for bugs, the fake security tool stole LiteLLM’s private "publishing key." The hackers used this key to upload the malicious LiteLLM versions directly to the public, making them look like official updates.
3. The OpenClaw involvement
"OpenClaw" played a double role in this event, representing a new era of AI-driven cybercrime:
- The Attacker's Bot: The hack was initiated by an autonomous AI agent named hackerbot-claw (which used the OpenClaw framework). This bot automatically scanned tens of thousands of GitHub projects to find the exact "unpinned" security tool mistake mentioned above. This is considered one of the first major cases of an AI agent attacking AI infrastructure.
- The Impacted Users: OpenClaw is a popular AI personal assistant that often runs through LiteLLM. Because these two tools are so closely linked, thousands of OpenClaw users were among the first to be infected, as their setups automatically pulled the bad LiteLLM update.
Summary
LiteLLM tried to be safe by using a security scanner (Trivy), but they left the "front door" unlocked by not locking the scanner to a specific version. An AI-powered hacker bot (OpenClaw/hackerbot-claw) found that unlocked door, stole the keys to the factory, and started putting "poison" into the LiteLLM updates. The only reason it didn't stay hidden longer was that the poison was so strong it crashed the computers it was meant to rob.
The Lesson: In 2026, even your security tools can be compromised and the fact that something is "open source" doesn't automatically mean it is safe, because open source supply chain is so deep and wide that you don't really know what hides in all dependencies.
AmiBroker is unaffected
As far as AmiBroker is concerned, we are NOT using 3rd party libraries for LLM access. AmiBroker talks to OpenAI / Google HTTP APIs directly, natively using in-house developed code, written in C++ with bare human hands
. AmiBroker uses just core Windows Internet functions (WINET) (like InterentOpenURL). No Python involved. No way for Python / pip update to affect anything inside AmiBroker.


