Changed since version 13

• Source numbering changed. Unit 42 primary research is now S1, SecurityWeek S2, CISA KEV S3, CISA alert S4, The Hacker News S5, FortiGuard FG-IR-26-122 S6. Citations were updated throughout.
• Confidence set high: the Unit 42 primary source is now directly cited [S1].
• Added verify steps for 16KB rwxp regions, 0xAA0003E0 patches at named offsets, /proc/<pid>/mem audit, and Signal 11 crashlogs [S1].
• Added 47.18.167.159:8085/pM.js as a download source in the hunt meaning [S1].
• Added a scope enumeration item for sniffer configs and their capture ports [S1].
• Added an eradicate section listing artifacts to remove [S1].
• Noted that the SecurityWeek item could not be retrieved and corroborates nothing [S2].
• Added open questions on unsourced PAN signature IDs and inconsistent story dating.

What happened

• The actor exploited FortiJump (CVE-2024-47575) on a telecom MSP's FortiManager [S1].
• It registered a rogue Virtual FortiGate named localhost (FMG-VMTM23017412) and created a .tm config archive [S1].
• It took configs, credentials and keys for 500+ managed FortiGates [S1].
• It pushed sniffer configs and opened SSL-VPN sessions with cracked credentials [S1].
• It used CVE-2025-61624 auto-script path traversal (../../../../setup) to reach root [S1].
• It fetched five files from 23.240.77.233:8085 and ran PEERSTITCH. PEERSTITCH ptrace-injects into miglogd and iked to skip validation on tagged VPN sessions [S1].

Timeline

Detect

FortiGate auto-script objects with path traversal names · FortiOS system event / config change logs (syslog or FortiAnalyzer forward)

index=* devid=* type="event" subtype="system" (cfgpath="system.auto-script" OR msg="*auto-script*") (cfgobj="*../*" OR msg="*../*") | stats count min(_time) as first_seen max(_time) as last_seen values(action) as action values(cfgobj) as cfgobj values(msg) as msg by devname user ui

A hit means: An auto-script object with ../ in its name was created, edited or deleted. Unit 42 names ../../../../setup and ../../tmp/apache2/conf/md-acme.conf [S1]. Treat a hit as likely compromise. The actor deletes auto-scripts after use, so a delete event alone matters [S1].

Traffic, web or SSL-VPN sessions involving campaign infrastructure · FortiGate traffic, web filter and VPN event logs; proxy/egress logs

index=* (srcip IN ("23.240.77.233","47.18.167.159","45.32.41.202","198.199.122.22") OR dstip IN ("23.240.77.233","47.18.167.159","45.32.41.202","198.199.122.22") OR remip IN ("23.240.77.233","47.18.167.159","45.32.41.202","198.199.122.22") OR url="*/pM.js" OR (dstport=8085 (url="*/a.js" OR url="*/a.wasm" OR url="*/b.js" OR url="*/dd")) OR (dstport=8084 (url="*/acme/*" OR url="*/directory")) OR url="*/acme/new-acct*" OR url="*/acme/finalize/*" OR url="*/acme/order/*" OR url="*/acme/authz/*") | stats count min(_time) as first_seen max(_time) as last_seen values(dstport) as dstport values(url) as url values(action) as action values(user) as user by devname srcip dstip

A hit means: A device contacted campaign infrastructure. Fetches of pM.js from 23.240.77.233:8085 or 47.18.167.159:8085 match the component download [S1]. Port 8084 /directory and /acme/ paths match the mod_md SSH reverse-shell channel [S1]. Inbound SSL-VPN logins from these IPs match stolen-credential use [S1]. ACME paths alone can be benign if the peer is not a campaign IP.

Logging daemons killed, crashlogs cleared, or FortiGateCloud admin activity · FortiOS CLI audit and system event logs

index=* devid=* (msg="*killall*miglogd*" OR msg="*killall*syslogd*" OR msg="*crashlog clear*" OR user="FortiGateCloud") | stats count min(_time) as first_seen max(_time) as last_seen values(msg) as msg values(ui) as ui by devname user

A hit means: Someone stopped logging or cleared crash logs, which matches the reported anti-logging steps [S1]. An admin named FortiGateCloud pulling running configs over FGFM also matches the actor [S1]. Check each device's syslog stream for gaps too. A successful kill produces silence, not events.

Rogue Virtual FortiGate registration on FortiManager · FortiManager event / device management logs

index=* ("FMG-VMTM23017412" OR ("Virtual FortiGate" AND "localhost") OR ".tm") devid=* | stats count min(_time) as first_seen max(_time) as last_seen values(msg) as msg by devname

