ZeroHour
DashboardNewsCVEsExploitsIncidentsAIBriefAnalyticsEntitiesWatchlistIOCsAsk the feedSourcesFeeds & APIKiosk mode
Vendor

AWS

3 mentions in 7 days · 16 in 30 days · 18 total · first seen · last

Search everything

Timeline

Hackers abused Claude to extract secrets from 1.8M Android apps

Anthropic reports ShinyHunters, Midnight Blizzard, and GTG-10007 misused Claude to automate credential theft, malware operations, and espionage against dozens of victims.

Anthropic's threat report details how ShinyHunters member 'frkoo' ran a credential-harvesting pipeline on ten AWS EC2 workers that mass-downloaded and decompiled 1.8 million Android APKs, scanning for hardcoded secrets with TruffleHog. In one AI-assisted operation, an actor extracted 2,100+ Azure AD authentication tokens across more than 40 Microsoft tenants in roughly 34 hours, and ShinyHunters affiliates also stole AI API keys and breached a SaaS provider affecting about 200 downstream customers. Russian espionage group Midnight Blizzard used Claude Code skills to automate malware development, phishing, C2, and exfiltration against 20+ government and defense entities, rebuilding malware automatically when detected. Chinese-linked GTG-10007 ran autonomous vulnerability research that uncovered zero-days in a major endpoint security product and hit roughly 50 organizations with confirmed compromises; Anthropic disrupted the abuse and banned the accounts.

BleepingComputerupdated · 3d agofirst · 4d agoThreat actor in the wild 11 sources1

Hackers Can Turn Vulnerable LiteLLM AI Gateways Into Root Access and Cloud Credential Theft

Wiz found multiple LiteLLM AI gateway flaws, including a CVE-2026-59822 MCP auth bypass added to CISA KEV, enabling root code execution and cloud credential theft.

An internet scan of 3,074 exposed LiteLLM instances found 294 (9.6%) accepting the default sk-1234 master key and 191 (6.2%) requiring no authentication. CVE-2026-59822 lets a single-character Bearer token establish a valid MCP session via an OAuth2 fallback in versions before 1.84.0; the flaw is in CISA's Known Exploited Vulnerabilities catalog. CVE-2026-59821 allows Python code execution as root in the gateway container via unsanitized Custom Code Guardrails registration before 1.82.0-stable, and CVE-2026-35029 permits config changes leading to RCE and admin takeover. Admin access plus pass-through endpoints can reach cloud metadata services to steal IAM credentials.

GBHackers · 5d agoAI safety & security in the wild 4 sourcesCVE-2026-59822CVE-2026-59821CVE-2026-35029

AWS spent years rebuilding its routing control plane without taking the network down

AWS replaced its fragmented border-network routing control planes with a single unified system, improving convergence times by up to 96%.

AWS disclosed a multi-year live-network migration that consolidated independent routing control planes into one system spanning 39 regions, 123 availability zones, and 750+ points of presence. The redesign uses unidirectional route sharing, packet tunneling, and a single source of truth to eliminate routing loops and stale-path inconsistencies. AWS reports faster convergence (up to 96% improvement on some fabrics), fewer retries, and more predictable latency for services including CloudFront, Route 53, and Direct Connect.

Help Net Security · 6d agoOther

Product showcase: Doppler secures secrets for humans, pipelines, and AI agents

Doppler's secrets management platform centralizes credentials for engineers, CI/CD pipelines, MCP servers, and AI agents with runtime injection and dynamic secrets.

Doppler stores API keys, database URLs, tokens, and certificates in a single control plane and injects them at runtime, replacing .env files for human and machine identities including AI agents. It supports OIDC with short-lived identity tokens for Azure, AWS, and GCP, dynamic secrets scoped and time-boxed to single sessions, SCIM provisioning, 50+ integrations, and an MCP server that lets agents request configurations natively. Permissions are enforced at each layer so raw secrets stay out of logs, prompts, and model context, with versioning, rollback, SIEM log forwarding, and cloud or on-prem deployment.

Help Net Security · 7d agoTools

Your AI agent's system prompt is not a security control

AWS and SANS guidance says system prompts are not security controls; enforce user permissions at retrieval time and default-deny every agent tool invocation.

AWS VP Gee Rittenhouse and SANS fellow Eric Johnson, with three AWS security specialists, published agentic AI security guidance for organizations with agents running or under development. They recommend scoping queries to user permissions inside existing RBAC/ABAC systems and filtering results before the model's context window, noting prompts can be bypassed, ignored, or overridden. The guidance warns risk concentrates when one agent holds sensitive data access, external communication, and exposure to untrusted content, the vector for prompt injection, which OWASP ranks as the top AI application threat. It cites IBM 2025 research that ungoverned shadow AI added $670,000 to average breach cost, and prescribes 30-day behavioral baselines, Cedar or Open Policy Agent for default-deny tool invocation, and four-layer containment with automatic circuit breakers.

