2024 · United States · O - Public administration and defence · Data theft and extortion via intrusion into a vendor-managed benefits system (no encryption)
Analysed 2026-11-06 by Hermes
Open this case in the tool →Data theft and extortion via intrusion into a vendor-managed benefits system (no encryption)
Expertise to Execution
Evidence coverage: 4/6 stages, weight 36/60
Decisive stage: detection (clearest evidence) · Alternative: Strategy to Execution
(1) The expectation at the victim was a technical one: RIBridges, the integrated eligibility system holding Medicaid, SNAP, TANF and health-exchange data on much of the state's population, was run by Deloitte under contract with operational security tooling in place - a SIEM and antivirus telemetry managed by Deloitte, firewall alerting, and MFA asserted for production accounts; experts knew the remedies (triage outbound-transfer alerts, aggregate volume and VPN MFA logs, retain MFA event logs, monitor bulk egress). (2) In practice the actor used a compromised non-privileged account to enter the non-production VPN on 2 July 2024, escalated privileges, established a reverse proxy and RMM persistence on a domain controller, browsed 28 systems for five months and moved bulk files to external cloud storage between 11 and 28 November while the firewall recorded 397 large-outbound-transfer alerts from 15 systems that went unactioned; the intrusion surfaced only through the Brain Cipher leak-site posting of 4 December, the state ordered a shutdown on 13 December, and the data was leaked on 30 December, affecting 644,401 people. CrowdStrike found no ransomware execution. (3) This is an Expertise to Execution gap rather than merely weak security: the remedies were standard, the tooling was present and even fired - 397 alerts - but the operational chain did not realise what the expertise prescribed (alerts untriaged, key log sources not aggregated, MFA logs not retained), so a five-month dwell and a disproportionate exfiltration followed; the decisive stage is detection, where the primary forensic report documents both the material origin and the execution break, and no source shows leadership having decided, deferred or under-resourced these remedies (the how of the credential theft is undisclosed and not load-bearing). Containment, egress and entry point the same way; recovery and response show the opposite pattern (prompt shutdown, phased validated relaunch, early outreach), which keeps the case mixed. RM13 (Expertise to Execution lens): the state's technical teams could not verify what happened inside the vendor-managed RIBridges environment - the access path was a Deloitte credential, the SIEM and antivirus monitoring were Deloitte-run, and the forensic review itself depended on Deloitte-provided collections - so supplier-side assurance could not be validated on the victim side (causal role: Enabling). RM33 (Expertise to Execution lens): experts could not investigate or reconstruct because logs were missing: VPN MFA events and firewall volume data were never aggregated into the SIEM and MFA event logs were not retained, so CrowdStrike could not determine how the credentials were obtained or whether MFA was triggered (causal role: Obscuring). RM34 (Expertise to Execution lens): the available monitoring tooling was not configured, tuned or staffed to catch the activity: 397 large-outbound-transfer alerts over seventeen days were not acted on and a five-month intrusion was discovered via the attacker's own leak site rather than by detection (causal role: Obscuring). RM35 (Expertise to Execution lens): bulk egress monitoring did not function in practice - large transfers to external cloud storage proceeded from 15 systems for seventeen days undetected and uninterrupted, amplifying the impact to 644,401 individuals whose data was then published (causal role: Amplifying).
RM13 — Third-party / supply-chain trust boundaryRM33 — Logging / forensic-readiness gapRM34 — Monitoring / detection / alert-handling gapRM35 — Egress / exfiltration monitoring gapThe EuRepoC row labels the incident a ransomware attack starting 5 December 2024; the state-released CrowdStrike forensic report found no evidence of ransomware execution and dates first activity to 2 July 2024 - the 5 December date is when Deloitte notified the state, and the incident is a data theft and extortion case. Attribution: the dataset says Not attributed; Brain Cipher claimed responsibility on its leak site (4 December 2024) and Deloitte confirmed RIBridges was the affected client system; no official government attribution was found in the sources opened. Brain Cipher's own claims (domain controller reached in five minutes, weak default password, USD 23 million ransom demand) are unverified attacker claims and were not used for the classification. Victim taken as the State of Rhode Island, the owner of the RIBridges data, though the compromised environment was managed by Deloitte under contract. CrowdStrike found no evidence of lateral movement from RIBridges into the state-managed enterprise environment. Link check: admin.ri.gov blocks automated access (HTTP 403); the page was opened and read during research. Link check: admin.ri.gov blocks automated access (HTTP 403); the page was opened and read during research. Link check: governor.ri.gov blocks automated access (HTTP 403); the page was opened and read during research.