Skip to content
Welcome, thoughtbot's Giant Robots listeners!Start here
Cybersecurity: Threats and Defences
5SEP

One firm hedged, heise online named APT28

3 min read
12:09UTC

ReliaQuest put the hotel campaign's initial-access route at low-to-medium confidence and named no state actor. heise online reported on 27 July that Russian state attackers were behind it and named APT28.

TechnologyDeveloping
Key takeaway

One publisher named a state actor the researching firm would not; treat the label as contested.

ReliaQuest assessed the route by which the hotel routers were compromised at low-to-medium confidence, and said visibility constraints stopped it confirming that route at all⁠1. Its candidate explanation is exposed Secure Shell, Simple Network Management Protocol and web administration interfaces paired with weak or reused administrative credentials. ReliaQuest does not name APT28. What it reports instead is tradecraft reuse overlapping a cluster it tracks internally as FrostArmada, while stating that the current activity differs from prior FrostArmada activity in several respects.

heise online, the German technology publisher, described the same campaign on 27 July as the work of Russian state attackers and named APT28 directly⁠2. APT28, also tracked as Fancy Bear and as Unit 26165 of Russia's military intelligence service, carries roughly two decades of published state-attribution history, and attaching that label converts a vendor's hedged finding into a geopolitical fact. The two accounts cannot both be reported as they stand: heise online states as established what ReliaQuest explicitly declines to confirm, and this briefing takes neither side.

The machinery under the disagreement rewards attention. FrostArmada exists as a cluster label only inside ReliaQuest, so no other firm can corroborate or contradict the overlap it reports, and the hedge cannot be tested from outside. A state attribution repeated onward from secondary coverage can reach an insurer's act-of-war exclusion, a policy clause the underlying vendor assessment would not support, and it can do so without anyone rereading the original.

When Russia's FSB Centre 16 hijacked network-management protocols on internet gear, the naming came from NCSC alongside 18 partner agencies on 9 July, with governments putting their own credibility behind it. Nothing of that kind has been published about the hospitality campaign, and until it is, the codename in circulation traces back to one publisher rather than to the firm that did the research.

Deep Analysis

In plain English

When a cybersecurity firm investigates who is behind an attack, it doesn't always reach a confident answer, and when news outlets summarise that research, some of that uncertainty can get lost along the way. Here, the firm that actually found the hotel-router campaign, ReliaQuest, says it can only guess with 'low-to-medium confidence' at how the routers were first broken into, and it does not name the well-known Russian hacking group APT28 as responsible. It only says the campaign resembles, in a rough way, a different, less-known cluster it tracks under its own internal codename. A German technology outlet, heise online, reported the story on 27 July describing it as Russian state hackers and naming APT28 directly, a firmer claim than ReliaQuest's own report supports.

Deep Analysis
Root Causes

ReliaQuest's hedge traces to a specific gap: the firm states visibility constraints prevented it from confirming which of the exposed management interfaces, SSH, SNMP or web-admin, actually served as the entry point, and it can only report tradecraft overlap with a cluster it tracks under its own internal name, not the publicly known APT28 designation.

Secondary reporting compresses that hedge because 'Russian state hackers' is a simpler sentence than 'a firm citing low-to-medium confidence overlap with an internally labelled cluster that itself differs from prior activity'. The compression happens in translation, not in the underlying research.

What could happen next?
  • Meaning

    Readers following named-actor attribution in cyber reporting should treat secondary coverage as potentially firmer than the primary research it cites, particularly when the primary source itself uses hedged confidence language.

  • Risk

    If APT28 attribution later proves wrong, the correction burden falls on secondary coverage that went further than the source research, not on ReliaQuest's own hedged assessment.

First Reported In

Update #12 · KEV deadlines fell from 14 days to three

ReliaQuest· 3 Aug 2026
Read original →
Different Perspectives
Hospital Sírio-Libanês
Hospital Sírio-Libanês
Hospital Sírio-Libanês said a 21 September attack reached a reporting system for its social projects, possibly exposing patients' and staff identity numbers and health information, while its general patient database was untouched. It notified the ANPD and the Polícia Federal and warned of fraud attempts.
The Foschini Group
The Foschini Group
The Foschini Group told the Johannesburg exchange on 13 October that an attack found on 11 October disrupted IT systems at its TFG London brands, while stores stayed open. It has not identified the attackers or established whether personal data was taken.
FirstVDS
FirstVDS
FirstVDS said attackers used a VMmanager 6 flaw to copy customers' passwords, cloud credentials and cryptocurrency wallets from beneath their virtual servers, and told notified customers to assume theft and rotate credentials. ISPsystem's flaw was not fully fixed on 19 October.
ESET
ESET
ESET says Russia-aligned UAC-0099 phished a Ukrainian grain logistics firm in July 2025 and apparently passed its access to GRU-linked Sandworm, which wiped the company's data that September. It treats the attackers' use of the Yggdrasil network as a first for a state-aligned actor.
JPCERT/CC
JPCERT/CC
JPCERT/CC issued emergency alert AT-2026-0032 on 14 October as EG Secure Solutions confirmed attacks on the SiteGuard Server Edition flaw. It told operators to save diagnostic data before updating, because the update may erase traces of the attack.
Cyber Security Agency of Singapore
Cyber Security Agency of Singapore
The Cyber Security Agency of Singapore said on 20 October that attackers are exploiting Ivanti Connect Secure, seven days after Ivanti's disclosure, having flagged PAN-OS exploitation on 16 October. It issued a PHP2Shell alert on 21 October, the day the fixes shipped.

Written with AI from Lowdown's published reporting. Not individually reviewed by an editor. Editorial standards.