City Hall and municipal services disrupted
Hoboken, New Jersey, identified a ransomware attack early Nov. 27, 2024. Its initial public alert closed City Hall, suspended online city services, canceled that day’s municipal court session and halted street sweeping. Waste collection and recreation programs continued.
Police, city IT staff and outside specialists investigated and worked to restore services.
Services returned in stages
A Dec. 1 city update said most resident services were available online through third-party vendors. The parking utility planned to reopen its service window Dec. 2 with cash or check payments. Email and Wi-Fi restoration continued, and residents were directed to call city departments.
By Dec. 4, parking-window card payments and most staff email access had returned. Responses could be delayed, and Vital Statistics and Licensing remained reachable only by phone. That update did not establish full restoration of every system.
Later investigation identified personal information
In its May 23, 2025, notice, Hoboken said certain files were accessed without authorization between Nov. 26 and 27, 2024. The affected information varied by person and could include names with Social Security numbers, driver’s-license or state-identification numbers, or bank-account and routing numbers.
The city completed its file review March 12 and address research May 16. It said it had no reason to believe information had been misused at the time of the notice. A call center and complimentary monitoring and identity protection were offered.
Those review and notification milestones are distinct from operational recovery. The notice does not provide a final affected-person count.
Attribution remains qualified
The Record reported Dec. 5 that ThreeAM claimed responsibility and listed the city on its leak site. That is an attacker claim, not city-confirmed attribution. The reviewed city notices do not establish a ransom payment or independently confirm the claim’s data-theft assertions.
Current assessment
The incident is presumed resolved because the last directly verified operational limitations were documented Dec. 4, 2024. The reviewed sources do not establish an exact date when all affected systems were restored. Later investigation and notification dates do not extend the documented service disruption.