OFFSEC · Offensive Security

PEERSTITCH: a 2024 FortiManager compromise that outlived the patch

Unit 42 traces a FortiGate memory implant back to configuration theft through FortiJump in September 2024. The chain shows why management-plane incidents must be scoped from first exposure, not from the patch date.

The finding

A single compromised FortiManager gave an intruder the configuration, credentials and key material for more than 500 downstream FortiGate firewalls at a telecommunications managed service provider. Unit 42 published the case on 14 October 2026 and named the resulting implant PEERSTITCH [1]. The entry point was CVE-2024-47575, the FortiManager flaw disclosed and patched in October 2024 [1][7]. The intrusion began in September 2024 [1]. The lesson is not about one implant. It is that a management-plane compromise outlives the patch for the bug that caused it, and Unit 42 says so directly [1].

In Unit 42’s words: “That compromise also does not end when the platform is patched.” [1]

What the sources say

Unit 42 tracks the activity as CL-STA-0954 and links it to UNC5820, the cluster Mandiant named in 2024 [1][8]. According to Unit 42, the attackers registered a rogue virtual FortiGate with the central FortiManager and exfiltrated an archive of running configurations [1]. That archive held a 500-plus entry device inventory, administrator and SSL VPN credentials, certificates and private keys [1]. After an extended dwell period, which Unit 42 does not quantify, the attackers pushed packet-capture rules to downstream firewalls and used recovered credentials for VPN access [1].

The later phase used CVE-2025-61624, a path traversal flaw in the FortiOS command-line interpreter, to escalate to root and place PEERSTITCH on a select number of firewalls [1]. Unit 42 describes the implant at behaviour level as a one-shot injector that hooks the FortiOS logging and IKE daemons in memory, so that tagged VPN sessions take an alternate path that skips some validation [1]. Unit 42 states that it ‘leaves no persistent binary on disk, opens no listening ports and initiates no outbound network connections’ [1]. A second channel abused the certificate-renewal module of the device’s web server to keep a reverse shell alive [1][2]. The operators also killed logging processes, cleared crash logs and removed rogue accounts [1][3].

Unit 42 assesses with medium confidence that the attackers impersonated FortiManager to issue commands to managed firewalls, and that they deliberately degraded logging telemetry [1]. It says some post-exploitation activity overlaps with intrusions attributed to suspected nation-state actors, without making a firm attribution [1]. Its investigation covered the provider only. It did not examine the client networks behind the managed firewalls, so the client-side exposure is configuration and credential exposure, not confirmed intrusion [1].

Where the sources diverge

  • Use of the stolen data. In October 2024 Mandiant reported no evidence that UNC5820 had used the configuration data to move laterally, and said it lacked data to assess motivation or location [8]. Unit 42 now documents that the same data was used for credential recovery, VPN access and implant deployment [1]. The two accounts describe different stages and different victims; they are not in conflict, but the 2024 reassurance no longer holds as a general statement.
  • Credential protection. Mandiant described exfiltrated user passwords as FortiOS256-hashed [8]. Unit 42 says the administrator and VPN credentials in its case were stored as reversible ciphertext and recovered by brute force [1]. Defenders should not treat either description as a reason to delay rotation.
  • Severity of CVE-2025-61624. Fortinet scores it 6.0 with a local attack vector, temporal score 5.4 [4]. NVD scores it 6.5 with a network attack vector [5]. Trade reporting of the PEERSTITCH case gives 5.4 [2]. A Tenable scanner plugin lists the flaw as medium [6].
  • Exploitation status. Fortinet’s advisory, published 14 April 2026, marks the flaw as known exploited and credits internal discovery, without detail [4]. The Tenable plugin page states no known exploits are available [6]. Whether CVE-2025-61624 is in CISA’s Known Exploited Vulnerabilities catalogue could not be confirmed: the NVD record shows no KEV entry [5], neither press report mentions one [2][3], and the CISA catalogue could not be retrieved. Treat the KEV status as unverified.
  • Exposure scale. In October 2024 Tenable cited nearly 60,000 internet-facing FortiManager devices from Shodan [9]. Censys counted 4,081 exposed admin portals, roughly 86 per cent on the default FGFM port [10]. The figures measure different things and should not be compared directly.

Unit 42 does not give dates for the escalation phase [1]. Whether CVE-2025-61624 was a zero-day at the time it was used cannot be established from the published material.

What it means

The intrusion chain runs from a critical, unauthenticated management flaw to a medium-severity, authenticated CLI flaw. The second bug matters only because the first one delivered the administrator credentials it requires [1][4]. Severity scores rate bugs in isolation. They do not rate what an attacker already holds. A medium CVE on a firewall whose credentials sit in an exfiltrated archive is effectively a root primitive.

