KrebsOnSecurity Hit With Near-Record 6.3 Tbps DDoS

KrebsOnSecurity last week was hit by a near record distributed denial-of-service (DDoS) attack that clocked in at more than 6.3 terabits of data per second (a terabit is one trillion bits of data). The brief attack appears to have been a test run for a massive new Internet of Things (IoT) botnet capable of launching crippling digital assaults that few web destinations can withstand. Read on for more about the botnet, the attack, and the apparent creator of this global menace.

For reference, the 6.3 Tbps attack last week was ten times the size of the assault launched against this site in 2016 by the Mirai IoT botnet, which held KrebsOnSecurity offline for nearly four days. The 2016 assault was so large that Akamai – which was providing pro-bono DDoS protection for KrebsOnSecurity at the time — asked me to leave their service because the attack was causing problems for their paying customers.

Since the Mirai attack, KrebsOnSecurity.com has been behind the protection of Project Shield, a free DDoS defense service that Google subsidiary Jigsaw provides to websites offering news, human rights, and election-related content. Google Security Engineer Damian Menscher told KrebsOnSecurity the May 12 attack was the largest Google has ever handled. In terms of sheer size, it is second only to a very similar attack that Cloudflare mitigated and wrote about in April.

After comparing notes with Cloudflare, Menscher said the botnet that launched both attacks bear the fingerprints of Aisuru, a digital siege machine that first surfaced less than a year ago. Menscher said the attack on KrebsOnSecurity lasted less than a minute, hurling large UDP data packets at random ports at a rate of approximately 585 million data packets per second.

“It was the type of attack normally designed to overwhelm network links,” Menscher said, referring to the throughput connections between and among various Internet service providers (ISPs). “For most companies, this size of attack would kill them.”

A graph depicting the 6.5 Tbps attack mitigated by Cloudflare in April 2025. Image: Cloudflare.

The Aisuru botnet comprises a globally-dispersed collection of hacked IoT devices, including routers, digital video recorders and other systems that are commandeered via default passwords or software vulnerabilities. As documented by researchers at QiAnXin XLab, the botnet was first identified in an August 2024 attack on a large gaming platform.

Aisuru reportedly went quiet after that exposure, only to reappear in November with even more firepower and software exploits. In a January 2025 report, XLab found the new and improved Aisuru (a.k.a. “Airashi“) had incorporated a previously unknown zero-day vulnerability in Cambium Networks cnPilot routers.

NOT FORKING AROUND

The people behind the Aisuru botnet have been peddling access to their DDoS machine in public Telegram chat channels that are closely monitored by multiple security firms. In August 2024, the botnet was rented out in subscription tiers ranging from $150 per day to $600 per week, offering attacks of up to two terabits per second.

“You may not attack any measurement walls, healthcare facilities, schools or government sites,” read a notice posted on Telegram by the Aisuru botnet owners in August 2024.

Interested parties were told to contact the Telegram handle “@yfork” to purchase a subscription. The account @yfork previously used the nickname “Forky,” an identity that has been posting to public DDoS-focused Telegram channels since 2021.

According to the FBI, Forky’s DDoS-for-hire domains have been seized in multiple law enforcement operations over the years. Last year, Forky said on Telegram he was selling the domain stresser[.]best, which saw its servers seized by the FBI in 2022 as part of an ongoing international law enforcement effort aimed at diminishing the supply of and demand for DDoS-for-hire services.

“The operator of this service, who calls himself ‘Forky,’ operates a Telegram channel to advertise features and communicate with current and prospective DDoS customers,” reads an FBI seizure warrant (PDF) issued for stresser[.]best. The FBI warrant stated that on the same day the seizures were announced, Forky posted a link to a story on this blog that detailed the domain seizure operation, adding the comment, “We are buying our new domains right now.”

A screenshot from the FBI’s seizure warrant for Forky’s DDoS-for-hire domains shows Forky announcing the resurrection of their service at new domains.

Approximately ten hours later, Forky posted again, including a screenshot of the stresser[.]best user dashboard, instructing customers to use their saved passwords for the old website on the new one.

