El juego Californication de Red Hot Chili Peppers existe, es de un desarrollador español y funciona en Linux

Californication, el juego

En 1999 yo hacía tiempo que había descubierto a Metallica y hacía unos años que disfrutaba más del Thrash que de cualquier otro estilo musical. Tiempo antes era más de Nirvana o Iron Maiden, y nunca he sido fan de Red Hot Chili Peppers. Sí puedo decir que me llamó la atención una canción que daba nombre a un disco. Corría 1999, y la canción era más suave de lo que solían hacer. Pero llamaba la atención por dos cosas: la primera era el nombre, Californication, que incluía la palabra «fornicación», y la segunda era un videojuego en el que aparecían los componentes del grupo.

Aquel videojuego no era real. Era una animación en la que los Red Hot Chili Peppers se enfrentaban a todo tipo de situaciones, como volar por una ciudad, esquiar o huir de un autobús para que no les atropellara. Por aquellos tiempos aún no existía o acababa de lanzarse la PlayStation 2, y juegos como ese, con esos gráficos, aún no eran habituales. Hoy en día, esos gráficos no parecen gran cosa, pero, ¿y si lo hubiera hecho real un sólo desarrollador? Eso ha pasado, y el desarrollador es español.

Californication para Windows funciona con WINE

Nada más iniciar el juego vemos a un perrito dentro de un tanque y un nombre que delante tiene una arroba. Es la cuenta de Twitter de Miguel (@comandogdev), y a continuación vemos una pantalla que nos indica qué música va a sonar. Porque sí, el juego es uno como cualquier otro, pero siempre que lo hemos visto ha sonado de fondo Californication, por lo que la experiencia completa se consigue con esa canción de fondo. ¿El problema? Es evidente: los derechos de autor. Pero a Miguel se le ha ocurrido una manera de evitar problemas.

La canción no se incluye en el juego. El menú para elegir qué ponemos son enlaces a YouTube, por lo que nos saca momentáneamente del juego hasta que empezamos a reproducir la canción y volvemos a entrar. Es aquí en el único momento en el que yo he notado algo raro en Linux, pero es que no está disponible para nosotros. ¿Y por qué lo escribimos en Linux Adictos? Pues porque funciona perfectamente en Linux.

El juego está disponible gratis en este enlace para Windows y macOS. Es un ZIP de menos de 300mb que dentro tiene un EXE y algunos archivos más, pero lo importante es que, si tenemos instalado WINE, podremos jugar a Californication sin problemas.

Es gratis y compatible con mandos de juegos

La primera vez que lo iniciamos, es probable que WINE nos diga que no tiene algún paquete instalado, pero se acepta y más tarde podremos jugar a Californication. Como he mencionado, puede ser que al elegir la música de fondo y volver a entrar haya algo que no funcione, pero se puede cerrar, volver a abrir y, con la música ya sonando, la segunda vez elegir que no suene nada. También puede que tenga algo que ver algo de mi mando, que no funciona todo lo bien que podría (como podéis comprobar en el vídeo anterior, en el que he elegido un «cover» para evitar que YouTube me lo elimine).

El juego usa el motor Unity para moverse, y tenemos varios niveles para elegir. La mecánica es sencilla: tenemos que conseguir coger hasta cinco logotipos de Red Hot Chili Peppers antes de que se acabe la barra de nuestra vida. Se puede jugar con mando o con el teclado, y no hace falta aprender mucho para empezar a jugar. En la parte inferior de la pantalla tenemos un mapa que nos ayudará a saber dónde están los logos, los enemigos e incluso obstáculos. Vaya, que no le falta de nada.

Pero lo más importante de esta noticia son tres cosas: la primera, que el juego Californication es una realidad; la segunda, que lo ha creado un desarrollador español, quien lo ha añadido a su porfolio para promocionarse; y la tercera es que está disponible, bueno, que podemos jugarlo en Linux sólo con WINE. Os dejamos con el vídeo original de 1999 o 2000 (tengo dudas de cuándo salió).

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

Conti Ransomware Group Diaries, Part III: Weaponry

Part I of this series examined newly-leaked internal chats from the Conti ransomware group, and how the crime gang dealt with its own internal breaches. Part II explored what it’s like to be an employee of Conti’s sprawling organization. Today’s Part III looks at how Conti abused a panoply of popular commercial security services to undermine the security of their targets, as well as how the team’s leaders strategized for the upper hand in ransom negotiations with victims.

Conti is by far the most aggressive and profitable ransomware group in operation today. Image: Chainalysis

Conti is by far the most successful ransomware group in operation today, routinely pulling in multi-million dollar payments from victim organizations. That’s because more than perhaps any other ransomware outfit, Conti has chosen to focus its considerable staff and talents on targeting companies with more than $100 million in annual revenues.

