2023 · United States · O - Public administration and defence · Ransomware attack encrypting investigative and administrative files
Analysed 2026-11-06 by Hermes
Open this case in the tool →Ransomware attack encrypting investigative and administrative files
No DV evidenced
Alternative: none defensible
(1) The expectation at a police department holding criminal investigative records is that administrative file systems stay reachable and that an intrusion is contained and remediated without the department itself becoming dependent on recovery under extortion. (2) What the sources establish is impact and aftermath only: on 13 March 2023 ransomware encrypted many criminal investigative files and day-to-day internal administration systems, delaying some investigations; 911 and public-safety response services were not affected; by early April about 80-85 percent of files had been reopened, and the department said the attack had been overcome; the attackers demanded hundreds of thousands of dollars and the department never disclosed whether payment was considered; the incident became public only on 6 April 2023 through an NBC New York report based on anonymous law-enforcement officials, which the department's spokesperson confirmed as accurate; the FBI, the NJ Office of Homeland Security and the NJ Attorney General's office assisted, and the county retained outside cyber-law counsel. (3) No lifecycle stage yields a defensible victim-side mechanism: the entry vector is explicitly unconfirmed (one law-enforcement source told NBC that investigators were examining whether an employee had opened a malicious personal email on a department device, and later vendor analysis warns this should not be presented as a proven cause, so it is not load-bearing); how and when the department detected the intrusion is nowhere documented; no source reports data theft or exfiltration; recovery was completed by the department's own technicians and external IT and law-enforcement support with no documented backup or continuity shortfall; and while public acknowledgment came only after the media report roughly three weeks on, nothing in the reporting establishes the delay as inaccurate or concealed disclosure - the spokesperson's statements stayed within what the department's counsel allowed and caused no documented harm. Because reporting confirms impact only and the primary sources themselves leave the cause undetermined, the decision rule for Unknown applies; equally, the affirmative-alignment evidence 'No DV evidenced' requires is absent. (The case is not attacker-side, so Unknown rests on insufficient evidence, not atypicality.)
EuRepoC row: the case file's description says the hackers demanded thousands of dollars, but the NBC New York article it rests on reports sources describing a demand of hundreds of thousands of dollars - the row understates the figure. Two of the case file's source_url entries (The Record articles on Montclair NJ and a Coastal Mississippi county) are unrelated stories by the same reporter and were not used. The Camden County Prosecutor's Office was hit by a separate, unrelated cyberattack about a week later; per the police spokesman the two agencies do not share servers or networks (The Record, New Jersey 101.5). No ransomware group publicly claimed either attack and attribution remained open; whether a ransom was paid was never disclosed. The 2023 reporting never revealed a root cause, so this row's Unknown reflects the transparency of the record, not a research gap. Link check: tapinto.net blocks automated access (HTTP 403); the page was opened and read during research. Link check: databreaches.net blocks automated access (HTTP 403); the page was opened and read during research.