Fulton County, Security Experts Call LockBit’s Bluff

The ransomware group LockBit told officials with Fulton County, Ga. they could expect to see their internal documents published online this morning unless the county paid a ransom demand. LockBit removed Fulton County’s listing from its victim shaming website this morning, claiming the county had paid. But county officials said they did not pay, nor did anyone make payment on their behalf. Security experts say LockBit was likely bluffing and probably lost most of the data when the gang’s servers were seized this month by U.S. and U.K. law enforcement.

The LockBit website included a countdown timer until the promised release of data stolen from Fulton County, Ga. LockBit would later move this deadline up to Feb. 29, 2024.

LockBit listed Fulton County as a victim on Feb. 13, saying that unless it was paid a ransom the group would publish files stolen in a breach at the county last month. That attack disrupted county phones, Internet access and even their court system. LockBit leaked a small number of the county’s files as a teaser, which appeared to include sensitive and sealed court records in current and past criminal trials.

On Feb. 16, Fulton County’s entry — along with a countdown timer until the data would be published — was removed from the LockBit website without explanation. The leader of LockBit told KrebsOnSecurity this was because Fulton County officials had engaged in last-minute negotiations with the group.

But on Feb. 19, investigators with the FBI and the U.K.’s National Crime Agency (NCA) took over LockBit’s online infrastructure, replacing the group’s homepage with a seizure notice and links to LockBit ransomware decryption tools.

In a press briefing on Feb. 20, Fulton County Commission Chairman Robb Pitts told reporters the county did not pay a ransom demand, noting that the board “could not in good conscience use Fulton County taxpayer funds to make a payment.”

Three days later, LockBit reemerged with new domains on the dark web, and with Fulton County listed among a half-dozen other victims whose data was about to be leaked if they refused to pay. As it does with all victims, LockBit assigned Fulton County a countdown timer, saying officials had until late in the evening on March 1 until their data was published.

LockBit revised its deadline for Fulton County to Feb. 29.

LockBit soon moved up the deadline to the morning of Feb. 29. As Fulton County’s LockBit timer was counting down to zero this morning, its listing disappeared from LockBit’s site. LockBit’s leader and spokesperson, who goes by the handle “LockBitSupp,” told KrebsOnSecurity today that Fulton County’s data disappeared from their site because county officials paid a ransom.

“Fulton paid,” LockBitSupp said. When asked for evidence of payment, LockBitSupp claimed. “The proof is that we deleted their data and did not publish it.”

But at a press conference today, Fulton County Chairman Robb Pitts said the county does not know why its data was removed from LockBit’s site.

“As I stand here at 4:08 p.m., we are not aware of any data being released today so far,” Pitts said. “That does not mean the threat is over. They could release whatever data they have at any time. We have no control over that. We have not paid any ransom. Nor has any ransom been paid on our behalf.”

Brett Callow, a threat analyst with the security firm Emsisoft, said LockBit likely lost all of the victim data it stole before the FBI/NCA seizure, and that it has been trying madly since then to save face within the cybercrime community.

“I think it was a case of them trying to convince their affiliates that they were still in good shape,” Callow said of LockBit’s recent activities. “I strongly suspect this will be the end of the LockBit brand.”

Others have come to a similar conclusion. The security firm RedSense posted an analysis to Twitter/X that after the takedown, LockBit published several “new” victim profiles for companies that it had listed weeks earlier on its victim shaming site. Those victim firms — a healthcare provider and major securities lending platform — also were unceremoniously removed from LockBit’s new shaming website, despite LockBit claiming their data would be leaked.

“We are 99% sure the rest of their ‘new victims’ are also fake claims (old data for new breaches),” RedSense posted. “So the best thing for them to do would be to delete all other entries from their blog and stop defrauding honest people.”

Callow said there certainly have been plenty of cases in the past where ransomware gangs exaggerated their plunder from a victim organization. But this time feels different, he said.

“It is a bit unusual,” Callow said. “This is about trying to still affiliates’ nerves, and saying, ‘All is well, we weren’t as badly compromised as law enforcement suggested.’ But I think you’d have to be a fool to work with an organization that has been so thoroughly hacked as LockBit has.”

from Krebs on Security https://ift.tt/kF589dZ
via IFTTT

LibreOffice 24.2.1, la primera actualización de mantenimiento tras el cambio de numeración llega con más de 100 bugs corregidos

LibreOffice 24.2.1

Tendré que acostumbrarme a la nueva numeración. De momento la he escrito dos veces, una para la imagen y otra para el titular, y me he equivocado las dos. Y es que hasta ahora se seguía una numeración de versión típica, subiendo el tercer número para las actualizaciones de mantenimiento, el segundo para las medianas y el primero en actualizaciones mayores, pero desde hace semanas se usa año y mes en los dos primeros. De ese modo, The Document Foundation acaba de hacer público el lanzamiento de LibreOffice 24.2.1 (y esta vez lo he escrito bien a la primera).

Las novedades de LibreOffice 24.2.1 están recogidas en los lanzamientos de su RC1 y RC2. En total se han corregido 102 bugs y regresiones que encontraron desde el lanzamiento de 24.2 RC3. En general, lo que se ha buscado ha sido mejorar la estabilidad y robustez de la suite, y se echa en falta leer que también han mejorado la compatibilidad con Microsoft Office, no tanto por lo que a uno le gustaría como por que es algo que han publicado muchas veces.

LibreOffice 24.2.1 no se recomienda para equipos de producción

Bien mirado, quizá sea mejor que no incluyan esa parte en la que nos hablan de lo que han mejorado las cosas con respecto a la compatibilidad con el Office de Microsoft. Mejor no dar falsas esperanzas, y lo que tenemos que hacer los usuarios es recomendar más LibreOffice y menos Microsoft 365.

Aunque ya está disponible LibreOffice 24.2.1, sigue sin ser la versión recomendada para equipos de producción. Esta, la del canal fresh, es para los que preferimos las novedades antes, pero en entornos de trabajo es mejor usar la anterior, actualmente 7.6.5. La serie 24.2 no será la opción recomendada al menos hasta que lancen la v24.2.5.

LibreOffice 24.2.1 ya se puede descargar desde la página web del proyecto para todos los sistemas soportados. Desde allí, los usuarios de Linux podemos descargar paquetes DEB y RPM, pero también está como paquetes flatpak y snap, ambos aún por actualizar.

from Linux Adictos https://ift.tt/FTywAjd
via IFTTT