As it happens, Conti itself recently joined the $100 million club. According to the latest Crypto Crime Report (PDF) published by virtual currency tracking firm Chainalysis, Conti generated at least $180 million in revenue last year.

On Feb. 27, a Ukrainian cybersecurity researcher who is currently in Ukraine leaked almost two years’ worth of internal chat records from Conti, which had just posted a press release to its victim shaming blog saying it fully supported Russia’s invasion of his country. Conti warned it would use its cyber prowess to strike back at anyone who interfered in the conflict.

The leaked chats show that the Conti group — which fluctuated in size from 65 to more than 100 employees — budgeted several thousand dollars each month to pay for a slew of security and antivirus tools. Conti sought out these tools both for continuous testing (to see how many products detected their malware as bad), but also for their own internal security.

A chat between Conti upper manager “Reshaev” and subordinate “Pin” on Aug. 8, 2021 shows Reshaev ordering Pin to quietly check on the activity of the Conti network administrators once a week — to ensure they’re not doing anything to undermine the integrity or security of the group’s operation. Reshaev tells Pin to install endpoint detection and response (EDR) tools on every administrator’s computer.

“Check admins’ activity on servers each week,” Reshaev said. “Install EDR on every computer (for example, Sentinel, Cylance, CrowdStrike); set up more complex storage system; protect LSAS dump on all computers; have only 1 active accounts; install latest security updates; install firewall on all network.”

Conti managers were hyper aware that their employees handled incredibly sensitive and invaluable data stolen from companies, information that would sell like hotcakes on the underground cybercrime forums. But in a company run by crooks, trust doesn’t come easily.

“You check on me all the time, don’t you trust me?,” asked mid-level Conti member “Bio” of “Tramp” (a.k.a. “Trump“), a top Conti overlord. Bio was handling a large bitcoin transfer from a victim ransom payment, and Bio detected that Trump was monitoring him.

“When that kind of money and people from the street come in who have never seen that kind of money, how can you trust them 1,000%?” Trump replied. “I’ve been working here for more than 15 years and haven’t seen anything else.”

OSINT

Conti also budgeted heavily for what it called “OSINT,” or open-source intelligence tools. For example, it subscribed to numerous services that can help determine who or what is behind a specific Internet Protocol (IP) address, or whether a given IP is tied to a known virtual private networking (VPN) service. On an average day, Conti had access to tens of thousands of hacked PCs, and these services helped the gang focus solely on infected systems thought to be situated within large corporate networks.

Conti’s OSINT activities also involved abusing commercial services that could help the group gain the upper hand in ransom negotiations with victims. Conti often set its ransom demands as a percentage of a victim’s annual revenues, and the gang was known to harass board members of and investors in companies that refused to engage or negotiate.

In October 2021, Conti underling “Bloodrush” told his manager “Bentley” that the group urgently needed to purchase subscriptions to Crunchbase Pro and Zoominfo, noting that the services provide detailed information on millions of companies, such as how much insurance a company maintains; their latest earnings estimates; and contact information of executive officers and board members.

In a months-long project last year, Conti invested $60,000 in acquiring a valid license to Cobalt Strike, a commercial network penetration testing and reconnaissance tool that is sold only to vetted partners. But stolen or ill-gotten “Coba” licenses are frequently abused by cybercriminal gangs to help lay the groundwork for the installation of ransomware on a victim network. It appears $30,000 of that investment went to cover the actual cost of a Cobalt Strike license, while the other half was paid to a legitimate company that secretly purchased the license on Conti’s behalf.

Likewise, Conti’s Human Resources Department budgeted thousands of dollars each month toward employer subscriptions to numerous job-hunting websites, where Conti HR employees would sift through resumes for potential hires. In a note to Conti taskmaster “Stern” explaining the group’s paid access on one employment platform, Conti HR employee “Salamandra” says their workers have already viewed 25-30 percent of all relevant CVs available on the platform.

“About 25% of resumes will be free for you, as they are already opened by other managers of our company some CVs are already open for you, over time their number will be 30-35%,” Salamandra wrote. “Out of 10 CVs, approximately 3 will already be available.”

Another organizational unit within Conti with its own budget allocations — called the “Reversers” — was responsible for finding and exploiting new security vulnerabilities in widely used hardware, software and cloud-based services. On July 7, 2021, Stern ordered reverser “Kaktus” to start focusing the department’s attention on Windows 11, Microsoft’s newest operating system.

“Win11 is coming out soon, we should be ready for this and start studying it,” Stern said. “The beta is already online, you can officially download and work.”

BY HOOK OR BY CROOK

The chats from the Conti organization include numerous internal deliberations over how much different ransomware victims should be made to pay. And on this front, Conti appears to have sought assistance from multiple third parties.

Milwaukee-based cyber intelligence firm Hold Security this week posted a screenshot on Twitter of a conversation in which one Conti member claims to have a journalist on their payroll who can be hired to write articles that put pressure on victim companies to pay a ransom demand.