A review of Forky’s posts to public Telegram channels — as indexed by the cyber intelligence firms Unit 221B and Flashpoint — reveals a 21-year-old individual who claims to reside in Brazil [full disclosure: Flashpoint is currently an advertiser on this blog].

Since late 2022, Forky’s posts have frequently promoted a DDoS mitigation company and ISP that he operates called botshield[.]io. The Botshield website is connected to a business entity registered in the United Kingdom called Botshield LTD, which lists a 21-year-old woman from Sao Paulo, Brazil as the director. Internet routing records indicate Botshield (AS213613) currently controls several hundred Internet addresses that were allocated to the company earlier this year.

Domaintools.com reports that botshield[.]io was registered in July 2022 to a Kaike Southier Leite in Sao Paulo. A LinkedIn profile by the same name says this individual is a network specialist from Brazil who works in “the planning and implementation of robust network infrastructures, with a focus on security, DDoS mitigation, colocation and cloud server services.”

MEET FORKY

Image: Jaclyn Vernace / Shutterstock.com.

In his posts to public Telegram chat channels, Forky has hardly attempted to conceal his whereabouts or identity. In countless chat conversations indexed by Unit 221B, Forky could be seen talking about everyday life in Brazil, often remarking on the extremely low or high prices in Brazil for a range of goods, from computer and networking gear to narcotics and food.

Reached via Telegram, Forky claimed he was “not involved in this type of illegal actions for years now,” and that the project had been taken over by other unspecified developers. Forky initially told KrebsOnSecurity he had been out of the botnet scene for years, only to concede this wasn’t true when presented with public posts on Telegram from late last year that clearly showed otherwise.

Forky denied being involved in the attack on KrebsOnSecurity, but acknowledged that he helped to develop and market the Aisuru botnet. Forky claims he is now merely a staff member for the Aisuru botnet team, and that he stopped running the botnet roughly two months ago after starting a family. Forky also said the woman named as director of Botshield is related to him.

Forky offered equivocal, evasive responses to a number of questions about the Aisuru botnet and his business endeavors. But on one point he was crystal clear:

“I have zero fear about you, the FBI, or Interpol,” Forky said, asserting that he is now almost entirely focused on their hosting business — Botshield.

Forky declined to discuss the makeup of his ISP’s clientele, or to clarify whether Botshield was more of a hosting provider or a DDoS mitigation firm. However, Forky has posted on Telegram about Botshield successfully mitigating large DDoS attacks launched against other DDoS-for-hire services.

DomainTools finds the same Sao Paulo street address in the registration records for botshield[.]io was used to register several other domains, including cant-mitigate[.]us. The email address in the WHOIS records for that domain is forkcontato@gmail.com, which DomainTools says was used to register the domain for the now-defunct DDoS-for-hire service stresser[.]us, one of the domains seized in the FBI’s 2023 crackdown.

On May 8, 2023, the U.S. Department of Justice announced the seizure of stresser[.]us, along with a dozen other domains offering DDoS services. The DOJ said ten of the 13 domains were reincarnations of services that were seized during a prior sweep in December, which targeted 48 top stresser services (also known as “booters”).

Forky claimed he could find out who attacked my site with Aisuru. But when pressed a day later on the question, Forky said he’d come up empty-handed.

“I tried to ask around, all the big guys are not retarded enough to attack you,” Forky explained in an interview on Telegram. “I didn’t have anything to do with it. But you are welcome to write the story and try to put the blame on me.”

THE GHOST OF MIRAI

The 6.3 Tbps attack last week caused no visible disruption to this site, in part because it was so brief — lasting approximately 45 seconds. DDoS attacks of such magnitude and brevity typically are produced when botnet operators wish to test or demonstrate their firepower for the benefit of potential buyers. Indeed, Google’s Menscher said it is likely that both the May 12 attack and the slightly larger 6.5 Tbps attack against Cloudflare last month were simply tests of the same botnet’s capabilities.

