Password Spraying Campaign Targets AWS Root Accounts in Over 150 Organizations
A password spraying campaign targeted AWS root accounts across more than 150 organizations between July 24 and August 23, 2026. The attacks involved repeated login attempts against identities holding maximum privileges in the cloud.
The root account is created with every AWS account and provides complete access to resources, configurations, billing details, and sensitive administrative functions. A successful compromise could grant broad control over the entire environment.
Researchers recorded a median of two attempts per organization, while some targets received as many as eight attempts. No successful authentications connected to the campaign have been identified to date.
In password spraying, criminals test a small set of common or previously leaked passwords against many accounts. This approach reduces the volume of attempts per user and can evade traditional lockout mechanisms.
The attacks utilized proxies distributed across different countries and networks, including hosting infrastructure and residential proxies. Attackers also employed user agents simulating older versions of Microsoft Edge and Firefox.
To access a root account via the console, an attacker must know the associated email address. This suggests the operators may have obtained such information from prior leaks, reconnaissance, or by testing corporate email lists.
Since June 2025, AWS has required multi-factor authentication for root users, increasing the difficulty of account takeover even when a password is discovered. The company also recommends avoiding everyday use of the root identity and refraining from creating permanent access keys for it.
Related articles
T-Bank's wev.js Anti-Fraud Collector: Reverse Engineering Browser Fingerprinting for Bot Detection
A detailed reverse engineering of T-Bank's wev.js anti-fraud SDK reveals how the bank builds a persistent device fingerprint during debit card applications. The collector draws an invisible 2000x200 canvas with non-existent fonts and colored arcs, then hashes the result with SHA256 to create a stable device identifier called nf. It also captures twelve data blocks including compressed mouse and keyboard event streams, full WebGL renderer details such as UNMASKED_RENDERER exposing the Apple M4 Max chip, and sensor data from gyroscopes and accelerometers. Eight dedicated bot-detection checks target automation frameworks by inspecting navigator.webdriver, native code descriptors, and Safari-specific markers. Experiments showed that spoofing the GPU renderer leaves the nf hash unchanged, while deterministic canvas modifications can create a stable fake device fingerprint. A second collector, fp-pixel.js, runs on SSO pages and aggregates even more signals including audio, fonts, and WebRTC before sending data to a separate endpoint.
Scammers Impersonate Russian Traffic Police and Treasury Demanding Repeat Fine Payments
Russian scammers are sending SMS messages impersonating the State Traffic Inspectorate and the Federal Treasury, claiming that previous payments for traffic fines or state fees were not processed due to a system update. Recipients are instructed to pay the amount again or a small confirmation fee through a phishing link, with threats of accumulating debt if they refuse. The scheme was reported by the Moshilovka platform operated by the Narodny Front. Official agencies do not request repeated payments via third-party links or charge fees for transaction confirmations. Users are advised to verify payment status only through a verified Gosuslugi account and retain electronic receipts for any fees paid.
Scammers Abuse Google Looker Studio to Send Fraudulent Compensation Emails
Kaspersky researchers have identified a new wave of Russian-language phishing emails distributed through the legitimate Google Looker Studio service, formerly known as Google Data Studio. The messages promise compensation payments or confirm supposedly approved money transfers from financial institutions, using the platform’s scheduled report delivery feature to reach victims. Emails arrive from a genuine Google address and carry the official Data Studio branding, making them harder for security tools to block. Recipients are directed to open documents in Google Presentations or forms in Google Forms that reference fake legal changes and display state symbols before leading to scam sites. The campaign is limited to messages sent at the start or middle of each hour due to scheduling constraints in the service. Experts note that the abuse of trusted platforms increases the difficulty of automated detection and filtering.
Human-like Cursor Movements: Evading Behavioral Anti-Fraud Detection in Browser Automation
Anti-detect browser provider Aurorium explains how modern anti-fraud systems analyze mouse telemetry including coordinates, timestamps, velocity profiles, acceleration, curvature, and USB polling intervals to distinguish humans from automated scripts. Standard straight-line movements at constant speed with perfect center clicks trigger immediate alerts because they lack natural human motor patterns described by Fitts's law. The article details four key techniques to simulate realistic behavior: cubic Bezier curves with random control points for organic arcs, phased acceleration and deceleration with occasional overshoot, low-amplitude Gaussian jitter that fades near targets, and offset clicks distributed around element centers. It also stresses that JavaScript click() calls set the isTrusted flag to false, making server-side mouse events via Playwright or Puppeteer mandatory. A complete Python implementation using Playwright's page.mouse API is provided, incorporating normal distribution sampling and smoothstep easing. The guide concludes that realistic mouse mechanics must be combined with clean residential proxies and consistent browser fingerprints to remain undetected.