A hit means: The rogue Virtual FortiGate serial or name appears, or a .tm archive is referenced [S1]. Treat the FortiManager and every device it manages as in scope. Absence does not clear you; the actor may use other serials. The bare .tm term is noisy, so confirm by context.

Verify

• Pull config revisions on each FortiGate. Look for auto-script objects containing ../ and for admins or VPN groups created then deleted [S1].
• Run diagnose debug crashlog read. Signal 11 crashes in miglogd, iked or syslogd are a reported indicator [S1].
• pM.js deletes itself, so its absence does not clear a device. Check /data2/template/ for leftover components [S1].
• With vendor support, inspect /proc/<pid>/maps of /bin/miglogd and /bin/iked for anonymous 16,384-byte rwxp regions [S1].
• Check text at base+0x106F7B8, 0x1072E20 and 0x109A570 for 0xAA0003E0 patches. Also audit open/write on /proc/<pid>/mem between miglogd and iked [S1].
• Scan images with the Unit 42 YARA rule u42_apt_linux_PEERSTITCH_fortigate_implant. Compare files such as lldprx, ipssem.js, pM.js and index.wasm to the published SHA256 values [S1].

Scope

Affected

• FortiOS, FortiPAM, FortiProxy and FortiSwitchManager (CVE-2025-61624) [S4][S6]
• FortiManager (CVE-2024-47575), the initial access in this campaign [S1]
• FortiGates managed by a compromised FortiManager, whose configs and keys were exfiltrated [S1]

Only if

• CVE-2025-61624: the attacker is authenticated with an admin profile that has read-write permissions [S4]
• In this campaign, that access followed credentials and keys taken via the compromised FortiManager [S1]

Not affected if

None stated by the sources.

Fixed in: See Fortinet FG-IR-26-122 [S6]. Fixed versions are not stated in the provided material.

Enumerate

• Every FortiOS, FortiPAM, FortiProxy, FortiSwitchManager and FortiManager instance, with its running version.
• For each FortiManager: all registered devices, unknown Virtual FortiGates, .tm archives, and the FortiGates it manages.
• All admin accounts, VPN users and groups, including deleted ones visible in config revisions.
• Sniffer configs on FortiGates, especially those capturing TCP 3696-3706, UDP 69, 1812/1813 or TCP 389 [S1].
• Secrets stored in FortiGate configs: admin and VPN credentials, pre-shared keys, certificates, RADIUS/LDAP binds.
• Management and FGFM (TCP 541) exposure per device, and which hosts each FortiGate accepts management connections from.

Contain

• Before patching or rebooting, export config revisions, event logs and crash logs. With vendor support, capture memory of miglogd and iked, since PEERSTITCH lives there [S1]. A reboot destroys in-memory artifacts and cannot be undone.
• Block 23.240.77.233, 47.18.167.159, 45.32.41.202 and 198.199.122.22 at egress and for SSL-VPN [S1].
• Block outbound SSH from firewall management addresses unless it is required. The actor used mod_md to spawn SSH reverse shells [S1].
• Restrict management and FGFM access to known FortiManager and admin hosts. Remove internet exposure of FortiManager and admin interfaces.
• Disable unknown admins and VPN accounts. Remove unauthorized sniffer configs and rogue FortiManager device registrations [S1].
• If a FortiManager may be compromised, rotate every credential and key stored in FortiGate configs [S1]. Data already taken stays exposed after rotation.
• Apply FG-IR-26-122 and the FortiManager fix for CVE-2024-47575. Where patching lags, confirm FortiGuard virtual patch FG-VD-59270.0day (FMWP db 25.120) is in place [S6].

Eradicate

• Remove traversal auto-scripts, files under /data2/template/, and the mod_md md-acme.conf / job.json entries [S1].
• Remove the in-memory PEERSTITCH injection in miglogd and iked via vendor-guided rebuild or reimage, after evidence capture [S1].
• Remove rogue Virtual FortiGate registrations and the .tm archive from FortiManager [S1].
• Close the root cause by patching CVE-2024-47575 and CVE-2025-61624 [S4][S6].

Recover

• Before restoring, confirm patched firmware, a config that matches a known-good baseline, and rotated secrets [S6].
• Confirm syslog flows continuously from each device and crash logs are retained [S1].
• Confirm no 16KB rwxp regions remain in miglogd and iked [S1].
• Afterwards, keep the four hunts running. Alert on new auto-scripts, short-lived admins, sniffer config changes, outbound SSH from firewalls, unexpected FGFM peers and logging gaps [S1].

