
New Amazon Ransomware Attack—‘Recovery Impossible’ Without Payment
Ransomware, a scourge on the digital landscape, has once again reared its ugly head. This time, it’s Amazon Web Services (AWS) users who are in the crosshairs as a new ransomware attack, dubbed Codefinger, is spreading rapidly.
According to reports from Halcyon threat research and intelligence team, this latest assault leverages AWS’s server-side encryption with customer-provided keys (SSE-C) to encrypt data and demand payment in exchange for decryption. The stakes are higher than ever before, as Codefinger makes recovery “impossible” without a hefty ransom being paid.
This new breed of ransomware is particularly pernicious due to its seamless integration with AWS’s secure encryption infrastructure. As Halcyon researchers warn, once encrypted, data cannot be recovered without the attacker’s key, leaving affected users with no choice but to pay up if they wish to regain access.
But how does Codefinger manage to achieve this level of security? The answer lies in its ability to identify vulnerable AWS keys using publicly disclosed or previously compromised credentials. It then encrypts files using AES-256 encryption and sets lifecycle policies for file deletion, ensuring that any changes to account permissions or files will end negotiations with the attackers.
Amazon Web Services has responded to the situation by emphasizing its commitment to customer security. In a statement, an AWS spokesperson stressed the company’s shared responsibility model, where customers are encouraged to follow best practices in terms of security, identity, and compliance.
While this may provide some solace for those already caught in the Codefinger crossfire, it’s clear that users must be vigilant in protecting their cloud resources. AWS claims to notify affected customers whenever exposed keys are discovered and quickly take necessary actions to minimize risks without disrupting business operations.
As with all cybersecurity threats, prevention is key. Users should ensure they follow security best practices and report any suspicious activity to AWS Support promptly. The clock is ticking for those who have already fallen victim to Codefinger – will they be able to recover their data, or will they succumb to the attackers’ demands? Only time will tell.
Stay tuned for further updates on this developing story as more information becomes available.
Source: www.forbes.com