Product
AWS Secrets Manager
- First Reported
- Sep 4, 2024
- Latest Reported
- Nov 10, 2026
Reported Context (22)
- Wiz says the attacker then surveyed cloud resources, retrieved secrets from AWS Secrets Manager and SSM Parameter Store, and read Lambda environment variables. Compromised Qubole AWS Credentials Used to Access Customer Environments
- The listing also claimed access to 492 AWS Secrets Manager values, approximately 7,000 sensitive keys, Terraform state files, Jenkins credentials, SSH private keys, and AWS administrative privileges. SOCRadar Tracks Five Unverified Dark-Web Access and Data Exposure Claims
- the workflow. Hours later, cloud credentials from the same organization were used to enumerate AWS Secrets Manager. Wiz's analysis does not say where those credentials came from or who used them. Wiz Finds Gheist Campaign Using Stolen GitHub Tokens to Steal Repository Secrets
- workflows. Within hours, cloud credentials from the same organization were used to enumerate AWS Secrets Manager, the researchers added. Gheist Campaign Uses Stolen GitHub Tokens to Harvest Cloud Secrets
- the workflow, and hours later, cloud credentials from the same organization used to enumerate AWS Secrets Manager. Gheist Campaign Uses Stolen GitHub Tokens to Expose Repository Secrets
CVE (6)
Malware (20)
People (14)
Threat Actors (20)
MITRE ATT&CK (76)
Vendors (32)
Products (131)
Tools (19)
Industries (11)
Countries (12)
Note: Related entities, including threat actors, malware, CVEs, MITRE ATT&CK techniques, vendors, products, tools, countries, and industries, are shown when they appear in the same reporting. Their presence does not necessarily mean they were targeted, compromised, vulnerable, responsible for the activity, or directly involved in the incident.
