Ransomgroup Helldown: Attacks on Zyxel Devices
defence1. Threat Actor
Helldown appears to be a new ransomware group active since August 2024, Truesec has performed a detailed analysis of the threat actor's emergence in a recent blog post.
Like other ransomware grops Helldown uses double-extortion in which victims not only get encrypted but also blackmailed and threatened data to be leaked. (Watchguard) Since the threat actor only appeared recently, there is not much more information, yet.
Helldown published data about Zyxel on 2024-08-21, which suggests that they compromised Zyxel in September/October 2024 (see attached screenshot of the TAs leaked-page).
2. Additional Information
Other institutions and security researches have observed similar attacks. (CERT.at, Borncity) Some also suggest that the threat actors exploit a yet "undocumented Zyxel flaw" (Darkreading), which fits our observation that the exploited systems were on the newest patch level (v5.39). The Zyxel vulnerability exploited by Helldown, as documented by Truesec, appears to match the one reported by a user on the Zyxel forum. It does not seem to align with any CVE currently listed by Zyxel.
Additionally, Sekoia, who appears to have access to part of the attack files, have observed new accounts being created in the firewall (e.g. “SUPPOR87,” “SUPPOR817,” or “VPN”). SEC Consult did not witness such behaviour of the attacker.
3. Defences
SEC Defence recommends, that companies running Zyxel firewall devices should:
- Ensure they are running the lastest version of the firmware (currently, this is v5.39 for the ATP device),
- proactively rotate their passwords, since there are indicators (Zyxel support) that there are vulnerabilities exposing passwords,
- monitor their firewalls (and firewall logs) for newly created users not matching the standard naming-convention of the organization,
- and to stay up to date with the recommendations and publications of Zyxel or the National CERTs.
To prepare for attacks, companies should:
- Collect their firewall logs, such as syslog, idealy on a centralized logging platform.
- If possible, secure the ingress point with a second firewall of a different vendor (intrusion-tolerant approaches).
This blogpost has been written by Dr. Michael Denzel und Tobias Weisskopf and published on behalf of SEC Defence.