In many ways, the threat posed by the Aisuru/Airashi botnet is reminiscent of Mirai, an innovative IoT malware strain that emerged in the summer of 2016 and successfully out-competed virtually all other IoT malware strains in existence at the time.

As first revealed by KrebsOnSecurity in January 2017, the Mirai authors were two U.S. men who co-ran a DDoS mitigation service — even as they were selling far more lucrative DDoS-for-hire services using the most powerful botnet on the planet.

Less than a week after the Mirai botnet was used in a days-long DDoS against KrebsOnSecurity, the Mirai authors published the source code to their botnet so that they would not be the only ones in possession of it in the event of their arrest by federal investigators.

Ironically, the leaking of the Mirai source is precisely what led to the eventual unmasking and arrest of the Mirai authors, who went on to serve probation sentences that required them to consult with FBI investigators on DDoS investigations. But that leak also rapidly led to the creation of dozens of Mirai botnet clones, many of which were harnessed to fuel their own powerful DDoS-for-hire services.

Menscher told KrebsOnSecurity that as counterintuitive as it may sound, the Internet as a whole would probably be better off if the source code for Aisuru became public knowledge. After all, he said, the people behind Aisuru are in constant competition with other IoT botnet operators who are all striving to commandeer a finite number of vulnerable IoT devices globally.

Such a development would almost certainly cause a proliferation of Aisuru botnet clones, he said, but at least then the overall firepower from each individual botnet would be greatly diminished — or at least within range of the mitigation capabilities of most DDoS protection providers.

Barring a source code leak, Menscher said, it would be nice if someone published the full list of software exploits being used by the Aisuru operators to grow their botnet so quickly.

“Part of the reason Mirai was so dangerous was that it effectively took out competing botnets,” he said. “This attack somehow managed to compromise all these boxes that nobody else knows about. Ideally, we’d want to see that fragmented out, so that no [individual botnet operator] controls too much.”

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

Red Hat Enterprise Linux 10 llega con nteligencia artificial y seguridad para los entornos híbridos

Red Hat Enterprise Linux 10

Red Hat ha lanzado oficialmente la versión 10 de su sistema operativo empresarial, Red Hat Enterprise Linux (RHEL), marcando un paso decisivo en la evolución del software enfocado a empresas que buscan gestionar infraestructuras modernas, seguras y adaptadas al auge de la inteligencia artificial (IA). Este lanzamiento llega tras varias filtraciones y la aparición anticipada de imágenes ISO en su portal de clientes, unos días antes del esperado anuncio en el Red Hat Summit 2025 de Boston.

La décima generación de RHEL no supone una simple actualización: introduce capacidades pensadas para automatizar, proteger y simplificar la gestión de sistemas híbridos, abriendo la puerta a despliegues más ágiles tanto en entornos locales como en la nube pública. El núcleo de las novedades gira en torno a la integración de IA, la seguridad avanzada y una nueva forma de gestionar el sistema basada en imágenes, en línea con las prácticas de los contenedores.

Red Hat Lightspeed y el impulso de la IA en la administración

Uno de los avances más llamativos es RHEL Lightspeed, un asistente que incorpora IA generativa directamente en el sistema. Este copiloto se presenta como una solución a la escasez de especialistas en Linux, permitiendo a los administradores, tanto veteranos como recién llegados, acceder a orientaciones y recomendaciones contextuales en lenguaje natural directamente desde la línea de comandos. Detrás de Lightspeed hay años de experiencia acumulada en entornos Red Hat, lo que traduce en ayuda concreta para resolver problemas habituales, sugerir buenas prácticas o planificar la evolución de la infraestructura. Red Hat busca con esto reducir los errores, aumentar la productividad y que cualquier perfil profesional pueda abordar la gestión de sistemas complejos con mayor confianza.

Seguridad avanzada en Red Hat Enterprise Linux 10

