Vendor

Truffle Security

0 mentions in 7 days · 2 in 30 days · 2 total · first seen Aug 24, 2026 · last 22d ago

Timeline2 articles

TruffleHog AWS Analyze reduces remediation time on leaked AWS credentials

Truffle Security launched TruffleHog AWS Analyze, which maps leaked AWS keys' permissions and role assumptions; research found 88% of 64,024 leaked keys still active.

Truffle Security announced TruffleHog AWS Analyze, a TruffleHog Enterprise feature that enriches leaked AWS credentials with identity, effective permissions, and role-assumption context to help teams assess blast radius and prioritize remediation, extending earlier coverage of SaaS and Google Cloud to AWS. Truffle Security research on 64,024 unique leaked AWS keys found 88% still active, a median exposure of five years, only 14% rotated, 84% with full administrator access, and 1 in 6 being root keys, including 929 keys AWS had flagged via its compromised-key quarantine policy that still authenticated. A scan of 7.6 petabytes of public AI training data on Hugging Face found 3,343 live AWS keys, over 900 of which could list S3 buckets holding at least 51.7 TB of private data.

Help Net SecurityAug 25, 00:00 UTC · 22d agoTools

Researchers Uncover Thousands of Leaked AWS Keys

Truffle Security researchers discovered more than 9,000 publicly accessible and active AWS key pairs, creating credential exposure and account-takeover risks.

Truffle Security reported finding over 9,000 AWS key pairs that are simultaneously publicly accessible and active. Anyone retrieving such keys could potentially access the associated cloud resources without authentication. The finding underscores widespread secrets-hygiene failures in cloud environments and the risks of long-lived static credentials.

Infosecurity MagazineAug 24, 08:05 UTC · 22d agoResearch

Appears with

vendor AWS 2 organization Truffle Security 2 product AWS 1 product TruffleHog AWS Analyze 1 product TruffleHog Enterprise 1 organization AWS 1 vendor Hugging Face 1 organization Hugging Face 1

Entities are extracted by the model from each article. Watching an entity keeps it in this browser only (no account); the watchlist page and dashboard alerts use it.