INTELLIGENCEReference · public sources
← Incidents

Incident reportPrivilege escalation toolingReport version 1 · November 21, 2026

Forest Blizzard GooseEgg post-compromise tool (CVE-2022-38028)

Microsoft documented GooseEgg, a post-compromise tool exploiting a Windows Print Spooler vulnerability, used against government, non-governmental, education and transportation organizations.

ReportedAttribution: Forest Blizzard (APT28)Reference data · public sources

01Executive assessment

  • ReportedGooseEgg has been used since at least June 2020 and possibly as early as April 2019. [1]
  • ReportedTargets included Ukrainian, Western European and North American government, non-governmental, education and transportation sector organizations. [1]

Implication: organizations in the affected sectors should confirm whether the access paths described in the sources apply to their own environment. A matching sector or technology is a reason to examine exposure, not evidence of compromise.

02What happened

Microsoft documented GooseEgg, a post-compromise tool exploiting a Windows Print Spooler vulnerability, used against government, non-governmental, education and transportation organizations.

Incident type
Privilege escalation tooling
Event period
June 2020
Date precision
month
Evidence basis
Vendor research publication
Sectors
Government, Non-governmental organizations, Education, Transportation

Since at least June 2020 and possibly as early as April 2019, as stated by the source.

03Evidence chronology

Publication dateDevelopmentTypeSource
April 22, 2024Microsoft publishes GooseEgg research and guidance.Research publication[1]

Event dates, source publication dates and our observation time (November 21, 2026) are recorded separately. Observation time is when DarkFire first collected the record, not when the activity occurred.

04Targets and geography

TargetRoleLocationPrecision and basis
Government, NGO, education and transportation organizations (unnamed)Campaign targetsUAcountry · Country named by the source

Regions named by the source: Western Europe, North America. Regional scope is shown in the list, not as map points.

Locations describe affected organizations or countries as stated by the sources. They never indicate where an attacker operates from.

05Attribution assessment

Attributed actor
Forest Blizzard (APT28)
Assessed by
Microsoft
Confidence
stated by source
Sources
[1]

DarkFire aggregates attribution published by the named assessing organization; it does not make its own attribution. Event evidence, actor attribution and location precision are separate judgments.

06Technical behavior

ATT&CKTechnique
T1068Exploitation for Privilege Escalation

Techniques listed here are the behaviors described for this incident, not the actor's full ATT&CK catalog.

EVIDENCEACTOR AND TECHNIQUESMicrosoft Threat IntelligenceApril 22, 2024APT28 / Fancy BearMicrosoftExploitation for Privilege Es…T1068Government, NGO, educat…

07Software and indicators

CVEProductCISA KEV listingRequired action
CVE-2022-38028Microsoft WindowsAdded April 23, 2024Apply mitigations per vendor instructions or discontinue use of the product if mitigations are unavailable.

A Known Exploited Vulnerabilities listing confirms exploitation in the wild in general. It does not identify victims of this incident.

08Business exposure and priorities

Organizations in government, non-governmental organizations, education, transportation should review whether they share the conditions described in the sources: the same technology, supplier relationships or access paths. Relevance is a reason to examine exposure, not a finding of compromise.

The APT28 dossier sets out defender priorities for this actor's documented behaviors.

09Defensive actions

Identify externally managed routers and mail systems, assign accountable owners, verify supported software and review administrative access. For relevant Windows devices, verify remediation of the Print Spooler issue. Prioritize a documented inventory of applicable systems and controls over an unqualified assertion that the organization is protected.

Review abnormal mailbox access, new application permissions, token use and endpoint changes together. Preserve original timestamps and supporting logs before remediation. Where compromise is confirmed, use the organization's incident-response process to contain access, revoke affected credentials and sessions, and investigate persistence. Establish explicit completion criteria for each action so that response decisions can be reviewed against evidence.

From the APT28 dossier. For each action, name a control owner, the supporting evidence and a completion criterion.

10Analytic gaps

  • The source does not name the affected organizations.
  • The core claims rest on a single publishing organization; independent corroboration has not been recorded.
  • Whether access persists at any affected organization is unknown unless newer evidence is published.

11Source notes and changes

  1. [1]Analyzing Forest Blizzard's custom post-compromise tool for exploiting CVE-2022-38028 to obtain credentialsMicrosoft Threat Intelligence · published April 22, 2024 · collected November 21, 2026

Version 1, published November 21, 2026. No corrections recorded. Report an error to have it reviewed; corrections and retractions keep the previous version visible.