This is the third Fortinet case in eighteen months where access persisted after patching. In April 2025 Fortinet disclosed a symbolic-link technique that left read-only access on FortiGates after the original vulnerabilities were fixed [13]. Shadowserver counted more than 14,000 affected devices at the time, nearly 7,000 of them in Asia [14]. In June 2026 Fortinet attributed a credential-harvesting campaign to reuse of credentials from earlier incidents plus brute force against devices without MFA, and stated that it was not a new vulnerability [15]. The pattern is consistent: the residue of an old compromise, whether a link, a credential or a key, is the durable asset.

The same week shows the management plane remains the preferred target across vendors. Palo Alto Networks reported very limited exploitation of CVE-2026-0322, an authenticated code-execution flaw in the PAN-OS management interface, and advised restricting management access to trusted internal addresses [16].

For APAC operators the MSP angle is the material one. Regional service providers commonly run central managers for many customer firewalls. A provider-side compromise exposes every customer whose configuration that manager holds, even where no customer device was touched [1].

What to do

  • If any FortiManager ran a version affected by CVE-2024-47575 while reachable from untrusted networks, assume configuration theft. Fortinet’s own advisory says to assume data theft and rotate credentials for the manager and every managed device [7].
  • Rotate everything the manager held: administrator and local accounts, VPN pre-shared keys, certificate private keys, directory and RADIUS secrets, and routing and HA passwords [7]. Unit 42 notes exfiltrated trust material stays valid until rotated [1].
  • Patch CVE-2025-61624. FortiOS 7.0, 7.2 and 6.4 have no fixed release and must migrate to a fixed branch; a virtual patch exists for interim cover [4].
  • Hunt by behaviour, not hashes. Unit 42 lists memory, integrity, syscall, crash-log and configuration checks for FortiOS daemons, plus a YARA rule [1]. Unexplained crashes of logging daemons and auto-script objects with traversal strings are cheap starting points [1].
  • Isolate management. Restrict FGFM to known FortiGate addresses and deny unknown devices [7][11]. Keep administration off the internet, enforce MFA and remove legacy password settings [15].
  • Investigate history, not only state. Belgium’s CCB warned in 2024 that patching does not remediate a past compromise [12]. Logs from 2024 may already be gone, which is itself a finding to record.
  • MSPs should tell customers which configurations their managers held, so customers can rotate their own secrets.

Offensive security close

For red teams and vulnerability researchers the case is a reminder to model chains, not CVEs. The path from a management server to a firewall root shell crossed one critical bug and one medium bug, separated by credential recovery [1]. For defenders, the incident has to be scoped from the date the manager was first exposed, not from the date the patch went in.

Sources

Every R3KONX article cites its primary material. 16 sources, in order of first citation. Links open the original publication.

  1. Unit 42 Uncovers PEERSTITCH, a Stealthy FortiGate Implant Palo Alto Networks Unit 42 · 2026-10-14
  2. PEERSTITCH Malware Deployed via FortiOS Flaw Bypasses Checks on Tagged VPN Sessions The Hacker News · 2026-10-16
  3. New PEERSTITCH malware exploits Fortinet flaw for covert communication SC Media · 2026-10-16
  4. Path Traversal in CLI (FG-IR-26-122) Fortinet PSIRT · 2026-04-14
  5. CVE-2025-61624 Detail NIST National Vulnerability Database · accessed 2026-10-18
  6. Fortinet Fortigate Path Traversal in CLI (FG-IR-26-122), plugin 306463 Tenable · 2026-04-23
  7. Missing authentication in fgfmd (FG-IR-24-423) Fortinet PSIRT · 2024-10-23
  8. Investigating FortiManager Zero-Day Exploitation (CVE-2024-47575) Google Cloud / Mandiant · 2024-10-24
  9. CVE-2024-47575: Frequently Asked Questions About FortiJump Zero-Day in FortiManager and FortiManager Cloud Tenable · accessed 2026-10-18
  10. October 24 Advisory: Zero-Day in Fortinet FortiManager Seeing Active Exploitation (CVE-2024-47575) Censys · 2024-10-24
  11. Security Advisory 2024-113: Critical Vulnerability in Fortinet FortiManager CERT-EU · 2024-10-23
  12. Warning: Missing authentication in FortiManager being exploited, arbitrary code execution Centre for Cybersecurity Belgium · 2024-10-25
  13. Analysis of Threat Actor Activity Fortinet PSIRT · 2025-04-10
  14. Hackers lurk in over 14K Fortinet devices compromised using new attack method Cybersecurity Dive · 2025-04-14
  15. Analysis of Reported Credential Compromise of FortiGate Devices Fortinet PSIRT · 2026-06-19
  16. Palo Alto Networks Patches PAN-OS Flaw Exploited in Attacks The Hacker News · 2026-10-15

Researched and written by the R3KONX analysis desk from the cited primary material. Methodological caveat: the account of the intrusion rests on a single incident-response report covering one provider, without dates for the escalation phase, and the CISA KEV status of CVE-2025-61624 could not be confirmed. Corrections to event@r3konx.asia.

R3KONX 2027

Work in this domain? So does the programme

4–6 May 2027, World Trade Centre Kuala Lumpur. Curated talks, hands-on training and The BattleGrid.