Help Net Security · 8d agoAI safety & security

Drowning in CVEs and thirsty for answers? Try CTEM

Sponsored Register piece argues traditional vulnerability management cannot scale with CVE volume and promotes Continuous Threat Exposure Management via Horizon3's NodeZero.

The sponsored article cites surging CVE volumes, CVSS triage shortcomings, NVD backlog, and AI-driven discovery accelerating an asymmetric vulnerability cycle. It outlines Gartner's five CTEM steps - scoping, discovery, prioritization, validation, and mobilization - and describes how Horizon3's NodeZero automated pentesting validates exploitable attack paths with evidence. Horizon3 says NodeZero uses a deterministic machine learning expert system rather than general LLMs, limiting generative AI to scoped tasks via AWS Bedrock.

The Register · Security · 12d agoIndustry

DuckDB stays open source while the team behind it goes to work for Amazon

DuckDB founders Hannes Mühleisen and Mark Raasveldt join AWS as DuckLabs is acquired; DuckDB and DuckLake remain open source under the DuckDB Foundation.

Amazon Web Services hired DuckDB creators Hannes Mühleisen and Mark Raasveldt through the acquisition of DuckLabs, the bootstrapped 30-plus-person Amsterdam company behind the in-process analytical database downloaded more than a million times a day. DuckDB, DuckLake, and Quack remain MIT-licensed open source under the nonprofit DuckDB Foundation, which holds the IP and continues stewardship; the team stays in Amsterdam with the founders keeping technical leadership. The Foundation will add a technical advisory board and open the extension stack so extensions signed by other developers and organizations run in DuckDB.

Help Net Security · 13d agoOther

The Collective Cyber Defense letter wrote your next vendor questionnaire

Op-ed argues the 200-company Collective Cyber Defense letter's three endorsed metrics should become standard vendor procurement questions.

More than 200 companies including Microsoft, Google, AWS, CrowdStrike, Anthropic and Okta signed an August 27 open letter calling for faster cyber defenses against AI-enabled attacks. The letter endorses three measurable metrics: coverage, containment speed, and verified remediation. The author turns those into five concrete procurement questions buyers should pose at vendor renewals, while noting the letter contains no deadlines, dollar figures or measurable targets.

CyberScoop · 14d agoIndustry

‘Watershed 250’ test program in Texas looks to private sector for water cybersecurity help

White House launches Watershed 250, a six-month Texas pilot using volunteer vendor cyber and AI tools to harden water utility defenses.

The Office of the National Cyber Director and Texas Cyber Command will oversee the six-month Project Watershed 250 pilot to improve water sector cybersecurity through industry-donated red teaming, system hardening and AI tooling. Twelve companies including Microsoft, Fortinet, Google Cloud, Palo Alto Networks, AWS, Cloudflare, Zscaler, Forescout, Abnormal AI and Dragos participated in the rollout. Officials cited recent attacks including an Iranian-backed campaign against 30 water systems in 12 states and a 2024 incident in Muleshoe, Texas. Some water-security professionals criticized the program as lacking dedicated funding.

CyberScoop · 15d agoPolicy & legal1

CISA Red Team Compromised Two Critical Infrastructure Orgs, One Detected Nothing

CISA red teams fully compromised two critical infrastructure orgs with similar tradecraft; one detected nothing, the other contained phishing within minutes.

CISA advisory AA26-237A, 'A Tale of Two SOCs,' describes two simultaneous red team assessments of a Government Services organization and a Water and Wastewater Systems organization, both compromised to the domain level. Organization A never detected the intrusion, enabled by default credentials, a misconfigured AD CS template (ESC1), cleartext credentials, non-expiring static AWS keys, and over-permissioned Entra ID applications. Organization B detected and isolated phishing within 2-20 minutes, though the red team still reached krbtgt via DCSync from cleartext SCCM credentials. CISA attributes the outcome gap to people and processes rather than the security tools themselves.

The Hacker News · 20d agoAdvisory

TruffleHog AWS Analyze reduces remediation time on leaked AWS credentials

Truffle Security launched TruffleHog AWS Analyze, which maps leaked AWS keys' permissions and role assumptions; research found 88% of 64,024 leaked keys still active.

Truffle Security announced TruffleHog AWS Analyze, a TruffleHog Enterprise feature that enriches leaked AWS credentials with identity, effective permissions, and role-assumption context to help teams assess blast radius and prioritize remediation, extending earlier coverage of SaaS and Google Cloud to AWS. Truffle Security research on 64,024 unique leaked AWS keys found 88% still active, a median exposure of five years, only 14% rotated, 84% with full administrator access, and 1 in 6 being root keys, including 929 keys AWS had flagged via its compromised-key quarantine policy that still authenticated. A scan of 7.6 petabytes of public AI training data on Hugging Face found 3,343 live AWS keys, over 900 of which could list S3 buckets holding at least 51.7 TB of private data.

