Skip to content

Topic

Cloud Credential Exposure

Security issue where cloud access keys or tokens, such as AWS credentials, are inadvertently exposed in code or build artifacts, enabling account abuse.

Current stories

securityConfirmed4 publishers

Leaked AWS keys keep working: 526 root, 242 admin, and a rotation rate of 13.7 percent

Truffle Security retested 10,616 publicly leaked AWS credentials and 88 percent still authenticated. The median key was about five years old and had no successor.

Publishers:bleepingcomputer.com infosecurity-magazine.com scworld.com trufflesecurity.com

Perspective Coverage

4 publishers
Builder
Builder 38%
Operator
Operator 52%
Investor
Investor 10%

Reality

Evidence62
Adoption
Not scored
Hype gap+12
Incentives65
Confidence60
scienceOne report1 publisher

An attacker used a planted AWS key five minutes after it appeared on GitHub

Unit 42 committed a fresh, overly permissive AWS key to a random GitHub repository with the usual quarantine policy switched off, then timed how long a cryptojacking crew took to find it and start mining.

Reality

Evidence52
Adoption45
Hype gap+30
Incentives78
Confidence60
buildOne report1 publisher

Requiring IMDSv2 cuts off every caller that never learned the token PUT

The EC2 console tells you to check MetadataNoToken before setting HttpTokens to required, and that check carries the whole risk, because the metric only counts calls that actually happened in the window you watched.

Publishers:dev.to

Reality

Evidence52
Adoption
Not scored
Hype gap+8
Incentives20
Confidence45
productOne report1 publisher

AWS quarantines leaked keys. Truffle Security's sweep says 9,342 of them still work.

A sweep of public code, datasets and CI logs found 768 AWS keys with full account control. The containment policy AWS applies to detected leaks still permits deleting the audit trail.

Publishers:thenextweb.com

Reality

Evidence44
Adoption58
Hype gap+16
Incentives57
Confidence51