Live threats
HighCritical Nginx Memory‑Corruption Flaws (CVE‑2026‑123007 & CVE‑2026‑113425) Allow Unauthenticated Remote Code Execution BreachOpenAI Agents Hack Hugging Face Model Repository, Exposing AI Supply‑Chain Risks Rule changeCleveland mayor's office introduces ordinance to award Flock Safety $2M no‑bid contract expansion DeadlineFarm Credit Administration amends employee payroll system of records under Privacy Act, effective Nov 24, 2026 CriticalCritical Memory‑Corruption Flaw (Java4Shell) Enables Unauthenticated Takeover of OpenJDK Runtime BreachAttackers Compromise Microsoft’s Agent‑Framework PyPI Package to Harvest Cloud Credentials Rule changeCNIL and Groupe VYV publish "La Voix des jeunesses" report on youth conversational AI use CriticalCritical Java4Shell (CVE‑2026‑114938) Heap‑Corruption Vulnerability Threatens Java Applications; Cloudflare Adds WAF Rules
Updated 03:25 UTC All intelligence →
BREACH WATCH BRIEF High ☁️ Breach

Attackers Compromise Microsoft’s Agent‑Framework PyPI Package to Harvest Cloud Credentials

Threat actors published malicious versions of Microsoft’s agent‑framework package on PyPI, embedding a credential stealer that runs on every Python start and exfiltrates cloud keys. The breach highlights the need for continuous third‑party risk monitoring and evidence collection to satisfy control‑assurance requirements.

SeverityHigh
Type☁️ Breach
ConfidenceHigh
ReportedNov 18, 2026
Technology & SaaS Technology SaaS providers Cloud‑infrastructure customers Enterprises using Python‑based automation Third-Party Dependency
Check if you use it. This incident came through a third party or the supply chain. If the product or supplier is in your estate or your vendors', start with the questions to ask below.

What happened

On 17 Nov 2026, malicious versions 1.26.1 and 1.26.2 of Microsoft’s agent‑framework PyPI package were published, executing a credential‑stealer that harvested AWS, Azure, and GCP keys from infected hosts and sent them to attacker‑controlled servers.

Why it matters for trust and compliance

  • The incident demonstrates why organizations must continuously verify and monitor third‑party code, mapping directly to the control objective of vendor risk oversight and evidencing compliance readiness.
  • Enables continuous monitoring of third‑party package integrity as audit evidence.
  • Supports mapping of supply‑chain risk controls to multiple frameworks (e.g., NIST CSF, ISO 27001).

Who is affected

Technology SaaS providers Cloud‑infrastructure customers Enterprises using Python‑based automation

Recommended actions

  1. Remove compromised package versions and rotate any exposed cloud credentials.
  2. Adopt SBOM and signed‑package verification for all dependencies.
  3. Enable continuous monitoring of public repositories for unexpected updates.

Regulations library

Every US state privacy law, on one map

24 states have a comprehensive privacy law in the library, alongside the EU, UK, US federal and global laws: 102 in all, each explained in plain words with its sources. Select a state to see what applies there.

  • In force
  • Coming into force
  • Sector laws
AK ME VT NH WA ID MT ND MN IL WI MI NY RI MA OR NV WY SD IA IN OH PA NJ CT CA UT CO NE MO KY WV VA MD DE AZ NM KS AR TN NC SC DC OK LA MS AL GA HI TX FL

Get the Breach Digest

The incidents that matter for your vendors and your data, analyzed for practitioners, in one email.