“There is a journalist who will help intimidate them for 5 percent of the payout,” wrote Conti member “Alarm,” on March 30, 2021.

The Conti team also had decent working relationships with multiple people who worked at companies that helped ransomware victims navigate paying an extortion demand in virtual currency. One friendly negotiator even had his own nickname within the group — “The Spaniard” — who according to Conti mid-level manager Mango is a Romanian man who works for a large ransomware recovery firm in Canada.

“We have a partner here in the same panel who has been working with this negotiator for a long time, like you can quickly negotiate,” Trump says to Bio on Dec. 12, 2021, in regards to their ransomware negotiations with LeMans Corp., a large Wisconsin-based distributor of powersports equipment [LeMans declined to comment for this story].

Trump soon after posts a response from their negotiator friend:

“They are willing to pay $1KK [$1 million] quickly. Need decryptors. The board is willing to go to a maximum of $1KK, which is what I provided to you. Hopefully, they will understand. The company revenue is under $100KK [$100 million]. This is not a large organization. Let me know what you can do. But if you have information about their cyber insurance and maybe they have a lot of money in their account, I need a bank payout, then I can bargain. I’ll be online by 21-00 Moscow time. For now, take a look at the documents and see if there is insurance and bank statements.”

In a different ransom discussion, the negotiator urges Conti to reconsider such a hefty demand.

“My client only has a max of $200,000 to pay and only wants the data,” the negotiator wrote on Oct. 7, 2021. “See what you can do or this deal will not happen.”

Many organizations now hold cyber insurance to cover the losses associated with a ransomware attack. The logs indicate Conti was ambivalent about working with these victims. For one thing, the insurers seemed to limit their ability to demand astronomical ransom amounts. On the other hand, insured victims usually paid out, with a minimum of hassle or protracted back-and-forth negotiations.

“They are insured for cyber risks, so what are we waiting for?” asks Conti upper manager “Revers,” in a conversation on Sept. 14, 2021.

“There will be trades with the insurance company?” asks Conti employee “Grant.”

“That’s not how it works,” Revers replied. “They have a coverage budget. We just take it and that’s it.”

Conti was an early adopter of the ransomware best practice of “double extortion,” which involves charging the victim two separate ransom demands: One in exchange for a digital key needed to unlock infected systems, and another to secure a promise that any stolen data will not be published or sold, and will be destroyed. Indeed, some variation of the message “need decryptors, deletion logs” can be seen throughout the chats following the gang’s receipt of payment from a victim.

Conti victims were directed to a page on the dark web that included a countdown timer. Victims who failed to negotiate a payment before the timer expired could expect to see their internal data automatically published on Conti’s victim shaming blog.

The beauty of the double extortion approach is that even when victims refuse to pay for a decryption key — perhaps because they’re confident they can restore systems from backups — they might still pay to keep the breach quiet.

“Hello [victim company redacted],” the gang wrote in January 2022. “We are Conti Group. We want to inform that your company local network have been hacked and encrypted. We downloaded from your network more than 180GB of sensitive data. – Shared HR – Shared_Accounting – Corporate Debt – Departments. You can see your page in the our blog here [dark web link]. Your page is hidden. But it will be published if you do not go to the negotiations.”

“We came to an agreement before the New Year,” Conti member “Skippy” wrote later in a message to the victim company. “You got a lot of time, more than enough to find any sum and fulfill your part of this agreement. However, you now ask for additional time, additional proofs, etc. Seems like you are preparing to break the agreement and flee, or just to decrease the sum. Moreover, it is a very strange request and explanation. A lot of companies pay such amounts without any problems. So, our answer: We are waiting for the above mentioned sum until 5 February. We keep our words. If we see no payment and you continue to add any conditions, we begin to upload data. That is all.”

And a reputation for keeping their word is what makes groups like Conti so feared. But some may come to question the group’s competence, and whether it may now be too risky to work with them.

On Mar. 3, a new Twitter account called “Trickbotleaks” began posting the names, photos and personal information of what the account claimed were top Trickbot administrators, including information on many of the Conti nicknames mentioned throughout this story. The Trickbotleaks Twitter account was suspended less than 24 hours later.

On Mar. 2, the Twitter account that originally leaked the Conti chat (a.k.a. “jabber”) records posted fresh logs from the Conti chat room, proving the infiltrator still had access and that Conti hadn’t figured out how they’d been had.

“Ukraine will rise!,” the account tweeted. “Fresh jabber logs.”

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

libguestfs: accede y modifica imágenes de disco de máquinas virtuales

libguestfs

