AI Weekly Malaysia

Two malicious LiteLLM releases (versions 1.82.7 and 1.82.8) were live on PyPI for ~40 minutes on March 24, 2026, containing credential-stealing code that harvested cloud keys, SSH keys, Kubernetes tokens, and database passwords. CloudSEK obtained ~434,000 captured files mapping potential exposure to 2,500+ organizations (including NVIDIA, Cisco, Deloitte, Volkswagen), and published a public lookup tool. The FBI warned in a July advisory that stolen credentials may be weaponized long after the initial compromise.

Why: If you installed LiteLLM from PyPI on March 24, 2026 (especially between 10:39–16:00 UTC), treat your CI/CD secrets as compromised and rotate cloud keys, SSH keys, Kubernetes tokens, and database passwords immediately—do not wait for proof of misuse. Check CloudSEK's public lookup tool by org name or domain to assess exposure.

Two malicious VS Code extensions ('helper-beeps.solidity-pro' and 'web3devtoolsx.solidity-pro') were found delivering an information stealer targeting Solidity/Web3 developers. Versions 1.0.0–2.4.x beaconed to Cloudflare Workers for encrypted Python payloads; v3.0.0+ became a full stealer harvesting GitHub/GitLab tokens, AWS keys, Cloudflare tokens, OpenAI API keys, Telegram bot tokens, crypto wallet vaults, SSH keys, and 1Password MFA tokens, exfiltrating via Telegram bot upload. The malware uses obfuscation, clean intermediate versions to build trust, and randomized delayed activation hours or days after installation to evade sandbox scanning.

Why: If you develop in VS Code with community extensions—especially Web3 or Solidity tooling—audit installed extensions now and revoke any GitHub, GitLab, AWS, Cloudflare, OpenAI, or Telegram bot tokens that may have been exposed. The delayed activation means a recently installed extension that seemed fine for days could still be malicious; remove anything matching 'solidity-pro' and rotate credentials proactively.