Introduction
More than 9,300 Amazon Web Services (AWS) access keys have been exposed, granting full control over corporate accounts. Truffle Security has been tracking this exposure for the past four years and has identified 817 keys linked to companies, with 242 associated with the AdministratorAccess role. This role has full permissions to create, modify, delete, and view virtually all AWS services and resources within an account. Full control of a company's AWS account could allow an attacker to access, exfiltrate, or wipe cloud-hosted data, take control of servers and applications, and create rogue admin accounts for persistent access. Additionally, threat actors could use their access to deploy cryptominers, generating substantial charges for the company. Truffle Security recommends deleting all root access keys, reviewing IAM credentials by age, rotating or revoking exposed keys, and configuring budget alerts to defend against potential abuse.
Key Findings
- Exposure Timeline: The exposure of these keys occurred between August 2022 and August 2026. - Companies Involved: 817 keys were linked to companies, with 526 of them being AWS root keys. - Role Permissions: 242 keys were associated with IAM users with the AdministratorAccess policy, granting full permissions to AWS services. - Total Keys: 768 live keys in the two sets “full control of a company's AWS account. ”
- Credentials: 64,024 unique AWS keys were extracted from 50,654 AWS accounts after removing duplicates. - Verification Subset: 10,616 keys had complete credentials and continued to authenticate as of August 10. 9% of the keys were root, the highest-privileged identity, which isn’t restricted by IAM permissions. - Age Distribution: The median age of the 2,903 keys with available creation dates was 1,831 days (about five years), while the oldest had existed for 17. - Rotation Status: Only 398 (13. 7%) of the entries had a newer access key associated with the same user, suggesting most had never been rotated.
Recommendations
- Delete Root Access Keys: All root access keys should be deleted to prevent unauthorized access. - Review IAM Credentials: IAM credentials should be reviewed by age to identify and remove outdated or unnecessary keys. - Rotate or Revive Exposed Keys: Exposed keys should be rotated or revoked to ensure they are no longer accessible. - Configure Budget Alerts: Budget alerts should be configured to monitor and alert on any unauthorized access or usage. - Treat Credentials as Compromised: Any credentials committed to a public source should be treated as compromised and immediately addressed.
Additional Context
- Exposure Sources: Hugging Face, a popular online platform where developers share AI models, datasets, and applications, was the largest single source of leaked AWS keys, accounting for 8,482 unique key exposures. - Exposure Details: Truffle Security found that for the 2,903 keys with available creation dates, the median age was 1,831 days (about five years), while the oldest had existed for 17. - Notification and Support: Truffle Security has notified all identifiable owners of the exposed credentials and recommended following the steps listed in this post. Customers can contact AWS Support with any questions or concerns about the security of their account.
Conclusion
The exposure of AWS access keys highlights the importance of securing credentials and following best practices to prevent unauthorized access and potential abuse. By taking proactive measures, organizations can mitigate the risks associated with exposed credentials and protect their AWS accounts from potential threats.

Comments