The attacker first tested stolen credentials against one low-value Qubole role before moving quickly into every Qubole-trusted role across affected customer accounts.

Over 100 passwords and keys were read in seven minutes from three different places, including pulled secrets and reads of decrypted parameters.

Lambda environment variables and EC2 user data were harvested, so secrets stored in those locations should be treated as exposed and rotated immediately.

Thousands of credential records and files were downloaded, but the attacker performed zero write actions, so this was pure theft with no sabotage attached.

Access ran through a rented OVH server and the Mullvad VPN, and Sentra narrowed the activity to a handful of S3 buckets using matching leaked samples.

Credentials tied to Qubole's AWS account made sts:AssumeRole calls starting October 14, with further activity on October 15 and October 18 across multiple customer environments.

The attackers probed Lambda, Secrets Manager, and SSM Parameter Store, pulling keys and secrets, then copied whole S3 buckets without targeting specific data.

TruffleHog was used to test victim AWS credentials, discover Microsoft Entra ID secrets, and request OAuth tokens through Okta client credentials.

Wiz saw a separate campaign from October 8 to 11 using customer AWS access keys for Qubole integrations, linked to compromised environments but not confirmed as the same attack.

Researchers advise reviewing CloudTrail from October 1 for AssumeRole events where userIdentity.accountId matches 805246085872, then rotating every secret, parameter, and Lambda variable the role could read.

Exploitation requires OpenSSH running alongside musl, with PAM disabled and a passwordless account, and a password over 256 characters triggers the bug.

Greynoise tracks the attacking group as GT10, which ran mature intrusions against its real-time honeypots in Southeast Asia before the public fix shipped.

The backdoor TAC Agent supports shell command execution, system reconnaissance, and persistence, and its source contains Chinese-language comments suggesting AI-assisted generation.

Previdian recorded 20 exploitation attempts from 13 unique attacker IP addresses geolocated to nine countries within days of the vulnerability becoming public.

Attackers have been using the flaw for botnet recruitment and cryptocurrency activity, according to watchTowr, which saw exploitation tied to those campaigns across monitored systems.

Researchers found over 100,000 public GitHub repos containing Claude Code's local .claude/settings.local.json file, many of them uploaded without the developer noticing or intending it.

About 1,100 of those files contained live secrets such as API tokens, database passwords, and private keys, spanning 63 different organizations across the public web.

215 of the roughly 1,100 exposed secrets went undetected by gitleaks and TruffleHog, two widely used secret scanners that many teams rely on as their safety net.

The security flaw was reported in a Claude Code bug report in August 2025, but those reports were closed without action after 60 days of inactivity, per the researchers.

Secrets can persist in forks even after the original repo is cleaned, so anyone who cloned the project before the fix may still hold exposed credentials indefinitely.

Attackers may have accessed names, home addresses, and dates of birth of students and staff registered on the myTUM portal.

Student records exposed include ID numbers, degree programs, and completed semesters, which is exactly the data phishers love for targeted scams.

Employee records potentially exposed include work addresses and phone numbers for the university's 12,850 staff members across campuses.

Accounts protected by multi-factor authentication were shielded from the attack, so enabling MFA is the single most useful move right now.

TUM ranks first in Germany and 25th worldwide in QS rankings, serving 51,954 students across German campuses and TUM Asia in Singapore.

Topcoat is published on crates.io under an MIT licence, and the project has a public GitHub repository tracking the v0.9 release line.

The $(...) expression is evaluated on the server for the initial render and also translates to JavaScript, so it re-runs in the browser.

Topcoat UI is a shadcn/ui-inspired component library, and components get vendored into your project via the topcoat ui CLI command.

The roadmap lists authentication, background jobs, static export, and tighter Toasty integration as near-term work, with no dates committed.

Topcoat is explicitly not built for Figma-scale apps, targeting the run-of-the-mill, browser-based, database-driven applications most teams actually ship.