Cascadity Audio
← All streams

#credential-theft

Everything tagged credential-theft, across every stream.

0

"Black October": Wiz counts at least nine AI developer platforms breached in a month, with stolen AI keys resold

Wiz connects the dots across a month of separate breach notices and shows how a stolen AI key gets tested, resold and burned through.

Cloud security firm Wiz says at least nine platforms that developers use to build and host AI apps disclosed security incidents in October, among them Fireworks AI, Lightning AI, OpenCode, Railway, Warp and, on October 30, Northflank. It later added Brev (NVIDIA), Trigger.dev and Chainstack. Wiz says no single vulnerability links them, but every public report describes attackers hunting stored environment variables, especially keys that unlock AI services. Zeabur says it will shut down after its incident.

Wiz traced two stolen enterprise keys: each was first tested with a single call, then flooded with Amazon Bedrock requests, about 2.5 million calls in all and likely over $100,000 in usage at list price, with traffic resembling resold coding-agent use. It links the keys to an LLM-resale operation.

Northflank told customers to assume every environment variable was decrypted and to rotate all secrets; users reported their AI keys being abused. It says the attack vector was contained within an hour, that it patched the Linux flaw CVE-2026-98432 across its fleet, and that a root-cause report will follow.

Cascadic Analysis 2
UndertowPrivilege escalation + credential propagation

What hidden risk could pull against this, even if the news is good?

Wiz says no single bug links the nine incidents, but every public report describes attackers going after stored environment variables, and Railway's own account starts with privilege escalation in its build infrastructure. A hosting platform holds its customers' AI keys so their apps and agents can run, which makes one breach a key ring for many companies at once. Northflank's advice to treat every stored variable as decrypted and rotate all of them shows how far a single foothold can reach.

0
UndertowAutonomous cyber capability scales attackers enormously

What hidden risk could pull against this, even if the news is good?

Within 30 minutes of a key being stolen, one test call came from a residential address; then one key saw about 800,000 Bedrock calls in 30 hours and another about 1.7 million in 13. Fireworks, OpenCode and Warp reported signs of an "agent swarm" attack, and Wiz links the keys to resale operations whose traffic looked like coding-agent use. Theft, testing and resale of AI access now run fast enough that a stolen key can rack up more than $100,000 before anyone notices the bill.

0
Rabbit Holes 1
0

Cisco Talos finds an infostealer that asks an AI model to rank each victim by how much they're worth

Talos quotes the malware's own prompt and shows how it switches models when one refuses.

Cisco Talos describes VOLTA, a self-deleting Windows infostealer that, after taking browser passwords, cookies, payment cards, crypto wallet phrases, chat and gaming sessions, and cloud keys, builds a profile of the victim and sends it to a large language model through OpenRouter. The prompt tells the model to act as "a forensic intelligence analyst drafting a target assessment," with sections on what the victim is worth and how weak their security habits are.

Talos says the malware uses stolen sessions to enrich the profile, for example by searching the victim's Gmail for receipts to confirm a home address and pulling food-delivery order history. Its default model is Anthropic's Claude Opus 4.6; if a response contains refusal phrases such as "I can't," it falls back to Moonshot's Kimi K2 and then Google's Gemini 2.5 Flash, which Talos reads as the author expecting guardrails.

Talos's point: the AI is not writing malware here but doing the criminal's triage, turning a raw credential dump into a prioritized dossier.

Cascadic Analysis 2
UndertowAutonomous cyber capability scales attackers enormously

What hidden risk could pull against this, even if the news is good?

Talos is careful to say VOLTA's AI layer saves the criminal effort rather than adding speed or reach: the model turns a raw dump of passwords, cookies and wallets into a ranked "target assessment." That triage used to need a skilled person reading through each haul. Talos notes the dossier feature could be sold to low-skill buyers, which is how cheaper analysis turns into more attackers who know exactly which victim to work on first.

0
UndertowPrivilege escalation + credential propagation

What hidden risk could pull against this, even if the news is good?

The stolen sessions are not just loot; VOLTA uses them as tools. It searches the victim's own Gmail for receipts to confirm a home address, calls Uber Eats and DoorDash sessions for order history and reuses the Discord token for more profile data. Each logged-in session opens the next piece of a person's life, which is why Talos's advice focuses on keeping credentials in hardware-backed stores and spotting Chrome launched headless to steal tokens.

0
Rabbit Holes 1
0

Hijacked LiteLLM release on PyPI and Docker planted a credential stealer and backdoor

SafeDep shows exactly how the malicious files got into the package; BleepingComputer lists the affected images and what to rotate.

Version 1.107.0 of LiteLLM, a popular open-source Python gateway for calling AI models, was published to PyPI and Docker registries with malware on October 21, according to SafeDep and BleepingComputer. LiteLLM confirmed the compromise and says the release pipeline was hijacked; SafeDep says LiteLLM believes the attacker took three developers' GitHub CLI credentials from the logs of an internet-exposed internal deployment.

All seven wheels for Linux, macOS and Windows added three files that run whenever Python starts, even if litellm is never imported. One steals SSH keys, cloud and CI/CD credentials, AI tool tokens, browser passwords and stored model-provider keys; another checks in hourly and downloads and runs more code. The PyPI release was live from 11:39 to 13:23 UTC; Docker Hub and GHCR tags pointed to bad images for a couple of hours. Versions 1.106.2 and the 1.107.0 release candidates are clean.

BleepingComputer says affected systems should be isolated and rebuilt and all exposed secrets rotated, and warns that running Python or pip to investigate also triggers the malware.

Cascadic Analysis 1
UndertowPrivilege escalation + credential propagation

What hidden risk could pull against this, even if the news is good?

SafeDep says LiteLLM believes the attacker started with three developers' GitHub CLI credentials, found in the logs of an internet-exposed internal deployment. Those let the attacker publish a release, and the release's job was to collect more credentials: SSH keys, cloud and CI/CD secrets, AI tool tokens and stored model-provider keys. Because LiteLLM is a gateway that sits in front of many model providers, the machines that run it tend to hold keys to all of them at once.

0
Rabbit Holes 2
0

OpenCode breach exposes users' stored AI provider keys, and some run up charges overnight

A cautionary tale for anyone who stores API keys in a hosted dev tool, plus a twist about AI models refusing to help defenders.

OpenCode, the open-source AI coding agent, said on October 17 that a breach tied to what it called a large-scale distillation attack hit 1.4% of users of OpenCode Console, its hosted service, and that it had emailed those affected. BleepingComputer and TechCrunch report that only users who had linked external providers (Anthropic, OpenAI, Google) were affected, that some reported hundreds to over $1,700 in unauthorized charges, and that Google suspended some projects. Co-founder Dax Raad said the open-source app and CLI were not affected; the company has not said how attackers got in. OpenCode told users to revoke their keys and says refunds are underway. Raad said AI models first refused to help the investigation until it switched to OpenAI's Daybreak cybersecurity model.

On Hacker News, commenters asked why a hosted service held provider keys at all, questioned the unproven 'distillation' label, and argued over earlier warnings about the project's data practices.

Cascadic Analysis 1
UndertowPrivilege escalation + credential propagation

What hidden risk could pull against this, even if the news is good?

OpenCode's hosted service stored keys to users' Anthropic, OpenAI and Google accounts, and only users who had linked them were hit; some reported hundreds to more than $1,700 in charges, and Google suspended some projects. A coding tool that holds your provider keys turns one breach into spending on several other companies' bills, which is the question Hacker News commenters raised: why the hosted service held the keys at all.

0
Rabbit Holes 1