Nine Forum Listings Show Where Your Cloud Security Budget Should Actually Go
Cloud

Nine Forum Listings Show Where Your Cloud Security Budget Should Actually Go

Underground sellers spent early November advertising access to AWS S3 buckets, Alibaba Cloud accounts, and build systems for as little as 250 dollars, and almost none of it required breaking into the cloud itself.

PublishedNovember 16, 2026
Read time5 min read
Share

The marketplace nobody in the cloud security budget meeting is pricing

Threat intelligence researchers tracked nine listings posted across DarkForums, Exploitin, and PwnForums between November 2 and 9, offering direct access to corporate networks, databases, cloud accounts, and business applications. The sellers were not advertising zero day exploits or novel attack techniques. They were advertising working credentials: VPN accounts, Remote Desktop Protocol sessions, cloud API keys, database logins, and authenticated application sessions, priced like commodities because that is exactly what they have become.

The named systems tell the real story about where cloud risk concentrates. TeamCity build servers, Windows build hosts, SQL Server instances, Pulse Secure and FortiGate VPN gateways, PandaDoc document sessions, Slack and Twilio tokens, and credentials for AWS S3 and Alibaba Cloud all appeared across the nine listings. Every one of those is a system that sits adjacent to cloud infrastructure rather than inside a hyperscaler's own security perimeter, which is precisely why it keeps showing up for sale. BrowserStack sessions and plain FTP access rounded out the list, a reminder that the attack surface for sale includes whatever tooling engineering teams happened to wire into their pipelines, not just the obvious production systems.

The scale behind a few hundred dollar price tag

The asking prices look almost trivial next to what they unlock. A PandaDoc session went for 250 dollars and reportedly carried access to more than 8,000 documents. A Pulse Secure VPN account listed at 980 dollars. A FortiGate configuration with SSH and SSL VPN access tied to a US manufacturer, spanning 81 hosts, listed at 4,000 dollars. None of these numbers would clear a procurement approval threshold at most enterprises, which is exactly the point: the barrier to acquiring serious access into a target environment is now lower than the barrier to buying a conference ticket.

The most striking listing involved a TeamCity build system posted on November 5, which the seller claimed reached 28 databases, 1,133 targets, and 130 customer environments. A separate listing tied to an ERP SaaS provider claimed 180 Alibaba Cloud key pairs with 114 still active, 525 compute instances, nearly 240,000 plaintext MySQL credentials, almost 45,000 API tokens, and remote code execution on roughly 30 production hosts. Even heavily discounted for seller exaggeration, both numbers describe blast radii far beyond what any single stolen password should produce.

One VPN account, ten thousand hosts

A listing tied to a Turkish organization claimed enterprise admin rights spanning more than 10,000 hosts through a single VPN compromise. That figure, more than any dollar amount in this set of listings, is the one worth sitting with. It describes a world where identity and access management inside the corporate network, not the cloud provider's control plane, is the effective perimeter for an enormous share of an organization's infrastructure.

Researchers were careful to flag that these are seller claims, not independently verified compromises. One French RDP listing was marked sold, and its seller later claimed exploitation, but the report notes this remains unconfirmed and the ERP listing came from a newly registered account with no corroborating evidence. The caveats matter for accuracy. They do not change the operational lesson, because even a fraction of these claims being real represents exposure most enterprises are not actively hunting for.

It would be easy to read this as a cloud security story about hyperscaler vulnerabilities, and that would be the wrong read. None of the nine listings described a breach of AWS's, Azure's, or Google Cloud's own infrastructure. Every one of them involved credentials, tokens, or sessions that customers generated and then failed to rotate, scope, or monitor closely enough. The hyperscalers built the vault. These listings are about the keys customers left lying around it, scattered across build pipelines, VPN concentrators, and third party SaaS integrations that most security reviews treat as secondary to the cloud environment itself.

That distinction matters for where security investment should go next. A team that has thoroughly hardened its cloud provider's native controls, identity federation, network policies, encryption at rest, while leaving build servers on long lived credentials and SaaS tokens unrotated for months, has optimized the wrong layer of the stack. The access for sale in these listings came almost entirely from the layer most teams audit least often, which is exactly why it is the layer worth putting on next quarter's audit calendar rather than assuming the cloud provider's shared responsibility model already covers it.

What to actually do about it this quarter

The practical response does not require a new security product. It requires rotating exposed cloud keys on a defined schedule rather than only after an incident, auditing every deployment and build system credential for scope and age, and revoking sessions that have no business staying authenticated for months at a time. Build systems like TeamCity deserve the same scrutiny as production databases, since this round of listings shows they are frequently the shortest path into both.

For a CTO weighing where to spend the next security dollar, this is a useful corrective. Hardening the cloud provider boundary stays worthwhile, and the exposure in these listings sits mostly one layer further out, in the build systems, VPN gateways, and SaaS tokens that live around that boundary rather than inside it. Nine listings for a few thousand dollars combined described access that would be catastrophic at most of the enterprises involved, and every one of them traces back to ordinary credential hygiene rather than an exotic attack. That is a solvable problem, and it is cheaper to solve before the tenth listing than after it.

Tagged#news#cloud#infrastructure#datacenter#aws#azure#gcp#hyperscalers#credential-hygiene#access-broker#ciso#forum-marketplace