Dev.to AI 🤖 Ai 👁 0 📖 5 min read

NVIDIA's Brev breach and the month AI Dev Platforms got hunted

NVIDIA's Brev GPU cloud had 16 days of unauthorized activity that may have exposed SSH keys. What happened and what to check. NVIDIA has told some customers of Brev, its cloud platform for GPU virtual machines, that i

NVIDIA's Brev breach and the month AI Dev Platforms got hunted

NVIDIA's Brev GPU cloud had 16 days of unauthorized activity that may have exposed SSH keys. What happened and what to check.

NVIDIA has told some customers of Brev, its cloud platform for GPU virtual machines, that it found 16 days of unauthorized activity on the Brev network. The SSH key Brev uses to reach customer VMs may have been exposed. NVIDIA says the key has been rotated and it found no evidence of misuse.

On its own that is a contained incident. It is not on its own. Brev is one of more than a dozen AI developer platforms that disclosed incidents between early October and mid November, and the public reports point at the same target every time: the credentials developers leave on their machines.

What happened at Brev

Brev lets developers spin up GPU-backed VMs and one-click software setups. NVIDIA acquired it in 2024. Here is what the customer notice, as reported, says:

Unauthorized activity ran from October 4 to October 20, 2026.

What may be exposed: the SSH key Brev configures for customer instances. In NVIDIA's words, "this SSH key has since been rotated, and your instances have been updated with the replacement key."
Misuse: NVIDIA found "no evidence that the compromised keys were misused."
Here is what it does not say, as of today: how the attackers got in, when NVIDIA detected them, how many customers are affected, and whether any customer data or workloads were touched. No public post-mortem has been published. That gap matters, because a rotated access key does not undo anything done with the old one.

Brev was not alone

On October 30, Wiz published "Black October" for AI Developer Platforms. It listed nine platforms that disclosed incidents that month, including Fireworks AI, Lightning AI, OpenCode, Railway and Warp. Its running updates have since added Brev, Trigger.dev, Chainstack, kernel.sh, Blacksmith, Tensorlake and NEAR AI. One of them, Zeabur, is shutting down because of its incident.

Wiz does not tie these to one vulnerability or one actor, and Brev has not shared technical details. But the reports that do exist line up:

Credentials are the way in. Fireworks, Zeabur and Lightning attribute their root causes to credential access. Railway points to privilege escalation in its build infrastructure, and Warp to a third-party dependency.
AI keys are the prize. In Wiz's words, all public reports highlight attackers "explicitly hunting stored environment variables, with a focus on those granting AI access."
Stolen keys get used in minutes. In two cases Wiz traced, the first use of a stolen enterprise key came within 30 minutes of the vendor breach. Days later, one key was driven to about 800,000 Bedrock model calls in 30 hours before it was shut off.
The economics explain it. Stolen model access resells easily, so an AI key is close to cash, and a developer platform holds thousands of them at once.
Why your dev box is the target
A GPU VM or a hosted dev environment is where people paste the keys they need to get work done: model API keys, cloud credentials, GitHub tokens, sometimes wallet keys. They sit in .env files, shell history and environment variables, readable by anything that runs there.

When the platform is breached, the platform's own credentials are not the only loss. Its access to your machine becomes the attacker's access to your keys. That is why an SSH key that "may have been exposed" is worth taking seriously even with no evidence of misuse.

We have seen the same pattern from the other side. In Episode 5 of our VulnScanning series, Aeon's scanner found an API proxy writing full API keys into its logs. NEAR AI's November incident involved two cloud API keys exposed in logs, revoked after an attacker reached an inference server through an SGLang remote code execution bug. Keys leak sideways, through logs, responses and machines, long before anyone scans for them.

What to do if you use Brev

NVIDIA's notice, as reported, asks for no specific action. These checks come from security analysts covering the incident, and they are cheap:

Check ~/.ssh/authorized_keys on every Brev instance. Remove any key you do not recognize.
Review SSH logins between October 4 and October 20. Look for sessions you cannot account for.
Rotate every secret that lived on those VMs. Model API keys, cloud credentials, Hugging Face and GitHub tokens, anything in .env. Rotating Brev's key does not rotate yours.
Watch your AI bills. Unusual spend on a model provider is often the first sign a key was stolen.
Look for persistence. New cron jobs, systemd services or startup scripts on the VMs.
What to do on any AI dev platform
Keep long-lived keys off shared machines. Use short-lived tokens, OIDC or a secrets manager that issues credentials per job.
Scope every key. A key that can only call one model, with a spend cap, is worth far less to a reseller.
Alert on usage, not just on breach notices. Most of these platforms disclosed days or weeks after the activity. Your billing dashboard will usually notice first.
Assume your vendors will be breached. Ask what they store for you and how fast they will tell you.
How Aeon limits the blast radius
Aeon runs as an agent on GitHub Actions and holds keys too, so it is built around the same assumption. Each skill declares the keys it needs and only gets those, only for that call, through least-privilege secret handling. A compromised skill cannot read every secret the agent holds. Aeon also scans its own code on a schedule, and its vulnerability scanner has found and fixed 153 issues in open-source projects, including leaked secrets and API keys written to logs.

FAQ

What is NVIDIA Brev?

A cloud platform from NVIDIA for launching GPU-backed virtual machines and preconfigured AI software environments. NVIDIA acquired it in 2024.

Was customer data stolen in the Brev breach?

NVIDIA has said the SSH key used to access customer instances may have been exposed, that it has been rotated, and that it found no evidence of misuse. It has not said whether customer data or workloads were accessed.

What should Brev users do?

Check authorized_keys and SSH logins for October 4 to 20, 2026, rotate any secrets stored on the VMs, and watch AI and cloud bills for unusual usage.

Try it

Aeon is open source and MIT licensed. Fork it at github.com/aeonfun/aeon, or set it up in the browser with Aeon Connect.

📰 Read the original article on Dev.to AI

Originally published by Dev.to AI. Aggregated on AIWithGhost for educational purposes — full credit and traffic to the original publisher.