Cyber Security News

Hackers Launch Password Spraying Attacks Against AWS Root Accounts at 150+ Organizations

Research has discovered a password-spraying campaign targeting AWS root user accounts across more than 150 organizations. This highlights ongoing efforts by attackers to compromise the most privileged identities in cloud environments.

The campaign ran from July 24 to August 23, 2026, and involved multiple failed authentication attempts against AWS root accounts. Most affected organizations recorded a median of two attempts. In comparison, some experienced as many as eight attempts during the month-long activity period.

Datadog Security Researchers have not identified any successful logins associated with this campaign, leaving the attackers’ ultimate objective unclear.

However, compromising an AWS root account could grant an intruder unrestricted access to an organization’s cloud resources, billing data, account configurations, and other sensitive administrative functions.

Password Spraying Attacks Against AWS

The observed activity utilized a broad, proxy-backed infrastructure to tunnel authentication requests. Source IP addresses were spread across numerous countries and autonomous systems, with threat intelligence services classifying them as hosting infrastructure, residential proxies, or similar anonymization services.

This architecture makes IP-based blocking less effective and complicates attribution. Furthermore, Datadog did not find any obvious pattern in the victimology: the targeted organizations operated across various industries and geographic regions, suggesting opportunistic targeting rather than a campaign focused on a specific sector.

Two browser user-agent strings were consistently associated with the login attempts:

  • Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/85.0.4183.83 Safari/537.36 Edg/85.0.564.41
  • Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:120.0) Gecko/20100101 Firefox/120.0

A notable characteristic of this activity is that a failed AWS ConsoleLogin event for the root user requires the email address tied to that account.

This suggests that the threat actor may already possess a list of root account email addresses, potentially gathered from prior breaches, exposed records, open-source intelligence (OSINT) collection, or credential datasets.

Alternatively, the attackers could be testing a broader list of known corporate email addresses until they identify accounts registered as AWS root users.

AWS Root User Sign in page (Source: DataDog)

Using password spraying, testing a limited number of passwords across many accounts, allows attackers to evade conventional account-lockout controls typically associated with high-volume brute-force attacks.

AWS root users are particularly valuable targets because they hold complete authority over an account. Although AWS enforces multi-factor authentication (MFA) for root users and recommends monitoring all root activity, attackers may still target accounts where MFA enrollment is incomplete, recovery workflows are weak, or credentials have been previously exposed.

Security teams should review AWS CloudTrail logs for root ConsoleLogin events, both failed and successful attempts. A targeted query should filter for userIdentity.type:Root, eventName:ConsoleLogin, failed authentication results, and the identified Chrome/Edge and Firefox user agents.

Organizations should also set up alerts for:

  • Direct root-console sign-ins and root API activity
  • Changes to root credentials, MFA, and account recovery
  • Unusual source IPs, regions, or console destinations
  • Privileged sessions initiated through centralized root-access mechanisms

To reduce exposure, enterprises should eliminate persistent root user access wherever possible. The AWS Organizations service control policies can restrict direct root actions in member accounts.

In contrast, centralized root access can support short-lived AssumeRoot sessions for exceptional administrative tasks. Management-account root credentials require separate, tightly controlled protections.

Prevent incidents due to slow investigations. Power your Tier 1 with threat intelligence from 15K SOCs: Integrate TI Lookup in your SOC

Divya

Divya is a Senior Journalist at GBhackers covering Cyber Attacks, Threats, Breaches, Vulnerabilities and other happenings in the cyber world.

Recent Posts

Hackers Use ConnectWise SkyKick Credentials to Access Microsoft 365, Halting Cloud Backups

Attackers abused compromised ConnectWise Cloud Backup credentials to access Microsoft 365 customer environments, prompting ConnectWise…

21 hours ago

Anthropic’s Claude AI Uncovers Origins of NSA-Provided Cryptographic Keys After 25 Years

Anthropic says an internal Claude research model reconstructed how the National Security Agency generated seeds…

1 day ago

Critical WordPress Flaws Allow Attackers to Execute Remote Code Without Authentication

Two WordPress Core vulnerabilities can be chained to execute remote code without authentication, according to…

1 day ago

OpenBSD Kernel Flaw Dating Back 37 Years Enables Local Privilege Escalation to Root

A newly disclosed OpenBSD kernel exploitation chain combines a shared memory accounting flaw with a…

1 day ago

GhostAction Hackers Hide Credential-Stealing Malware in Fake Font Files Across 94 GitHub Repositories

GhostAction attackers have expanded their GitHub credential theft campaign with a second stage that disguises…

1 day ago

SideCopy Hackers Target Indian Organizations With ReverseRAT Malware to Steal Data

Indian authorities have warned that SideCopy hackers are targeting Indian organizations, including academic institutions, with…

1 day ago