Updated
Updated · Ars Technica · Nov 9
GT10 Exploits *sshole Flaw to Breach Linux Systems, Installing TAC Agent
Updated
Updated · Ars Technica · Nov 9

GT10 Exploits *sshole Flaw to Breach Linux Systems, Installing TAC Agent

2 articles · Updated · Ars Technica · Nov 9

Summary

  • Greynoise said GT10 is actively exploiting the newly disclosed *sshole vulnerability, carrying out “mature intrusions” against Linux honeypots in Southeast Asia within four days of the flaw becoming public.
  • *sshole stems from the interaction between OpenSSH and musl, letting attackers gain unauthenticated access to privileged accounts on affected Linux systems in seconds.
  • TAC Agent—the backdoor GT10 deploys—supports shell commands, reconnaissance and persistence, and the group is installing Python3 on compromised machines when needed to run it.
  • A server Greynoise accessed pointed to possible additional victims and showed tooling that included a backdoor with Chinese-language comments that appears to have been AI-generated.
  • OpenSSH has released a fix for the bug, which quickly raised fears of broad Linux compromise after its disclosure last Thursday.

Insights

With hackers rapidly weaponizing the sshole flaw, are your lightweight Alpine Linux containers secretly exposing privileged accounts to attackers?
How does a quirky interaction between OpenSSH and the musl library allow hackers to bypass authentication in seconds?

CVE-2026-123158: Anatomy, Exploitation, and Defense of the OpenSSH musl libc Authentication Bypass Impacting Alpine Linux and Cloud Containers

Overview

The CVE-2026-123158 vulnerability in OpenSSH was rapidly disclosed and patched after artificial intelligence agents were observed independently rediscovering such flaws within hours. Public exploit scripts and detection tools quickly removed technical barriers, increasing the urgency for organizations to patch. The flaw allowed attackers to bypass authentication on musl libc-based systems, especially Alpine Linux cloud images, by exploiting a logic error when an overlong password was sent to accounts with a '*' in /etc/shadow. This led to immediate root access via the default 'alpine' account and passwordless privilege escalation. Effective defense required not just patching and restarting services, but also shifting from static indicators to behavioral monitoring and careful log analysis.

...