Help Net Security · 21d agoTools

Researchers Uncover Thousands of Leaked AWS Keys

Truffle Security researchers discovered more than 9,000 publicly accessible and active AWS key pairs, creating credential exposure and account-takeover risks.

Truffle Security reported finding over 9,000 AWS key pairs that are simultaneously publicly accessible and active. Anyone retrieving such keys could potentially access the associated cloud resources without authentication. The finding underscores widespread secrets-hygiene failures in cloud environments and the risks of long-lived static credentials.

Infosecurity Magazine · 22d agoResearch

AWS makes it easier to spot firewall rules that have gone quiet

AWS Network Firewall added rule hit counts for stateful rules, letting teams identify unused rules and validate control effectiveness at no added cost.

AWS Network Firewall's rule hit count capability gives security teams visibility into which stateful firewall rules are matching traffic, helping identify unused or redundant rules and validate controls for compliance frameworks like PCI DSS 4.0 and DORA. The feature covers stateful rules in custom and managed rule groups, is enabled by default at no additional Network Firewall cost, and is available in all supported Regions except UAE and Bahrain. Data is surfaced in the Network Firewall dashboard's Top Rule Hits view and can be queried via CloudWatch Logs Insights or Amazon Athena.

Help Net Security · 22d agoTools

AWS limits AI agents’ data access, even when manipulated

AWS detailed propagating user authorization context through Bedrock AgentCore so downstream services enforce access controls even if the agent is manipulated via prompt injection.

AWS described an architecture for Amazon Bedrock AgentCore where user tokens and department claims are validated at runtime and propagated to DynamoDB, Bedrock Knowledge Bases, and Salesforce. Downstream services enforce authorization themselves, so a prompt-injected or buggy agent cannot retrieve data the user is not entitled to see. AWS demonstrated the pattern with a CRM use case separating Sales and Finance access and recommends IAM-backed knowledge bases for stricter isolation.

Help Net Security · 26d agoAI safety & security

Microsoft Tracks MacSync Stealer by Its Behavior, Not Its Domains

Microsoft correlates over 30 rotating domains to track MacSync Stealer, which steals passwords, SSH keys, wallets and AWS credentials.

Microsoft Defender Experts tracked MacSync Stealer, a macOS information stealer, by analyzing recurring behaviors rather than individual domains, linking over 30 domains to the campaign. The infection chain uses the ClickFix social engineering technique, tricking victims into pasting commands in Terminal, then uses curl, AppleScript, and native macOS tools to deploy the payload. The stealer targets Keychain data, browser passwords and cookies, SSH keys, AWS credentials, Kubernetes configurations, and Ledger and Trezor wallet data, staging data before exfiltration via chunked HTTP PUT requests. RST Cloud identified rapid C2 infrastructure replacement after initial public disclosure.

Security Affairs · 27d agoMalware

When an Attacker Meets a Group of Agents: Navigating Amazon Bedrock's Multi

Unit 42 red-teamed Amazon Bedrock multi-agent applications, demonstrating prompt-injection attack chains that leak agent instructions and invoke tools, mitigated by Bedrock Guardrails.

Unit 42 red-teamed Amazon Bedrock Agents' multi-agent collaboration in Supervisor and Supervisor with Routing modes. The demonstrated attack chain detects the operating mode, discovers collaborator agents, delivers attacker-controlled payloads, and can disclose agent instructions and tool schemas and invoke tools with attacker-supplied inputs. No vulnerabilities were found in Bedrock itself, and the built-in prompt attack Guardrail blocked the attacks when properly configured. The researchers collaborated with Amazon's security team and frame the findings as a broader prompt injection risk for LLM-based systems.

Palo Alto Unit 42 · 29d agoAI safety & security

CTM360 Uncovers Over 3,000 Recruitment Phishing URLs Using Browser-in-the

CTM360's RecruitTrap report documents 3,000+ recruitment phishing URLs using BitB windows to steal credentials and relay MFA.

CTM360 identified over 3,000 phishing URLs impersonating recruiters from more than 50 organizations across 14 sectors in the RecruitTrap campaign. Attacks use Browser-in-the-Browser popups with spoofed address bars to harvest Google and Facebook credentials and relay MFA prompts in real time. About 96% of pages used a Calendly theme, with infrastructure concentrated on AWS EC2 and hidden behind Cloudflare.

The Hacker News · Aug 15, 2026Phishing & fraud in the wild