Quizás no muchos conocen libguestfs, una biblioteca escrita en C y un conjunto de herramientas que te permiten acceder y modificar las imágenes de disco virtual empleadas en las máquinas virtuales. Además, podrás trabajar con varias plataformas de virtualización basadas en KVM de Linux, y las imágenes de las MV se montarán directamente sobre el host haciendo uso del módulo FUSE y con las herramientas guestmount/guestunmount.

Otro detalle positivo de libguestfs es que puede acceder a casi cualquier FS, o sistema de archivos, y eso incluye todos los de Linux (ext2, ext3, ext4, XFS, btrfs,…), los de MS Windows (VFAT y NTFS), los de macOS (HFS y HFS+), así como los de BSD, e incluso gestión de volúmenes LVM2. Todo eso tanto en MBR como en GPT.

En cuanto a los tipos de discos virtuales a los que puede acceder, pueden ser:

  • qcow2
  • VirtualBox .vdi
  • VMWare .vmdk
  • Hyper-V .vhd y .vhdx

También puede acceder y modificar archivos, dispositivos locales, imágenes ISO, tarjetas de memoria SD, o hacerlo de forma remota a través de protocolos como:

  • FTP
  • HTTP
  • SSH
  • iSCSI
  • NBD
  • GlusterFS
  • Ceph
  • Sheepdog
  • etc.

Por otro lado, libguestfs no necesita privilegios, lo que también resulta interesante. Gracias a este proyecto, tendrás varias herramientas de línea de comandos como guestfish, guestmount, guestunmount, virt-rescue para reparar las MV que no arrancan, virt-cat, virt-tar, etc.

libguestfs también actúa como una API para poder vincular programas de administración en diversos lenguajes de programación:

  • C
  • C++
  • Perl
  • Python
  • Ruby
  • Java
  • PHP
  • Haskell
  • Erlang
  • Lua
  • C#
  • etc.

También puedes usarlo desde scripts, lo que resulta muy práctico a la hora de administrar sistemas. Además, este proyecto de Richard Jones se puede instalar desde los repos de muchas de las distros conocidas de esta forma:

  • Debian/Ubuntu y derivados

sudo apt install libguestfs-tools

  • Fedora/CentOS/RHEL y derivados

sudo dnf install libguestfs

  • Arch Linux y derivados

sudo pacman -Sy libguestfs

Por cierto, si estás usando libvirt y tratas de invocar a alguna de las utilidades o herramientas incluidas en libguestfs, vas a recibir un error como este:


libguestfs: error: could not create appliance through libvirt.

La solución es tan simple como exportar una variable como «direct» así:


export LIBGUESTFS_BACKEND=direct

Más información – Sitio web oficial

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

Arch Linux y Manjaro trabajan para mejorar la gestión que hace el segundo de AUR

Manjaro trabaja con Arch Linux para mejorar la gestión de AUR

Hace unas semanas, la cuenta oficial de Manjaro en Twitter publicó algo que alteró a sus usuarios. Era un tweet que parecía normal, pero que terminaba recomendando los paquetes Flatpak para que se usara menos AUR, el repositorio de la comunidad de Arch Linux en donde se encuentran paquetes como el Chrome de Google, por poner un ejemplo. Hubo gente que respondió a aquel tweet diciendo directamente que usaban Manjaro/Arch Linux por AUR, y era difícil de creer lo que estábamos leyendo, pero todo tiene una explicación y parece que una solución.

El principio de la explicación es que hay usuarios que usan AUR un poco de más. Es decir, incluso instalan el software desde este repositorio de la comunidad de Arch Linux antes que desde los repositorios oficiales. Cuando las peticiones son pocas, no hay problema, pero Manjaro no es Arch Linux, y su rama estable se actualiza cada pocas semanas. Ese es parte del problema: cuando Manjaro lanza una versión estable, muchos tiramos de Pamac para actualizar, y Pamac actualiza todo lo que tiene disponible, paquetes de AUR incluidos. En esos momentos, Arch User Repository sufre, y Manjaro se lleva un pequeño tirón de orejas.

Arch Linux y Manjaro preparan soluciones

Tal y como explican en este y este otro enlace del GitLab de Arch Linux, están trabajando en un nuevo AURweb que mejoraría la gestión del tráfico. Por lo que leemos en el segundo enlace, una solución parece ser bloquear el User Agent de Pamac, con lo que el tráfico parece reducirse hasta una octava parte. Si Manjaro ha publicado que están trabajando con Arch Linux, no parece probable que la solución sea un bloqueo permanente, sino temporal, probablemente en los días en los que se lanza una versión estable. Si es esto último lo que deciden hacer, recibiríamos las actualizaciones estables como siempre, pero los paquetes de AUR se actualizarían en otro momento.

Se espera que pronto publiquen detalles más extensos, pero este trabajo conjunto entre «padre» e «hijo» hará que todos salgamos beneficiados.

La última versión estable de Manjaro se lanzó el pasado 27 de febrero.

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