En el capítulo de seguridad, RHEL 10 destaca por integrar criptografía post-cuántica certificada por los estándares FIPS, una apuesta que anticipa el impacto potencial de la computación cuántica en la protección de datos empresariales. Se trata de implementar algoritmos resistentes a posibles ataques que podrían descifrar datos cifrados hoy en el futuro, junto a mecanismos para certificar la autenticidad e integridad de los paquetes y certificados TLS. Asimismo, Red Hat estrena el complemento Enterprise Linux Security Select Add-On, que permitirá solicitar correcciones específicas para un máximo de 10 vulnerabilidades (CVEs) al año, brindando más control sobre la seguridad del entorno y permitiendo adaptarse a necesidades concretas.

Nueva arquitectura de despliegue: modo imagen y gestión unificada

Otra novedad relevante es el denominado modo imagen, una aproximación que lleva la gestión basada en imágenes a todo el sistema operativo, no solo a las aplicaciones. Esta modalidad facilita la creación, despliegue y gestión del SO y los programas en un flujo de trabajo unificado, simplificando la administración y minimizando las discrepancias de configuración. Así, tanto desarrolladores como equipos de operaciones pueden utilizar la misma metodología, lo que reduce el tiempo de despliegue, el riesgo de errores y la fragmentación. Además, RHEL 10 viene con imágenes preconfiguradas, listas para funcionar en AWS, Google Cloud y Microsoft Azure, reforzando su apuesta por la nube híbrida.

Mejoras para desarrolladores y nuevas arquitecturas

Para los desarrolladores, Red Hat añade soporte para RISC-V en modo vista previa, en colaboración con SiFive, permitiendo experimentar y construir soluciones en una arquitectura que cada vez gana más presencia en la industria. Mediante el repositorio de extensiones de RHEL, también es ahora más sencillo acceder a software de la comunidad, como Podman Desktop. Por otra parte, Red Hat Insights amplía su capacidad predictiva, ofreciendo recomendaciones de paquetes mediante IA antes de los despliegues en producción, para que los equipos tomen decisiones informadas y detecten posibles problemas a tiempo.

Red Hat AI Inference Server: IA generativa a escala y sin ataduras

En sintonía con el auge de las tecnologías de IA, Red Hat refuerza su ecosistema lanzando Red Hat AI Inference Server. Esta solución, integrada con OpenShift AI y RHEL AI, aprovecha el proyecto vLLM para ofrecer inferencia de modelos de IA generativa sobre una amplia variedad de aceleradores de hardware y cualquier entorno de nube. La plataforma soporta modelos optimizados y comprimidos, permitiendo mejorar el rendimiento, reducir la latencia y hacer un uso más eficiente de los recursos. El repositorio gestionado por Hugging Face facilita el acceso a modelos validados y ajustados para IA, agilizando entre dos y cuatro veces la implantación de soluciones, según datos de la compañía. Además, con el proyecto comunitario llm-d, respaldado por nombres como Nvidia o Google, Red Hat busca escalar el servicio de modelos de lenguaje a múltiples usuarios en entornos empresariales complejos.

Cambios técnicos y de compatibilidad de Red Hat Enterprise Linux 10

En cuanto a compatibilidad y requisitos, RHEL 10 abandona definitivamente el soporte para arquitecturas x86 de 32 bits, exigiendo procesadores modernos compatibles con x86-64-v3 y extensiones AVX2, lo que implica que solo equipos relativamente recientes podrán usar esta versión. A nivel de escritorio, se elimina X.org y LibreOffice, apostando por GNOME bajo Wayland como única opción gráfica.

El sistema incorpora además una actualización importante del kernel, mejorando el soporte de hardware y el rendimiento general. Otras mejoras incluyen la gestión de archivos en la consola web, nuevos métodos de acceso remoto basados en RDP y la transición definitiva a PipeWire como servidor de sonido, reemplazando PulseAudio. Flatpak toma protagonismo para la instalación de aplicaciones de escritorio, y se optimiza la descarga de metadatos para ahorrar espacio. Además, los cambios en la gestión de paquetes y repositorios buscan un modelo más simple y directo, suprimiendo módulos en favor de paquetes no modulares.

Disponibilidad y acceso a Red Hat Enterprise Linux 10

