Skip to main content
Mallory
← Back to News
leaked-secret-api-keycloud-misconfigurationmass-credential-exposure

Publicly Exposed AWS Keys Left Thousands of Corporate Accounts at Risk

Breach & Incident Intelligence · 8 sources · Updated 3mo ago · First seen Aug 21, 2026

Publicly Exposed AWS Keys Left Thousands of Corporate Accounts at Risk

Truffle Security reported that more than 9,300 publicly exposed Amazon Web Services access keys remained active and valid after being leaked between August 2022 and August 2026, highlighting a widespread cloud credential exposure problem. Across public sources, the researchers identified 64,024 unique AWS keys and found that 88% of a subset of 10,616 keys with complete credentials still successfully authenticated as of August 10. The leaked secrets included 526 root keys and 242 IAM user keys with AdministratorAccess, creating a path to full AWS account compromise.

Researchers said the exposed credentials could allow attackers to steal or destroy data, take control of applications, establish persistence, and deploy cryptominers. Hugging Face was identified as the largest single source of leaked AWS keys in the dataset, while the persistence of valid credentials pointed to weak key rotation and poor credential hygiene across affected organizations. Truffle Security urged organizations to delete root access keys, rotate or revoke exposed credentials, review IAM key age and permissions, and enable AWS budget alerts to detect abuse.

Is this vendor in your chain?See attribution, scope, and your downstream exposure.
Check the blast radius
Event timeline

How this story unfolded

Events from the most recent confirmed update back to the earliest known activity.

7 events · Aug 2022 – Aug 10, 2026
  1. Aug 10, 20263mo ago

    Researchers verify most leaked AWS keys still work

    Truffle Security found that 88% of 10,616 exposed AWS keys with complete credentials still authenticated, showing that thousands of leaked keys remained usable. The source explicitly anchors this verification status as of August 10.

    Hundreds of leaked AWS keys give full control over corporate accounts
  2. Aug 2026

    Truffle Security finds most leaked AWS keys were never rotated

    Truffle Security reported that 86% of enumerated leaked AWS keys were never rotated, superseded, or cleaned up, and that only 13.7% had any newer key alongside the leaked one. The researchers also said half of the live exposed keys were more than five years old, indicating the problem accumulated over years rather than from a recent spike.

    Researchers warn thousands of active AWS access keys are publicly exposed | IT Pro
  3. Aug 2026

    Truffle Security identifies Hugging Face as major source of leaked AWS keys

    Truffle Security reported that Hugging Face datasets were the largest single source of leaked AWS keys in its dataset, identifying 8,482 unique live keys across 3,394 public datasets. The report said 18% of the live keys found in those datasets had root privileges.

    Researchers Uncover Thousands of Leaked AWS Keys - Infosecurity Magazine
  4. Aug 2026

    Article details risky gaps in AWS leaked-credential quarantine policy

    A new report described AWS's quarantine policy for publicly leaked credentials and said it still permits numerous sensitive actions, including SSM command execution, STS role assumption, some RDS and Auto Scaling operations, CloudTrail disruption, SNS/SES abuse, S3 writes and retention locking, secret access, backup deletion, and CloudFormation stack deletion. The piece argued that AWS's approach limits some fraud-related abuse without fully neutralizing compromised keys, leaving significant residual risk.

    AWS Security makes an inscrutable choice - Corey Quinn
  5. Aug 2026

    Truffle Security identifies 768 active corporate AWS admin credentials

    Truffle Security reported that 768 publicly exposed AWS credentials still provided full administrative control over corporate AWS environments. The set included 526 root access keys and 242 IAM-user credentials with the AdministratorAccess policy, highlighting especially severe residual risk among leaked keys.

    768 Leaked Corporate AWS Keys Remain Active With Full Administrator Access
  6. Aug 2026

    Truffle Security reports thousands of active exposed AWS keys

    Truffle Security reported that more than 9,300 publicly exposed AWS access keys observed between August 2022 and August 2026 remained active and valid. The dataset included 64,024 unique keys from 50,654 AWS accounts, with many highly privileged credentials such as root keys and AdministratorAccess IAM keys.

    Hundreds of leaked AWS keys give full control over corporate accounts
  7. Aug 2022

    Truffle Security begins four-year tracking of exposed AWS keys

    Truffle Security said it tracked the public exposure of AWS credentials over a four-year period spanning August 2022 through August 2026.

    Hundreds of leaked AWS keys give full control over corporate accounts
Linked entities

Related entities

Vulnerabilities, threat actors, malware, products, organizations, and breaches Mallory has linked to this story.

Open in app →

Affected products

2 linked
Amazon Web ServicesAws Identity And Access Management

Organizations

1 linked
Amazon Web Services
Do you run this?See attribution, scope, and whether this vendor sits anywhere in your supply chain.
Get the Full Incident Picture
Mallory platform

See the full picture, correlated to your attack surface.

This page covers what’s public. Mallory adds the parts that aren’t: which of your assets are affected, which threat actors are using it right now, and what to deploy next.

Exposure mappingMap indicators from this story to your assets and identify affected systems in minutes.
Threat actor evidenceEvery observed campaign, victim, and pivot linked to actors named in this story.
Associated malwareMalware, exploits, and IOCs connected to the activity described here.
Detection signaturesYARA, Sigma, and Snort rules deployed to your SIEM as soon as they’re published.
Scheduled alertsGet matching new stories delivered to your team as they break, not the next morning.
AI threadsAsk questions about this story and take action on the answers.