INTELLIGENCEReference · public sources
← Incidents

Incident reportCyber incident (reported)Report version 1 · November 21, 2026

JPMorgan Chase service providers cyberattack

The incident list records a cyberattack at service providers of JPMorgan Chase; marketing data held by third parties may have been accessed.

ReportedAttribution: Not attributedReference data · public sources

01Executive assessment

  • ReportedThe incident list records a cyberattack at service providers of JPMorgan Chase; marketing data held by third parties may have been accessed. [1]

Implication: organizations in the affected sectors should confirm whether the access paths described in the sources apply to their own environment. A matching sector or technology is a reason to examine exposure, not evidence of compromise.

02What happened

The incident list records a cyberattack at service providers of JPMorgan Chase; marketing data held by third parties may have been accessed.

Incident type
Cyber incident (reported)
Event period
November 16, 2026
Date precision
day
Evidence basis
Incident aggregator entry
Sectors
Financial services

As stated by the cited reporting. Current collection, November 2026.

03Evidence chronology

Publication dateDevelopmentTypeSource
November 16, 2026JPMorgan Chase service providers cyberattack recorded.Aggregator entry[1]

Event dates, source publication dates and our observation time (November 21, 2026) are recorded separately. Observation time is when DarkFire first collected the record, not when the activity occurred.

04Targets and geography

TargetRoleLocationPrecision and basis
JPMorgan ChaseAffected organization, named by reportingNew York City, United Statescity · Organization headquarters, affected system location unspecified

Locations describe affected organizations or countries as stated by the sources. They never indicate where an attacker operates from.

05Attribution assessment

Attributed actor
Not attributed
Assessed by
No assessment
Confidence
unknown
Sources

DarkFire aggregates attribution published by the named assessing organization; it does not make its own attribution. Event evidence, actor attribution and location precision are separate judgments.

06Technical behavior

No incident-specific procedure evidence has been recorded yet.

Techniques listed here are the behaviors described for this incident, not the actor's full ATT&CK catalog.

EVIDENCEACTOR AND TECHNIQUESKonBriefingNovember 21, 2026JPMorgan Chase

07Software and indicators

No publicly shareable indicators are recorded for this incident.

08Business exposure and priorities

Organizations in financial services should review whether they share the conditions described in the sources: the same technology, supplier relationships or access paths. Relevance is a reason to examine exposure, not a finding of compromise.

09Defensive actions

No actor-level defensive guidance is linked.

From the dossier. For each action, name a control owner, the supporting evidence and a completion criterion.

10Analytic gaps

  • The core claims rest on a single publishing organization; independent corroboration has not been recorded.
  • Whether access persists at any affected organization is unknown unless newer evidence is published.

11Source notes and changes

  1. [1]Cyber attacks worldwide (incident list)KonBriefing · published November 21, 2026 · collected November 21, 2026

Version 1, published November 21, 2026. No corrections recorded. Report an error to have it reviewed; corrections and retractions keep the previous version visible.