Re-enter the loop when

• Fortinet updates FG-IR-26-122 with fixed versions or new affected products [S6].
• New IoCs, hashes or actor infrastructure are published by Unit 42 or others [S1].
• A hit appears on any FortiGate not managed by the FortiManager first in scope.
• Evidence shows the actor used credentials from rotated configs after rotation.
• CVE-2024-26008 or CVE-2024-26009 gains a confirmed role in the chain.

Debrief

• Record each device, version, patch date, evidence captured and hunt results.
• Record which secrets were rotated and when, and any logging gaps found.
• Record VPN sessions that could not be validated, given the iked bypass [S1].
• Gap: no fixed versions in the provided material.
• Gap: the roles of CVE-2024-26008 and CVE-2024-26009 are not explained. One story calls CVE-2024-26008 an alias of FortiJump, which the sources do not support [S2].
• Gap: whether PEERSTITCH survives a reboot is not stated.

Detection coverage — checked automatically

Checked automatically 2026-11-01 04:33Z from public sources: 18 published, 27 nothing found, 0 not machine-checkable, 0 failed. "Nothing found" means the public source answered and had nothing, as of that moment; a feed covers only its newest posts. Re-checked daily.

Exposure queries — generated automatically

vuln:CVE-2024-47575

vuln:CVE-2024-26008

vuln:CVE-2025-61624

cpe:"cpe:/a:fortinet:fortimanager"

product:"Fortimanager"

host.services: (software.product = "Fortimanager")

cpe:"cpe:/a:fortinet:fortimanager_cloud"

product:"Fortimanager Cloud"

host.services: (software.product = "Fortimanager Cloud")

cpe:"cpe:/a:fortinet:fortiproxy"

product:"Fortiproxy"

host.services: (software.product = "Fortiproxy")

cpe:"cpe:/a:fortinet:fortiswitchmanager"

product:"Fortiswitchmanager"

host.services: (software.product = "Fortiswitchmanager")

http.title:"FortiProxy"

Internet-wide count, trend

Shodan's count of matching services on the whole internet, one point a day; the scope (your ranges) is never part of it. A count moves with Shodan's crawl as much as with patching, so read the direction, not the digit.

NVD names 2 more affected products (libraries and embedders); the CVE query covers them where Shodan has fingerprinted the version.

Banner spellings: a model read 6 from the NVD names and this card's text (former and marketing names, console titles); 1 matched something on Shodan and is shown above, the rest were dropped.

Scope every query in your own tool, never in a shared document: Shodan `net:<your_ranges>`, `org:"<your_org>"` or `hostname:<your_domain>` (or a Shodan Monitor network alert, which applies the scope for you); Censys `host.ip: <your_ranges>` or `host.dns.names: <your_domain>`. Then compare the banner version with the affected range. Generated automatically 2026-11-01 04:33Z from the CVE ids and NVD's CPE configurations, each Shodan query counted against Shodan itself; re-built daily with the coverage check.

Open questions

• Is CVE-2024-26008 actually related, or a misattribution? The stories call it an alias of FortiJump without support [S2].
• What role, if any, does CVE-2024-26009 play?
• Which FortiOS and FortiManager versions fix the issues?
• Does PEERSTITCH persist across reboot?
• The PAN signature IDs 95788 and 96788 in the guidance have no attributed source.
• Story dates are inconsistent: the 'today' item is dated 2026-10-15 but other items run to 2026-10-20, and the thread order is newest first. Confirm the brief date.

Sources

• [S1] https://unit42.paloaltonetworks.com/fortimanager-cve-2024-47575-peerstitch-malware/ · Unit 42
• [S2] https://www.securityweek.com/exploited-fortinet-bug-linked-to-stealthy-fortigate-implant-in-telecom-hack/ · SecurityWeek
• [S3] https://www.cisa.gov/known-exploited-vulnerabilities-catalog · CISA
• [S4] https://www.cisa.gov/news-events/alerts/2026/10/16/cisa-adds-two-known-exploited-vulnerabilities-catalog · CISA
• [S5] https://thehackernews.com/2026/10/attackers-exploit-fortios-flaw-to.html · The Hacker News
• [S6] https://fortiguard.fortinet.com/psirt/FG-IR-26-122 · FortiGuard Labs

Public OSINT only. AI-generated by the pipeline; structure follows the DAIR model from Dynamic Incident Response (Joshua Wright). Published automatically once it crosses the publish bar.