153GB of stolen credentials surface after LiteLLM supply chain attack

153GB archive from the LiteLLM supply chain attack exposes secrets from about 2,500 companies, including AWS, Samsung, Cisco and Salesforce.

Hudson Rock obtained and analyzed a 153GB archive stolen in the LiteLLM supply chain attack, containing 433,909 files with secrets attributed to 2,488 corporate domains, including AWS, Samsung, Cisco, Salesforce, NVIDIA, Microsoft and Siemens. TeamPCP compromised Trivy on March 19, 2026, stole LiteLLM's PyPI publishing tokens through the build pipeline, and published malicious LiteLLM versions 1.82.7 and 1.82.8 on March 24. CloudSEK separately estimated close to 2,500 exposed organizations, and Kevin Beaumont confirmed the data is legitimate. Hudson Rock is running a global ethical disclosure effort and urges organizations to rotate secrets before the trove leaks publicly.

Help Net Security · Aug 13, 2026Data breach in the wild

Related CVEs

  • CVE-2026-598228.8<1%
    Unauthenticated MCP Endpoint Authentication Bypass in BerriAI LiteLLM
    BerriAI LiteLLM, a widely used self-hosted AI gateway and proxy server for calling LLM APIs, fails to properly authenticate requests to its MCP Streamable HTTP endpoint in versions prior to 1.84.0. An unauthenticated attacker can send a fabricated Authorization header that triggers an OAuth2 passthrough fallback, which replaces failed LiteLLM key validation with an empty UserAPIKeyAuth() object and lets the request reach MCP tooling without any valid LiteLLM key. Successful exploitation grants unauthenticated access to the gateway's MCP tooling with high confidentiality impact per the CVSS 4.0 score of 8.8, and public reporting describes attackers chaining LiteLLM weaknesses from authentication bypass to root code execution and cloud credential theft. Any organization running LiteLLM before 1.84.0 is affected, particularly gateways exposed to the internet. The flaw is confirmed exploited in the wild: CISA added it to the Known Exploited Vulnerabilities catalog on 2026-09-02, while EPSS currently estimates a 0.9% probability of exploitation in the next 30 days.
    · BerriAI LiteLLM all versions prior to 1.84.0 (fixed in 1.84.0) KEVmoderate
  • CVE-2026-350298.725%
    Broken Access Control in LiteLLM AI Gateway Enables Authenticated RCE
    CVE-2026-35029 is a broken access control flaw (CWE-863, CWE-425) in LiteLLM, an open-source proxy server (AI Gateway) for calling LLM APIs, in which the /config/update endpoint fails to enforce admin-role authorization in versions prior to 1.83.0. Any user who is already authenticated to the proxy can call this network-accessible endpoint without admin rights and modify the proxy configuration and environment variables. Through this, an attacker can achieve remote code execution by registering pass-through endpoint handlers that point to attacker-controlled Python code, read arbitrary server files by setting UI_LOGO_PATH and fetching the file via /get_image, and take over other privileged accounts by overwriting the UI_USERNAME and UI_PASSWORD environment variables; related security coverage also highlights that vulnerable LiteLLM gateways can be turned into root-level code execution and cloud credential theft. Any organization running a LiteLLM proxy older than v1.83.0 is affected, particularly deployments where non-admin users hold authenticated accounts. No public proof-of-concept or confirmed in-the-wild exploitation is known and the flaw is not in CISA KEV, but EPSS assigns a 25.1% probability of exploitation within 30 days (98th percentile), signaling elevated near-term risk.
    · LiteLLM proxy server (AI Gateway) all versions prior to 1.83.0; fixed in v1.83.0moderate
  • CVE-2026-598212.1<1%
    LiteLLM is a proxy server (AI Gateway) to call LLM APIs in OpenAI (or native) format.
    LiteLLM is a proxy server (AI Gateway) to call LLM APIs in OpenAI (or native) format. Prior to 1.82.0-stable, LiteLLM's Custom Code Guardrails production create and update paths did not apply the same sandboxing and validation used by the test endpoint, allowing a privileged user with access to create or update guardrails to submit custom Python code that executed in the LiteLLM proxy environment and could expose secrets available to the process. This issue is fixed in version 1.82.0-stable.
    · litellm litellm—

Appears with

vendor Microsoft 9vendor Cloudflare 3vendor Salesforce 2vendor Fortinet 2vendor Okta 2vendor Palo Alto Networks 2ai model Claude 2vendor Amazon 2vendor Cisco 2vendor Anthropic 2vendor LiteLLM 2vendor Google 2organization AWS 2organization CISA 2organization Truffle Security 2vendor Truffle Security 2
Entities are extracted by the model from each article. Watching an entity keeps it in this browser only (no account); the watchlist page and dashboard alerts use it.