tag: Edge-Devices · 3 items
- Engineer — Act: FortiGate and GlobalProtect are common enterprise fixtures; active access obtained at organizations worldwide means assume-breach posture is warranted now. Audit both platforms for unauthorized sessions or config changes, force credential rotation for all VPN users, and cross-reference your logs against any IOCs released by the researchers.
- SOC/IR — Act: This is a live campaign with confirmed access at multiple orgs — edge device compromise typically precedes patching, so run an assume-breach hunt now. Search SIEM for anomalous lateral movement sourced from your FortiGate or GlobalProtect IPs since at least early October, and monitor the researcher disclosure for IOC drops to build detection rules.
- Leader — Act: Seventy thousand exposed credentials across a worldwide enterprise campaign is a credible board-level event if your org runs either product. Confirm with engineering whether FortiGate or GlobalProtect is in scope, request a status report on credential exposure and any observed unauthorized access, and prepare a brief for leadership before this surfaces in mainstream press.
- Engineer — Act: Active exploitation of CVE-2025-61624 on FortiOS, FortiPAM, FortiProxy, and FortiSwitchManager is confirmed; patch all affected Fortinet products immediately and audit edge device logs for signs of PEERSTITCH deployment.
- SOC/IR — Act: Memory-resident malware on edge devices evades most endpoint controls — assume compromise if Fortinet appliances are in scope; hunt for anomalous outbound traffic or process anomalies on FortiOS devices and sweep for PEERSTITCH IOCs published with this campaign.
- Leader — Plan: Advanced actor activity against widely deployed Fortinet edge infrastructure warrants confirming this quarter whether all Fortinet appliances are patched and whether incident response runbooks cover memory-resident implants on network devices.
- Signals: CVE-2025-61624 — CISA KEV: not listed, EPSS 0.01, public PoC on GitHub
- Engineer — Plan: Mirai-derived malware is actively targeting internet-facing Linux edge devices using known vulnerabilities to establish SOCKS5 proxy infrastructure; audit your exposed edge device inventory for signs of compromise, ensure firmware/OS patches are current on routers, VPN appliances, and similar gear, and block unauthorized outbound SOCKS5 traffic at the perimeter.
- SOC/IR — Plan: No specific IOCs are published yet, but the Mirai lineage gives detection footing — tune existing Mirai behavioral signatures and add rules hunting for anomalous SOCKS5 proxy establishment from edge device IP ranges; flag unusual outbound TCP 1080 or similar proxy-port connections from network appliance subnets.
- Leader — Learn: A new Mirai variant converting edge devices into proxy nodes is an emerging infrastructure threat worth tracking, but it presents no immediate vendor-breach, regulatory, or board-escalation trigger at this stage.