Skip to content

Security Not yet confirmed elsewhere1 publisher 2 min read Published

ReversingLabs started from two Anthropic-published hashes and traced a Midnight Blizzard-linked campaign to new servers, lures and domains

ReversingLabs says it expanded the two file hashes in Anthropic's Midnight Blizzard report into a campaign map in five pivots. RL says Anthropic's appendix does not list the servers, lures and domain links it found.

The Watch · Security desk

How we use AI Send a correction

Illustration accompanying ReversingLabs started from two Anthropic-published hashes and traced a Midnight Blizzard-linked campaign to new servers, lures and domains
Generated illustration
RL had both seed files before either report When RL first observed the two seed files, when its platform classified them as malicious, and when Microsoft and Anthropic published.

Timeline: RL first observed the Go backdoor on July 6, 2026 and the PowerShell stager on July 10. Microsoft published on July 31, naming the files CornFlake and ChocoShell. RL's platform classified both files as malicious on August 1. Anthropic published its report on September 10.

RL had both seed files before either report
DateEventClaim
July 6, 2026RL first observes the Go backdoor16
July 10, 2026RL first observes the PowerShell stager16
July 31, 2026Microsoft publishes, naming the files CornFlake and ChocoShell17
August 1, 2026RL's platform classifies both files as malicious18
September 10, 2026Anthropic publishes its report19

What happened

  • Anthropic's report says the cluster it tracks as GTG-20006 went after more than 20 organizations in government, diplomacy, think tanks and the defense industry, most of them in Ukraine and Europe.
  • The Go backdoor first showed up in RL's data on July 6, 2026, and the PowerShell stager on July 10, before either Microsoft or Anthropic published.
  • The pivots returned the staging server, five more builds of it, two lure files, two files the server had served, and two links between phishing domains and servers.

Why it matters

  • exposure Defenders who loaded only the vendor lists are blind to the staging server and its other builds. Microsoft's report leaves out most of RL's finds as well.
  • decision A file-hash rule covers one build, and RL saw a new hash about every five days. Detection has to key on the server and the beacon path, which stayed fixed.
  • contradiction RL says it tracked the samples for weeks before Anthropic published, but its malicious classification is dated August 1, the day after Microsoft's report.

RL says it traced the campaign through what stayed the same from build to build: what each build had to do, and the server it had to talk to [3]. File hashes were a poor key. Five stager builds arrived with five different hashes in 25 days [1], an average of one new hash every five days [12]. Anthropic's appendix lists 209 indicators, but only two are file hashes [7].

Microsoft's CaptiveCrunch report does not include most of what RL found either [15]. The two vendors overlap on the seeds: both name the same two hashes and the same beacon path, along with four domains built to imitate Microsoft 365 and three servers that appear in both reports [9]. RL says every hash, URL, rule and query from its work is in an indicators section at the end of its post [20].

Microsoft published on July 31 and named the two files CornFlake and ChocoShell [17]. RL's platform classified both as malicious on August 1 [18], and Anthropic published on September 10 [19]. Counted from RL's first sight of the Go backdoor, those are 26 days to a verdict [22] and 66 days to Anthropic's report [23].

Attribution rests on the two vendors. Anthropic describes GTG-20006 as a Russian-speaking operator, with attribution "consistent with public reporting linking the actor to Midnight Blizzard" [4]. Microsoft, under the name CaptiveCrunch, assesses that Storm-2945 is "an operational sub-cluster of Midnight Blizzard" [8]. Midnight Blizzard is also tracked as APT29, Cozy Bear and NOBELIUM [11].

On the AI claim, confidence varies by source. According to Anthropic, the operator "used Claude to systematically identify, modify and redeploy the detected artifacts" when its implants were flagged [6]. Microsoft's wording was softer. It said the ChocoShell script "was authored with full developer comments" in a style that, in Microsoft's assessment, suggests the author might have used AI-assisted code generation [10]. RL says its data is consistent with Anthropic's finding [2].

In our view, five hashes in 25 days fits that account but does not show which tool made the changes.

What to watch

  • Whether Anthropic or Microsoft adds RL's staging-server, lure and domain-resolution indicators to their published lists.
  • Any stager build after September 10 with a new hash, which would extend the five-in-25-days pattern RL recorded.
  • A second source for the Claude rebuild claim, since Microsoft's published wording covers only code style.

Clarity's read

What the record supports and how the coverage leans. The claims behind it follow.

Reality

Evidence50
Adoption
Insufficient
Hype gap+10
Incentives60
Confidence55
Why these scores

Claim ledger

Ranked by verification strength, evidence, and original report placement.

  1. [1]

    Five builds of the stager, with five different hashes, reached RL in 25 days.

    Reported Supported Source: ReversingLabsView cited source
  2. [2]

    RL says its data is consistent with Anthropic's finding that the operator used Claude to rebuild implants once security products flagged them.

    Reported Supported Source: ReversingLabsView cited source
  3. [3]

    The builds changed, but what each build had to do and the server it had to talk to did not, and that is what made the campaign traceable.

    Reported Supported Source: ReversingLabsView cited source

Get this ledger inside ChatGPT. Ask about any of our stories and the answer brings its figure, each claim’s verdict and the sources. Free, no account.

Add to ChatGPTAdd to Claude

Sources

1 independent publisher whose own reporting we read for this story.

  1. reversinglabs.com

    1 article · October 15, 2026

    How RL mapped a Midnight Blizzard-linked campaign from two hashes

Share your take

Let Clarity write the post for you.

Signed-in readers get a short post drafted on this story in the register they choose — narrative, analytical, or a direct position — editable to the last word before it goes anywhere. The share buttons at the top of this story work without an account.

Topics and entities

Follow any of these and your For You feed starts watching them — no settings page required.

Topics

Loading related stories