Recent investigations have uncovered a sophisticated new attack vector targeting AWS S3 storage, where threat actors are exploiting Amazon's Server-Side Encryption with Customer-Provided Keys (SSE-C) feature to conduct ransomware attacks. Unlike traditional ransomware that requires malware deployment, these attacks leverage AWS's native functionality to hold data hostage. The innovation of this approach lies in its simplicity - attackers encrypt data using legitimate AWS features (e.g., AWS KMS), making detection particularly challenging.
In this blog, we explore the mechanics of these attacks, provide statistical context for the threat landscape, outline prevention strategies, and explain how cloud security tools can help organizations protect their cloud assets.
Affected Services
The Alarming State of Cloud Storage Security
Recent research reveals concerning statistics about cloud storage security, highlighting why SSE-C attacks have become an attractive vector for threat actors:
66% of cloud storage buckets contain sensitive data, making them prime targets for ransomware attacks.
AWS S3 misconfigurations account for 16% of cloud security breaches, demonstrating how configuration errors can create security vulnerabilities.
Approximately 31% of S3 buckets are currently open to the public, exposing them to various security vulnerabilities and potential attacks.
According to GrayHatWarfare, more than 325,000 Amazon S3 buckets are publicly exposed. Elastic Security Labs' 2024 Global Threat Report further highlights the risk, revealing that 30% of failed AWS security posture checks were related to S3 misconfigurations.
These figures underscore why S3 buckets have become attractive targets for threat actors. They often contain valuable data and frequently suffer from security misconfigurations.
Anatomy of an SSE-C Ransomware Attack
SSE-C ransomware attacks represent a sophisticated evolution in cloud-targeting tactics, exploiting legitimate AWS encryption functionality rather than deploying traditional malware. Here's how these attacks typically unfold:
Initial Access
The attack begins when threat actors gain access to compromised AWS credentials or locate publicly exposed AWS account keys with sufficient permissions to interact with S3 buckets. This typically requires credentials with at least s3:GetObject and s3:PutObject permissions.
A leading cybersecurity consultant warns that "In just the past few months, we have witnessed two different methods for executing a ransomware attack using nothing but legitimate cloud security features."
Exploitation Mechanism
Once attackers have valid credentials, they execute a multi-step attack:
Discovery: They enumerate accessible S3 buckets and objects using s3:ListObjectsV2 and other discovery API calls.
Encryption: For each object, they:
Generate a secure AES-256 encryption key that only they possess
Pressure Tactics: Apply a 7-day deletion lifecycle policy to the encrypted objects using s3:PutLifecycleConfiguration, creating urgency for payment.
Ransom Demand: Upload ransom notes to the bucket detailing payment instructions, typically demanding cryptocurrency payment.
What makes this attack particularly insidious is that AWS processes the encryption request using the attacker's key but does not retain the key itself. Instead, it logs only a hash-based message authentication code (HMAC) in AWS CloudTrail, which is insufficient for recovery or forensic analysis.
Real-World SSE-C Attack Examples
The Codefinger Ransomware Campaign
A recently identified ransomware group, dubbed "Codefinger", has successfully targeted at least two organizations using the SSE-C encryption technique. This group specifically warns victims not to alter account permissions or attempt countermeasures during ransom negotiations, as any changes could result in the attackers cutting off communications, leaving victims with permanently encrypted data.
It was also observed by industry experts that the operation has already impacted multiple organizations who have warned about the potential for copycat attacks given the effectiveness of this approach.
Industry Observations
A leading cybersecurity consultant reported multiple methods of cloud ransomware attacks that leverage legitimate cloud security features. Beyond the SSE-C technique, the team demonstrated a similar attack using AWS KMS keys with external key material, using scripts that could be easily generated by large language models like ChatGPT.
This diversification of attack methods indicates that cloud-native ransomware is evolving rapidly, with the experts noting that "this topic is top-of-mind for both threat actors and researchers alike."
Best Practices to Prevent SSE-C Attacks
Organizations can implement several key defenses to mitigate the risk of SSE-C ransomware attacks:
Restrict SSE-C Usage
Implement S3 bucket policies that explicitly deny the use of SSE-C when not required for legitimate business purposes
Use resource control policies (RCPs) at the organization level in AWS Organizations to enforce this restriction across all accounts
Strengthen Identity and Access Management
Implement the principle of least privilege for all IAM users and roles accessing S3 resources
Regularly audit and rotate AWS access keys to limit the impact of credential compromise
Prefer short-term credentials (IAM roles with temporary security tokens) over long-term access keys
Use AWS Identity Center and Secrets Manager to minimize credential exposure
Enable Comprehensive Logging and Monitoring
Configure detailed CloudTrail logging for all S3 operations, particularly focusing on encryption-related activities
Implement monitoring for unusual patterns, such as:
Bulk object encryption operations
Unexpected SSE-C usage in buckets that typically use AWS-managed encryption
Lifecycle policy changes that set short expiration timeframes
The presence of suspicious files like ransom notes
Implement S3-Specific Security Controls
Enable S3 Block Public Access at both the account and bucket levels
Enforce server-side encryption using AWS-managed keys (SSE-S3 or SSE-KMS) as the default
Require secure transport (HTTPS) for all S3 operations using the aws:SecureTransport condition
Enable S3 Versioning with MFA Delete protection to preserve previous versions of objects
Consider implementing S3 Object Lock with WORM (Write Once Read Many) protection for critical data
Prepare Incident Response Procedures
If an SSE-C attack is suspected, immediately restrict SSE-C usage through emergency policy changes
Have procedures in place to promptly engage AWS Support during security incidents
Maintain offline backups of critical data using proper key management practices
Conclusion: Staying Ahead of Cloud-Native Ransomware
SSE-C ransomware attacks represent a sophisticated evolution in threat actor tactics, leveraging legitimate cloud functionality to achieve malicious objectives. As cloud adoption continues to accelerate, we can expect to see more threat actors exploiting native cloud features for financial gain.
The effectiveness of these attacks stems from their simplicity—they don't require traditional malware, exploit zero-day vulnerabilities, or exfiltrate data. Instead, they leverage the intended functionality of cloud services to harm organizations through data unavailability.
By implementing comprehensive security controls, restricting unnecessary encryption methods, maintaining strong identity management practices, and leveraging advanced security tools, organizations can significantly reduce their risk of falling victim to these emerging cloud-native ransomware techniques.
As cloud ransomware tactics are evolving rapidly, it is essential for security teams to stay informed about these new attack vectors and implement appropriate preventive measures before they become victims of an attack.