2023 · United States · O - Public administration and defence · Ransomware attack with data exfiltration
Analysed 2026-11-06 by Hermes
Open this case in the tool →Ransomware attack with data exfiltration
Expertise to Leadership
Evidence coverage: 5/6 stages, weight 27/60
Decisive stage: entry (tie-break: pre-breach condition) · Alternative: Expertise to Execution
(1) As a municipal government, Montclair carried a clear expectation to keep basic authentication controls current: its own cyber-insurer JIF, the CISA and NJCCIC guidance quoted in reporting, and its own CIO all treated multi-factor authentication as an urgent requirement, and the MFA capability had been sitting unused inside the Office 365 subscription the township had paid for since 2017. (2) In practice the remedy never reached the systems: the CIO's funding requests went unanswered from January 21, 2022, the insurer's consultant repeated the demand on May 8, 2023 with a July 1, 2023 coverage deadline, and the funds offered in May 2023 were not enough - while the CFO said the IT department always had surplus funds. Between May 22 and June 1, 2023 attackers held access, exfiltrated files, encrypted the network and reached the township's backups, which could not be restored; the insurer paid $450,000 by July 10, 2023, and personal data of 17,835 individuals, known to be taken only from March 25, 2024, was notified in April 2024 against earlier assurances of no personal-data breach. (3) The entry vector itself was never officially disclosed and is not load-bearing; the classification rests on the entry-stage victim condition: the unacted-on knowledge originated with technical and operational specialists (the CIO's repeated emails and funding requests, the insurer's IT consultant, a former IT employee, sector guidance - material origin) and the chain broke at the decision and funding level that never responded, underfunded or deferred the purchase for six years (leadership break) - experts warned, leaders did not act, which is Expertise to Leadership. The recovery stage (backups present but not isolated from the intruder, so restore failed) is a genuine Expertise to Execution pattern and the post-breach stage that lost the tie-break to this pre-breach condition; the response stage shows a secondary Strategy to Leadership pattern in the inaccurate public narrative. Decisive stage: entry, chosen over the load-bearing recovery stage by the pre-breach tie-break. RM22 (Expertise to Leadership lens): leaders left township authentication unprotected by MFA for years contrary to the explicit advice of their own CIO and the insurer's consultants, who kept requesting exactly this control (causal role: Enabling). RM07 (Expertise to Leadership lens): the insurer's 2022 report calling MFA an urgent item, the consultant's May 2023 warning and the CIO's escalating emails reached the decision-makers and were disregarded, leaving the exposure to persist until the attack forced action (causal role: Perpetuating). RM31 (Expertise to Leadership lens): the resilience gap was tolerated - backups existed but remained within the attacker's reach instead of the isolated or offline arrangement experts treat as standard, and the township had to buy its data back because no restorable copy survived (causal role: Constraining). RM39 (Expertise to Leadership lens): leadership's public account minimised the incident - dual authentication announced as new protection without disclosing that none had existed, and assurances of no personal-data breach that the township's own April 2024 notification to 17,835 individuals contradicted (causal role: Constraining).
RM22 — Authentication / credential exposureRM07 — Risk signal / escalation suppressionRM31 — Resilience / backup preparedness gapRM39 — Breach notification / disclosure failureEntry vector officially undisclosed; whether MFA would have blocked this specific intrusion is unconfirmed (the CIO declined to answer when asked), so the entry gap is classified as load-bearing on the documented condition and expert assessment, with that open question reflected in the claims. The JIF 2022 audit report recommending MFA was withheld from public records by both the township and JIF; its content is known through the CIO's emails as documented by the Montclair Local investigation. The CIO and the CFO give conflicting accounts of why the funding never arrived; both accounts agree MFA was unfunded and unimplemented before the attack. EuRepoC's intelligence_impact field says no data breach/exfiltration, which the victim's April 2024 notification (PII of 17,835 individuals removed May 22 - June 1, 2023) contradicts; the notification governs. The victim is officially the Township of Montclair; the dataset names it City of Montclair. The $450,000 payment was negotiated by the insurer with a team of experts and voted by the governing body, so no marker is coded for the payment decision itself (RM42 exclusion). Row description matches its stated victim. Link check: northjersey.com blocks automated access (HTTP 402); the page was opened and read during research. Link check: oag.maryland.gov blocks automated access (HTTP 403); the page was opened and read during research.