Red Hat Enterprise Linux 10 ya puede descargarse desde el portal de clientes de Red Hat para quienes cuenten con una suscripción activa, mientras que los desarrolladores pueden acceder a la versión a través de los programas gratuitos de Red Hat Developer. Para quienes deseen probar la plataforma sin compromiso, se ofrece una edición de evaluación de 60 días.

La nueva versión de RHEL, junto con todo el entorno Red Hat AI y las soluciones presentadas en el Summit, refuerzan la apuesta de la compañía por facilitar el uso de IA generativa, ampliar la automatización y la seguridad, y simplificar la gestión de infraestructuras TI sin importar su escala o complejidad. Con este enfoque, Red Hat busca posicionarse como un referente para organizaciones que necesitan entornos flexibles, seguros y preparados para los retos tecnológicos del futuro.

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

PAHO and Spain’s Ministry of Health strengthen cooperation in organ, tissue, and cell donation and transplantation in the Americas

PAHO and Spain’s Ministry of Health strengthen cooperation in organ, tissue, and cell donation and transplantation in the Americas

Cristina Mitchell


from PAHO/WHO | Pan American Health Organization https://ift.tt/PdeLcfn
via IFTTT

Lanzamiento de APT 3.1: Nuevas Funciones y Mejoras en Debian y Ubuntu

APT 3.1

APT 3.1 acaba de presentarse como la última evolución de la herramienta de gestión de paquetes esencial para sistemas basados en Debian, marcando un nuevo hito tras la llegada previa de APT 3.0 a principios de abril. Esta nueva versión incorpora avances que afectan tanto a los usuarios de Debian como a los de Ubuntu, prometiendo más funcionalidades y mayor control en la administración de paquetes desde la línea de comandos.

Con la transición a APT 3.1, Ubuntu ha adoptado ya por defecto el nuevo solucionador de paquetes introducido previamente en la serie 3.0. Tras un periodo de pruebas y mejoras, los desarrolladores han considerado que el solucionador 3.0 ofrece la estabilidad suficiente como para reemplazar al anterior, lo que afectará directamente a la gestión y resolución de dependencias dentro del sistema.

APT 3.1 introduce comandos explicativos: «apt why» y «apt why-not

Una de las funcionalidades más comentadas de APT 3.1 es la inclusión de los subcomandos «apt why» y «apt why-not». Estas nuevas herramientas permiten a los usuarios indagar fácilmente sobre el motivo por el que se toma una determinada decisión con los paquetes. Inspirados en las utilidades equivalentes de Aptitude, mostrarán una traza del solucionador detallando por qué se instala, retiene o elimina un paquete concreto, ayudando a entender mejor la gestión del software en sistemas avanzados.

Mayor control sobre los repositorios

Otro aspecto significativo que llega con esta versión es la posibilidad de delimitar los paquetes que se emplearán de cada repositorio gracias a las nuevas opciones «Include» y «Exclude». Esta característica permite definir con precisión qué fuentes de software pueden o no ser utilizadas durante la instalación o actualización, lo que resulta especialmente útil en entornos con múltiples orígenes, versiones o repositorios personalizados.

Mejoras adicionales y ampliación del soporte

El equipo de desarrollo también ha aprovechado este lanzamiento para ampliar la compatibilidad con conexiones HTTPS en dselect, reforzando la seguridad en la gestión de descargas e instalaciones de paquetes. Además, se han corregido errores detectados y se han implementado pequeñas optimizaciones que redundan en una experiencia de usuario más fluida y fiable.

APT 3.1 está disponible en el canal Experimental de Debian, y se espera su llegada progresiva a otras ramas y distribuciones basadas en esta popular familia GNU/Linux. Para conocer todos los detalles y novedades sobre el desarrollo de APT, puede consultarse la web oficial de seguimiento de Debian.

Este lanzamiento aporta un avance en la madurez y versatilidad de la gestión de paquetes en sistemas basados en Debian, ofreciendo nuevas herramientas tanto para usuarios avanzados como para quienes desean un mayor control y transparencia durante la instalación o actualización de software en Linux.

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