Live threats
CriticalCritical Java4Shell (CVE‑2026‑114938) Enables Unauthenticated RCE on AVX‑512‑Enabled OpenJDK 17+ BreachJPMorgan, Visa & Mastercard Elite Cardholder Data Exposed in Third‑Party Marketing Vendor Hack Rule changeHHS finalizes HIPAA Privacy Rule changes, cutting access request deadline to 15 days DeadlineFrench court orders DNS resolver Quad9 to block sites, prompting its withdrawal from France CriticalGoogle Chrome Patches Six Critical Memory‑Safety Flaws, Two Discovered via AI BreachThird‑Party JavaScript Supply‑Chain Compromise Serves Malicious Code to Major Brands, Exfiltrating Payment Data Rule changeEFF warns of rising service outages linked to rapid AI-driven patching and urges backup and resilience measures HighInteger Underflow in libumqtt (CVE‑2026‑125132) Enables Remote DoS and Data Exposure
Updated 03:50 UTC All intelligence →
BREACH WATCH BRIEF High 🏦 Breach

Third‑Party JavaScript Supply‑Chain Compromise Serves Malicious Code to Major Brands, Exfiltrating Payment Data

A trusted third‑party CDN was hijacked, allowing attackers to serve malicious JavaScript that stole payment‑card details and cookies from visitors of banks, news sites, airlines and SaaS firms. The breach bypassed traditional code reviews because the victim sites never changed their own code. It underscores the importance of continuous third‑party risk monitoring for audit readiness.

SeverityHigh
Type🏦 Breach
ConfidenceHigh
ReportedNov 19, 2026
Financial Services & FinTech Financial Services Media & Publishing Airlines Software & SaaS Third-Party Dependency Supply Chain Attack
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

Attackers obtained admin access to a popular third‑party web‑service and modified the JavaScript that the service’s CDN delivered to customer sites. The altered script ran in visitors’ browsers, capturing payment‑card numbers, cryptocurrency wallet data, and readable cookies before sending them to attacker‑controlled servers. The compromise affected dozens of high‑profile domains without any direct breach of the victims’ own infrastructure.

Why it matters for trust and compliance

  • The incident highlights a control gap in third‑party script governance; continuous vendor oversight and strict CSP enforcement are essential to demonstrate control assurance across multiple frameworks.
  • Enable continuous monitoring of third‑party script inventories to provide defensible evidence for vendor‑risk assessments.
  • Map CSP and script‑control findings to audit requirements, showing proactive mitigation of supply‑chain exposure.

Who is affected

Financial Services Media & Publishing Airlines Software & SaaS

Recommended actions

  1. Create a comprehensive inventory of all external JavaScript assets and their owners.
  2. Implement a restrictive Content Security Policy that disallows unsafe‑eval, unsafe‑inline, and limits script‑src to vetted domains.
  3. Apply Subresource Integrity or self‑host stable libraries.
  4. Enforce MFA/SSO for vendor accounts that can publish code and require regular security attestations.
  5. Set up continuous monitoring for script hash changes and CSP violation reports.

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.