SecPod

Learn Search

Search across all Learn content

← Back to Security Research
2026 First quarter attacker campaigns

2026 First quarter attacker campaigns

Jul 22, 2026By Rinu K
Quarterly Attack Trends Briefing

Campaigns in this report

A visual roadmap of the operations examined in this quarterly review. Select any campaign to move directly to its technical analysis.

Quarterly Attack Trends Briefing

Between April and June 2026, the most consequential intrusions did not begin with an obviously malicious executable landing on an employee workstation. They began further upstream: at the firewall, VPN gateway, Exchange server, web application, CI/CD workflow or remote-management service that organizations already trusted. Once attackers controlled those systems, they inherited the reach and authority of the platform itself.

The quarter also showed how sharply intrusion timelines have compressed. Storm-1175 moved from exploitation to Medusa ransomware in days—and in some cases in less than 24 hours—while CL-STA-1132 converted a newly discovered PAN-OS weakness into root-level access, tunneling and identity-focused follow-on activity. At the same time, FIRESTARTER and ShadowPad demonstrated the opposite operational model: quiet, durable access engineered to survive routine administration and remain useful for long-term intelligence collection.

Another defining trend was the blending of exploitation with trusted identities and legitimate tooling. FortiBleed-style credential operations turned exposed appliances into reusable access inventories. Megalodon placed malicious logic inside GitHub Actions, where a workflow could inherit deployment secrets and publishing privileges. Ransomware operators continued to rely on familiar administration utilities, RMM software, cloud-transfer tools and vulnerable drivers, making behavioral context more valuable than simple tool blocking.

Taken together, these campaigns show an attacker ecosystem moving toward faster edge exploitation, deeper control-plane persistence, automated secret theft and more dependable paths to extortion. The technical chapters that follow trace how each operation progressed, which ATT&CK techniques were visible, what evidence defenders can hunt, and where intervention is most likely to break the chain.

Rapid ransomware intrusion

Storm-1175 and Medusa: speed as the weapon

A financially motivated actor repeatedly weaponized web-facing vulnerabilities, moved from exploit to extortion in days—and sometimes under 24 hours—and deployed Medusa ransomware.

01disclosure6 April 2026
02MotivationFinancial
03TargetsHealthcare, education, finance, professional services
04RegionsUS, UK, Australia

Why Storm-1175 and Medusa matters

Microsoft tracks Storm-1175 as a high-velocity actor that rapidly rotates through newly disclosed N-days and has also used zero-days. Since 2023 it exploited more than 16 vulnerabilities across Exchange, PaperCut, Ivanti, ScreenConnect, TeamCity, SimpleHelp, CrushFTP, GoAnywhere, SmarterMail and BeyondTrust. The defensive problem is the compressed time between disclosure, exploitation, credential theft, exfiltration and ransomware. [secpod-storm]

Visual attack flow

Attack methodology and infection process

  1. Initial access. Exploit vulnerable public-facing applications. Microsoft observed rapid adoption of CVE-2026-23760, CVE-2026-1731 and multiple older enterprise flaws.
  2. Persistence. Create local or domain users and add them to privileged groups; deploy web shells or SimpleHelp for durable remote access.
  3. Credential access. Dump LSASS and domain material using Mimikatz/Impacket-style tooling.
  4. Lateral movement. Use PowerShell, PsExec, RDP, PDQ Deploy and RMM channels to reach servers and backup infrastructure.
  5. Collection and impact. Stage and exfiltrate data with Rclone, impair security controls, then distribute Medusa via administrative deployment mechanisms.

MITRE ATT&CK mapping

TacticIDTechniqueObserved use
Initial AccessT1190Exploit Public-Facing ApplicationMore than 16 exploited CVEs; rapid N-day/zero-day weaponization
PersistenceT1136.002Create Account: Domain AccountNew privileged accounts after compromise
ExecutionT1059.001PowerShellPost-exploitation and lateral tooling
Credential AccessT1003.001LSASS MemoryMimikatz/Impacket credential dumping
Lateral MovementT1021.002SMB/Windows Admin SharesPsExec and administrative deployment
ExfiltrationT1567.002Exfiltration to Cloud StorageRclone staging and transfer
Defense EvasionT1562.001Impair DefensesSecurity setting and protection changes
ImpactT1486Data Encrypted for ImpactMedusa ransomware

Technique mappings are based on reported behavior; they are not a claim that every affiliate or victim exhibited every technique.

Indicators of compromise and high-signal artifacts

TypeIndicatorWhy it matters
SHA-2560cefeb6210b7103fd32b996beff518c9b6e1691a97bb1cda7f5fb57905c4be96Gaze.exe / Medusa
SHA-2569632d7e4a87ec12fdd05ed3532f7564526016b78972b2cd49a610354d672523clsp.exe / Rclone; also used by other actors
IP185.135.86[.]149SimpleHelp C2
IP134.195.91[.]224SimpleHelp C2
IP85.155.186[.]121SimpleHelp C2
BehaviorPrivileged account creation + remote tool + Rclone within hoursHigh-signal sequence even when hashes change

Note: Defang network indicators before operational use. Validate age, ownership and local context; do not block shared infrastructure solely by hostname.

Campaign-specific detection and mitigation

  • Prioritize exposed-system patches within hours when exploitation is reported; isolate if a fix is unavailable.
  • Alert on account creation followed by Administrators/Domain Admins membership.
  • Detect PsExec/PDQ/RMM deployment outside approved change windows.
  • Block or tightly govern Rclone and investigate first-seen cloud destinations.
  • Protect and separately monitor backup, virtualization and domain-control planes.

Edge-device espionage

UAT-4356 and FIRESTARTER: persistence inside Cisco LINA

A custom Linux ELF backdoor survives graceful reboots and software upgrades by manipulating Cisco Service Platform mount behavior and injecting an in-memory handler into LINA.

01disclosure23 April 2026
02ActorUAT-4356 / Storm-1849
03ProductsCisco ASA and FTD on FXOS
04ObjectiveCovert long-term access / espionage

Why UAT-4356 and FIRESTARTER matters

Cisco Talos linked continued targeting of Firepower devices to UAT-4356, the actor associated with the ArcaneDoor campaign. The group exploited CVE-2025-20333 and CVE-2025-20362, deployed FIRESTARTER, and used it to execute arbitrary shellcode inside LINA. Its transient on-disk persistence survives graceful reboots and upgrades, while a true hard power cycle interrupts the runlevel-dependent restoration mechanism; compromised appliances should still be reimaged. [SecPod-blog]

Visual attack flow

Attack methodology and infection process

  1. Initial access. Exploit missing-authorization and buffer-overflow conditions on vulnerable Cisco devices.
  2. Boot-sequence persistence. Modify CSP_MOUNT_LIST so commands run during graceful reboot; copy the implant to a log-like backup path when runlevel 6 is detected.
  3. Self-restoration. Copy the ELF back to /usr/bin/lina_cs, execute it, then restore the original mount list and delete staging artifacts.
  4. In-memory execution. Locate executable libstdc++.so memory, stage shellcode, replace a LINA handler and parse specially prefixed WebVPN XML requests.
  5. Follow-on control. Execute arbitrary shellcode, including LINE VIPER capabilities, within the firewall data-plane process.

MITRE ATT&CK mapping

TacticIDTechniqueObserved use
Initial AccessT1190Exploit Public-Facing ApplicationCVE-2025-20333 and CVE-2025-20362
PersistenceT1547Boot or Logon Autostart ExecutionCSP_MOUNT_LIST abuse during the appliance boot sequence; analyst-level parent mapping
Defense EvasionT1036MasqueradingImplant stored as a log-like file
Defense EvasionT1070.004File DeletionRemove lina_cs and temporary mount-list copy
Privilege / ExecutionT1055Process InjectionUnauthorized handler and shellcode inside LINA
Command and ControlT1105Ingress Tool TransferShellcode delivered through crafted WebVPN request
ExecutionT1059.004Unix ShellArbitrary shell commands on appliance

Technique mappings are based on reported behavior; they are not a claim that every affiliate or victim exhibited every technique.

Indicators of compromise and high-signal artifacts

TypeIndicatorWhy it matters
File path/usr/bin/lina_csObserved FIRESTARTER filename; actor can rename it
File path/opt/cisco/platform/logs/var/log/svc_samcore.logBackup location used during graceful reboot
ArtifactCSP_MOUNT_LIST / CSP_MOUNTLIST.tmpBoot persistence and temporary restoration artifacts
Processlina_cs or anomalous executable mapped into LINATreat as confirmed compromise pending vendor validation
NetworkWebVPN XML carrying custom prefix plus shellcodeBackdoor trigger pattern; requires device/network inspection
CVECVE-2025-20333; CVE-2025-20362Initial-access vulnerabilities

Note: Defang network indicators before operational use. Validate age, ownership and local context; do not block shared infrastructure solely by hostname.

Campaign-specific detection and mitigation

  • Upgrade to Cisco-fixed releases and follow vendor compromise guidance; patching alone does not clean an implanted device.
  • Open a Cisco TAC case for forensic acquisition and reimage confirmed devices from trusted media.
  • Use a hard power cycle only as an emergency interruption, followed by reimaging and credential/certificate rotation.
  • Hunt for lina_cs, altered CSP_MOUNT_LIST, svc_samcore.log anomalies and unexplained LINA memory behavior.
  • Rotate administrative credentials, VPN secrets, certificates and private keys accessible from the device.

China-aligned cyberespionage

SHADOW-EARTH-053: ProxyLogon to GODZILLA and ShadowPad

A provisional China-aligned cluster exploited old Exchange/IIS flaws, maintained web-shell access, sideloaded ShadowPad through signed executables and collected high-value mailbox data.

01disclosure30 April 2026
02Activity sinceDecember 2024
03TargetsGovernment, defense-linked IT, critical infrastructure
04GeographyAsia; one NATO member state

Why SHADOW-EARTH-053 matters

Trend Micro observed SHADOW-EARTH-053 in at least eight countries. The actor repeatedly exploited long-patched Exchange/IIS vulnerabilities—especially ProxyLogon—then used GODZILLA web shells, registry-staged ShadowPad, legitimate signed loaders, WMIC, Sharp-SMBExec, Mimikatz and custom mailbox-export tools. Nearly half of targeted environments overlapped with SHADOW-EARTH-054, but available evidence suggested independent exploitation rather than coordinated operations. [SecPod-blog]

Visual attack flow

Attack methodology and infection process

  1. Initial access. Exploit CVE-2021-26855, -26857, -26858 and -27065 against exposed Exchange infrastructure.
  2. Web-shell persistence. Deploy .aspx or .ashx GODZILLA shells in aspnet_client or OWA auth directories.
  3. Discovery. Run nltest, nslookup, csvde, PowerView and a custom DomainMachines.exe directly under w3wp.exe.
  4. ShadowPad loading. Abuse legitimate signed executables for DLL sideloading; retrieve a machine-specific scode value from HKCU\Software\[ComputerName] and execute via EnumDesktopsA callback injection.
  5. Lateral movement. Use WMIC, Sharp-SMBExec, admin shares and copied web shells to expand across Exchange servers.
  6. Collection. Dump LSASS/SAM and DCSync material; export executive PST/mailbox data and stage password-protected RAR archives.

MITRE ATT&CK mapping

TacticIDTechniqueObserved use
Initial AccessT1190Exploit Public-Facing ApplicationProxyLogon and IIS N-days
PersistenceT1505.003Web ShellGODZILLA .aspx/.ashx files
Defense EvasionT1574.002DLL Side-LoadingSigned executables load malicious DLLs
ExecutionT1106Native APIEnumDesktopsA callback injection
DiscoveryT1087.002Domain Account DiscoveryPowerView/csvde enumeration
Credential AccessT1003.001LSASS MemoryEvil-CreateDump and Mimikatz
Credential AccessT1003.006DCSyncnewdcsync artifact
Lateral MovementT1047WMIWMIC backdoor/tool deployment
CollectionT1114.002Remote Email CollectionExchangeExport/EWS and PST collection
ArchiveT1560.001Archive via UtilityPassword-protected RAR

Technique mappings are based on reported behavior; they are not a claim that every affiliate or victim exhibited every technique.

Indicators of compromise and high-signal artifacts

TypeIndicatorWhy it matters
Web-shell nameserror.aspx; signout.aspx; warn.aspx; charcode.aspx; tunnel.ashx; i.aspxRepresentative filenames; validate content and parent process
Web roots?:\inetpub\wwwroot\aspnet_client\system_web; ...\owa\authRepeated web-shell locations
RegistryHKCU\Software\[ComputerName] value scodeRegistry-staged ShadowPad shellcode
LoaderCIATosBtKbd.exe + TosBtKbd.dllToshiba loader sideload chain
SHA-2564264cfb3980a068ab36d842c7ee0942f40aaf308f31ed48b41e140e59885f5c8Legitimate vulnerable loader; hunt only with adjacent artifacts
SHA-2568d9433e9734dd629d74abe41ff7024c84b3a28c45671df8f4baed344de733c78Legitimate xReport loader used in chain
Process chainw3wp.exe → rundll32.exe / cmd.exe / PowerShellStrong post-exploitation signal on Exchange

Note: Defang network indicators before operational use. Validate age, ownership and local context; do not block shared infrastructure solely by hostname.

Campaign-specific detection and mitigation

  • Patch or retire legacy Exchange/IIS; validate ProxyLogon remediation and external exposure.
  • Alert on w3wp.exe spawning shells, discovery tools, rundll32 or credential-dumping processes.
  • File-integrity monitor Exchange web roots for new .aspx/.ashx content.
  • Detect signed executables loading unexpected DLLs from writable directories and registry values named scode.
  • Restrict EWS/mailbox-export rights and monitor bulk PST/RAR creation.

PAN-OS zero-day exploitation

CL-STA-1132: root RCE through the Captive Portal

A likely state-sponsored cluster exploited CVE-2026-0300, injected shellcode into nginx, stole identity context from the firewall and used intermittent SOCKS tunnels while destroying forensic evidence.

01Earliest probe9 April 2026
02Successful RCE16 April 2026
03Disclosure5–6 May 2026
04ScopeLimited, targeted exploitation

Why CL-STA-1132 matters

CVE-2026-0300 is a critical unauthenticated buffer overflow in the PAN-OS User-ID Authentication Portal. Exposure requires the portal plus a response-enabled interface reachable from untrusted traffic. CL-STA-1132 achieved root execution, cleared crash and nginx evidence, deployed EarthWorm and ReverseSocks5, enumerated Active Directory using credentials likely obtained from the firewall, and operated in short, low-noise sessions.

Visual attack flow

Attack methodology and infection process

  1. Exploit. Trigger an out-of-bounds write in the Captive Portal and gain root-level arbitrary code execution.
  2. Immediate cleanup. Clear crash kernel messages, nginx crash entries/records and core dumps.
  3. Tool deployment. Write tunneling binaries into /var/tmp and /tmp and run them with root privileges.
  4. Identity-driven discovery. Use firewall service-account credentials to enumerate domain root and DomainDnsZones.
  5. HA targeting. Flood SAML traffic to promote a second peer to Active, then exploit the newly exposed device.
  6. Low-noise persistence. Favor intermittent non-persistent tunnels and delete ptrace/SUID evidence rather than installing a durable branded implant.

MITRE ATT&CK mapping

TacticIDTechniqueObserved use
Initial AccessT1190Exploit Public-Facing ApplicationCVE-2026-0300
ExecutionT1055Process InjectionShellcode in nginx worker
ProxyT1090.001Internal ProxyEarthWorm / ReverseSocks5 SOCKS
C2T1572Protocol TunnelingMulti-hop and reverse tunnels
DiscoveryT1087.002Domain Account DiscoveryAD enumeration with service account
Defense EvasionT1070.002Clear Linux or Mac System LogsCrash/nginx/audit cleanup
Defense EvasionT1070.004File DeletionCore dumps, tools and SUID artifact removed

Technique mappings are based on reported behavior; they are not a claim that every affiliate or victim exhibited every technique.

Indicators of compromise and high-signal artifacts

TypeIndicatorWhy it matters
IP67.206.213[.]86Observed attacker infrastructure
IP136.0.8[.]48Observed attacker infrastructure
IP146.70.100[.]69C2 staging; EarthWorm download host
URLhxxp[:]//146.70.100[.]69:8000/php_sessEarthWorm download
SHA-256e11f69b49b6f2e829454371c31ebf86893f82a042dae3f2faf63dcd84f97a584EarthWorm binary
Paths/var/tmp/linuxap; /var/tmp/linuxda; /var/tmp/linuxupdateTunneling tools
Paths/tmp/.c; /tmp/R5; /var/R5Python/ReverseSocks5 artifacts
User-AgentSafari/532.31 Mozilla/5.5 ... Chrome/138 ... Edg/138Observed attacker string

Note: Defang network indicators before operational use. Validate age, ownership and local context; do not block shared infrastructure solely by hostname.

Campaign-specific detection and mitigation

  • Upgrade to fixed PAN-OS versions and verify the exact product train against the vendor advisory.
  • Disable User-ID Authentication Portal if unnecessary; otherwise restrict it to trusted internal zones and disable response pages on untrusted L3 interfaces.
  • Enable Threat ID 510019 where supported and monitor portal exposure continuously.
  • Preserve off-box logs; hunt for gaps or deletion in crash, nginx and audit telemetry.
  • Rotate service-account credentials accessible to the firewall and investigate downstream AD queries.

CI/CD supply-chain compromise

Megalodon / TeamPCP: malicious workflows at repository scale

More than 5,500 repositories received automated commits that inserted or replaced GitHub Actions workflows, harvesting deployment secrets from privileged runners.

01Campaign date18 May 2026
02Duration~6 hours
03Repositories5,561 reported
04Malicious commits5,718 reported

Why Megalodon / TeamPCP matters

The campaign described as Megalodon abused GitHub Actions rather than changing application code directly. Automated commits inserted Base64-encoded Bash into workflow files. One variant triggered on every push and pull request; another remained dormant until workflow_dispatch. The reporting associated the activity with TeamPCP and linked poisoned source to malicious npm publication, including Tiledesk. [secpod-mega]

Visual attack flow

Attack methodology and infection process

  1. Repository access. Use automated, throwaway accounts and maintenance-themed commit identities to push workflow changes.
  2. Workflow persistence. Add always-on triggers or dormant manual-dispatch backdoors.
  3. Runner execution. Decode Bash payloads inside GitHub-hosted or self-hosted runners.
  4. Credential theft. Harvest GitHub, AWS, Azure, GCP, Kubernetes, Vault, SSH and deployment secrets available to the job.
  5. Exfiltration. Send secrets to dedicated attacker infrastructure over an application-layer channel.
  6. Downstream compromise. Use stolen publishing access or poisoned source to publish malicious npm versions.

MITRE ATT&CK mapping

TacticIDTechniqueObserved use
Initial AccessT1195.002Compromise Software Supply ChainMalicious CI/CD workflow commits
ExecutionT1059.004Unix ShellBase64-decoded Bash in runners
PersistenceT1546Event Triggered Executionpush, pull_request and workflow_dispatch triggers
Credential AccessT1552.001Credentials In FilesWorkflow secrets and environment material
DiscoveryT1083File and Directory DiscoveryRunner/repository enumeration
ExfiltrationT1041Exfiltration Over C2 ChannelSecrets sent to attacker server
C2T1071.001Web ProtocolsApplication-layer transfer

Technique mappings are based on reported behavior; they are not a claim that every affiliate or victim exhibited every technique.

Indicators of compromise and high-signal artifacts

TypeIndicatorWhy it matters
IP216.126.225[.]129:8443Reported exfiltration/C2 endpoint
Path.github/workflows/Unauthorized additions or replacements
ContentBase64-encoded Bash in YAML run stepsHigh-signal workflow artifact
Commit identitiesbuild-bot; auto-ci; ci-bot; pipeline-botReported suspicious authors; names are spoofable
Emailsbuild-system@noreply[.]dev; ci-bot@automated[.]devReported commit identities
BehaviorNew workflow trigger + secret enumeration + outbound 8443More durable than account-name matching

Note: Defang network indicators before operational use. Validate age, ownership and local context; do not block shared infrastructure solely by hostname.

Campaign-specific detection and mitigation

  • Require CODEOWNERS and protected-branch approval for .github/workflows changes.
  • Use read-only GITHUB_TOKEN by default; grant publishing and OIDC permissions only to dedicated jobs.
  • Prevent pull requests or unknown forks from reaching privileged secrets/runners.
  • Inspect workflow diffs for encoded shell, curl/wget, environment dumps and manual-dispatch backdoors.
  • Rotate all secrets exposed to affected runners and review downstream registry/cloud audit logs.

VPN-to-ransomware intrusion

Qilin and CVE-2026-50751: authentication bypass plus EDR killing

A Check Point IKEv1 certificate-validation flaw enabled passwordless VPN sessions; Qilin-linked post-exploitation overlapped with Linux payload delivery and a sophisticated vulnerable-driver EDR killer.

01Earliest exploitation7 May 2026
02Disclosure8 June 2026
03CVECVE-2026-50751 / CVSS 9.3
04ConfidenceMedium-confidence Qilin linkage

Why Qilin and CVE-2026-50751 matters

Check Point confirmed exploitation of CVE-2026-50751 against Remote Access VPN and Mobile Access deployments using deprecated IKEv1. The flaw bypasses user authentication but still requires post-authentication work to reach internal resources or escalate. One observed case involved a Qilin affiliate. Separately, Talos analyzed Qilin’s msimg32.dll loader, which blinds telemetry and abuses the signed rwdrv.sys/ThrottleStop driver to terminate hundreds of EDR drivers. [SecPod-blog]

Visual attack flow

Attack methodology and infection process

  1. Perimeter entry. Exploit CVE-2026-50751 on affected Check Point configurations.
  2. Post-authentication expansion. Use the VPN foothold to discover internal resources and obtain higher privileges.
  3. Defense impairment. Run msimg32.dll, recover clean syscalls, suppress ETW-related visibility and use exception-driven obfuscation.
  4. BYOVD. Load renamed signed ThrottleStop.sys as rwdrv.sys and use physical-memory primitives for kernel manipulation.
  5. Impact. Deploy Windows or Linux Qilin ransomware and conduct double extortion.

MITRE ATT&CK mapping

TacticIDTechniqueObserved use
Initial AccessT1190Exploit Public-Facing ApplicationVPN authentication bypass
Valid SessionT1078Valid Accounts / authenticated channelPasswordless VPN session resembles legitimate remote access
Defense EvasionT1562.001Impair DefensesTerminate 300+ EDR drivers
Privilege / KernelT1068Exploitation for Privilege EscalationVulnerable signed driver primitives
ExecutionT1129Shared ModulesMulti-stage malicious DLL chain
Lateral MovementT1021Remote ServicesInternal expansion after VPN access
ImpactT1486Data Encrypted for ImpactQilin ransomware
ImpactT1490Inhibit System RecoveryBackup/recovery disruption common to Qilin operations

Technique mappings are based on reported behavior; they are not a claim that every affiliate or victim exhibited every technique.

Indicators of compromise and high-signal artifacts

TypeIndicatorWhy it matters
IP45.77.149[.]152Check Point observed infrastructure
IP209.182.225[.]136Check Point observed infrastructure
IP38.60.157[.]139Check Point observed infrastructure
IP162.33.177[.]101Check Point observed infrastructure
Filenamemsimg32.dllQilin EDR-killer loader
Filenamerwdrv.sysRenamed vulnerable ThrottleStop driver
BehaviorVPN session without expected authentication eventsHigh-value gateway hunting sequence
BehaviorEDR health loss immediately after driver loadDefense-impairment indicator

Note: Defang network indicators before operational use. Validate age, ownership and local context; do not block shared infrastructure solely by hostname.

Campaign-specific detection and mitigation

  • Patch affected Check Point gateways, disable deprecated IKEv1 and review configuration against sk185033.
  • Hunt retrospectively from 7 May, not from public disclosure.
  • Correlate gateway VPN session establishment with IdP/MFA records; investigate sessions lacking the normal sequence.
  • Enable Microsoft vulnerable-driver protections and application control; alert on rwdrv.sys or equivalent hashes/renames.
  • Isolate immediately when multiple EDR agents disappear or ETW telemetry drops after a driver load.

Ransomware ecosystem activity

INC / Lynx RaaS: scale, affiliate reuse and double extortion

The INC lineage expanded through displaced affiliates, opportunistic edge exploitation, credential abuse, cross-platform encryption and a mature leak-site pressure model.

01EmergenceAugust 2023
02Reported total830+ claimed victims by June 2026
03ModelRansomware as a Service
04SectorsHealthcare, manufacturing, education, government, services

Why INC / Lynx RaaS matters

SecPod’s June review described INC as one of 2026’s most active RaaS ecosystems, citing more than 830 claimed victims since emergence. The operation and related Lynx lineage use varied affiliate entry methods, including exposed services, valid credentials, phishing and exploitation of Citrix, Fortinet and SimpleHelp vulnerabilities. Because affiliates differ, behavior-based coverage is more reliable than a single universal IOC set. [secpod-inc]

Visual attack flow

Attack methodology and infection process

  1. Initial access. Use compromised credentials, RDP/VPN, phishing or CVEs such as CVE-2023-3519, CVE-2025-5777, CVE-2023-48788 and CVE-2024-57727.
  2. Reconnaissance. Identify domain controllers, backups, hypervisors, file servers and sensitive repositories.
  3. Credential access. Dump LSASS, SAM and service/backup credentials with affiliate-selected tooling.
  4. Movement and persistence. Use RDP, PowerShell, PsExec, WMI and commercial remote tools.
  5. Exfiltration. Stage financial, customer, employee and intellectual-property data to cloud or attacker infrastructure.
  6. Impact. Delete recovery material, encrypt Windows/Linux/virtualization assets, append .INC and drop INC-README notes.

MITRE ATT&CK mapping

TacticIDTechniqueObserved use
Initial AccessT1078Valid AccountsVPN/RDP and compromised credentials
Initial AccessT1190Exploit Public-Facing ApplicationCitrix, Fortinet, SimpleHelp flaws
ExecutionT1059Command and Scripting InterpreterPowerShell/cmd/shell
PersistenceT1098Account ManipulationAffiliate persistence
Credential AccessT1003OS Credential DumpingLSASS/SAM/domain material
DiscoveryT1018Remote System DiscoveryNetwork/AD inventory
Lateral MovementT1021Remote ServicesRDP, SMB, WMI/PsExec
ExfiltrationT1567.002Cloud StorageRclone/MEGA/Restic
ImpactT1490Inhibit System RecoveryShadow-copy and backup disruption
ImpactT1486Data Encrypted for Impact.INC encryption

Technique mappings are based on reported behavior; they are not a claim that every affiliate or victim exhibited every technique.

Indicators of compromise and high-signal artifacts

TypeIndicatorWhy it matters
Extension.INCEncrypted files in INC variants
Ransom notesINC-README.txt; INC-README.htmlCommon INC note names
Lynx noteREADME.txtRelated Lynx lineage
SHA-25664b249eb3ab5993e7bcf5c0130e5f31cbd79dabdcad97268042780726e68533fPublished INC sample
BehaviorRclone/MEGASync/Restic + include list + large outbound transferPre-encryption exfiltration pattern
Behaviorvssadmin/WMIC shadow-copy deletion before mass writesImpact-stage indicator

Note: Defang network indicators before operational use. Validate age, ownership and local context; do not block shared infrastructure solely by hostname.

Campaign-specific detection and mitigation

  • Patch internet-facing Citrix, Fortinet and SimpleHelp systems and remove obsolete remote interfaces.
  • Require MFA for VPN/RDP/RMM and block unmanaged remote tools.
  • Monitor abnormal LSASS access, DCSync, PsExec service creation and backup-console logins.
  • Alert on Rclone/MEGA/Restic from servers and on shadow-copy deletion.
  • Maintain immutable backups with separate identity and test bare-metal/virtualization recovery.

Credential compromise campaign

FortiBleed: valid credentials as a self-reinforcing attack engine

Internet-wide spraying, configuration theft, offline cracking and credential reuse turned edge-device access into an expanding targeting database rather than a single-CVE exploit wave.

01activityActive through June 2026
02Primary surfaceFortiGate and SSL VPN
03MechanismCredential reuse + config extraction + offline cracking
04AttributionDisputed / vendor-assessed

Why FortiBleed matters

Unit 42 independently observed large-scale password spraying against Fortinet devices and MSSQL, with reports involving Sophos. It described a multi-stage loop of spraying, configuration extraction, optional privilege escalation and offline cracking; it did not validate an initial-access broker’s claimed CVE. SecPod reported approximately 73,000 firewall records, while SOCRadar later reported 86,644 working credentials and attributed the operation to Lynx/INC. These figures reflect evolving datasets and vendor methodology, not one immutable count. [secpod-forti]

Visual attack flow

Attack methodology and infection process

  1. Reconnaissance. Identify exposed FortiGate management and SSL VPN interfaces on 443 and common alternate ports.
  2. Initial access. Use credentials from previous breaches, infostealers and historic Fortinet leaks rather than depending on a new zero-day.
  3. Configuration theft. With sufficient rights, export appliance configuration and encrypted credential material.
  4. Offline cracking. Use Hashcat/Hashtopolis-style infrastructure to recover plaintext without generating victim-side password-guess logs.
  5. Expansion. Reuse recovered credentials across devices and organizations, creating a positive feedback loop.
  6. Monetization. Offer high-privilege access to brokers or ransomware affiliates; attribution remains a vendor assessment.

MITRE ATT&CK mapping

TacticIDTechniqueObserved use
Credential AccessT1110.003Password SprayingCurated internet-wide attempts
Initial AccessT1078Valid AccountsSuccessful appliance/VPN logins
Credential AccessT1552.001Credentials In FilesConfiguration export and stored material
PersistenceT1098Account ManipulationNew administrator accounts/policy changes
DiscoveryT1049System Network Connections DiscoveryAppliance and VPN context
CollectionT1005Data from Local SystemDevice configuration collection
ExfiltrationT1041Exfiltration Over C2 ChannelExported configs/credentials
Defense EvasionT1562.001Impair DefensesLogging/authentication configuration changes

Technique mappings are based on reported behavior; they are not a claim that every affiliate or victim exhibited every technique.

Indicators of compromise and high-signal artifacts

TypeIndicatorWhy it matters
BehaviorSuccessful admin login immediately after high-volume failuresCore spray-to-access sequence
Audit eventConfiguration export to unfamiliar destinationCredential-harvesting precursor
AccountNew super_admin or altered trusted-host settingPotential persistence
NetworkPersistent outbound tunnel from firewallFollow-on control channel
ToolingHashcat; Hashtopolis; CyberStrike; passive VPN snifferReported attacker-side components; not malicious by themselves
Dataset caveat~73,000 SecPod records; 86,644 SOCRadar credentialsEvolving datasets—validate organization-specific exposure

Note: Defang network indicators before operational use. Validate age, ownership and local context; do not block shared infrastructure solely by hostname.

Campaign-specific detection and mitigation

  • Remove management interfaces from the public internet; use allow-listed bastions.
  • Rotate all administrator and VPN credentials and enforce MFA.
  • After FortiOS upgrades, verify stronger password rehashing and remove retained weak hashes per vendor guidance.
  • Review new accounts, trusted hosts, logging, authentication policy, config exports and unusual geo/ASN access.
  • Treat verified inclusion in the leaked dataset as a compromise and perform full appliance incident response.

Post-quarter technical appendix

JADEPUFFER: autonomous database extortion as the reference format

Included because you supplied it as the desired structural model. Sysdig disclosed the research on 1 July 2026, so it is not counted as an April–June disclosure.

01Disclosure1 July 2026
02EntryCVE-2025-3248 / Langflow
03Operator modelLLM-driven agent
04ImpactNacos/MySQL configuration destruction

Why JADEPUFFER matters

Sysdig assessed JADEPUFFER as the first documented end-to-end agentic ransomware operation. The agent delivered Base64 Python through Langflow’s unauthenticated code-validation endpoint, searched for AI/cloud/database secrets, pivoted to a production database, self-corrected failed steps within seconds, encrypted 1,342 Nacos configuration items, dropped original tables and created a ransom table. Sysdig could not independently verify the agent’s exfiltration claim, and the generated AES key was not preserved—meaning payment could not restore the data. [SecPod-blog]

Visual attack flow

Attack methodology and infection process

  1. Langflow compromise. Abuse the missing-authentication code-validation endpoint for arbitrary Python.
  2. Parallel secret search. Enumerate OpenAI/Anthropic/DeepSeek/Gemini keys, cloud credentials, wallets and database files.
  3. Internal discovery. Probe MinIO, Nacos, secret stores and databases; adapt parsing and authentication logic when attempts fail.
  4. Persistence. Install a 30-minute cron beacon to the source/C2 address.
  5. Database extortion. Use AES_ENCRYPT() to copy encrypted configuration content, delete originals/history and create README_RANSOM.
  6. Destruction. Disable foreign-key checks when necessary and drop high-value schemas; the asserted staging/exfiltration was not independently proven.

MITRE ATT&CK mapping

TacticIDTechniqueObserved use
Initial AccessT1190Exploit Public-Facing ApplicationCVE-2025-3248
ExecutionT1059.006PythonBase64 Python payloads
DiscoveryT1082System Information Discoveryid, uname, hostname, processes
Credential AccessT1552.001Credentials In FilesEnvironment/config secret sweep
DiscoveryT1046Network Service DiscoveryInternal service probing
PersistenceT1053.003Cron30-minute beacon
CollectionT1005Data from Local SystemLangflow database/configuration data
ImpactT1485Data DestructionDROP TABLE / DROP DATABASE
ImpactT1486Data Encrypted for ImpactNacos configuration encryption

Technique mappings are based on reported behavior; they are not a claim that every affiliate or victim exhibited every technique.

Indicators of compromise and high-signal artifacts

TypeIndicatorWhy it matters
IP45.131.66[.]106Initial access/C2; cron beacon on port 4444
IP64.20.53[.]230Claimed staging server; exfiltration not independently observed
CVECVE-2025-3248Langflow unauthenticated RCE
Cron*/30 * * * * ... 45.131.66[.]106:4444/beaconPersistence behavior
TableREADME_RANSOMDatabase ransom artifact
Emaile78393397[@]proton[.]meRansom contact

Note: Defang network indicators before operational use. Validate age, ownership and local context; do not block shared infrastructure solely by hostname.

Campaign-specific detection and mitigation

  • Patch Langflow and never expose code-validation endpoints publicly.
  • Keep LLM/cloud provider keys out of Langflow process environments.
  • Restrict database admin ports and prohibit root access from application subnets.
  • Harden Nacos, change default signing keys and remove database root privileges.
  • Detect Python spawned by Langflow, cron modifications and destructive SQL from application hosts.

Consolidated defense

Mitigations across all campaigns

These controls are ordered around the recurring attack surfaces visible across the campaigns: exposed edge systems, identity and secrets, privileged automation, incomplete telemetry, and weak recovery assurance.

Featured Posts

Open One Request, Total Persistence: Inside the SharePoint Flaw Attackers Are Exploiting
One Request, Total Persistence: Inside the SharePoint Flaw Attackers Are Exploiting

CVE Research

One Request, Total Persistence: Inside the SharePoint Flaw Attackers Are Exploiting

A critical SharePoint deserialization flaw, CVE-2026-50522 (CVSS 9.8), is under active exploitation just weeks after its July 2026 patch, following a public PoC. Attackers are using it to steal IIS machine keys in a single request, gaining persistence that survives patching alone. Now on CISA's KEV list, it's the third actively exploited SharePoint flaw in recent months, patch immediately and rotate machine keys.

Jul 24, 2026

Open ENCFORGE Ransomware: Anatomy of an AI-Focused Cyber Attack
ENCFORGE Ransomware: Anatomy of an AI-Focused Cyber Attack

CVE Research

ENCFORGE Ransomware: Anatomy of an AI-Focused Cyber Attack

Jul 22, 2026

Open UTA0533 Weaponizes KNUCKLEBALL: Inside the SonicWall SMA Zero-Day Exploitation Chain
UTA0533 Weaponizes KNUCKLEBALL: Inside the SonicWall SMA Zero-Day Exploitation Chain

CVE Research

UTA0533 Weaponizes KNUCKLEBALL: Inside the SonicWall SMA Zero-Day Exploitation Chain

Jul 20, 2026

Open One Email, Full Session Takeover: Inside Zimbra's Critical Classic Web Client Code Execution Flaw
One Email, Full Session Takeover: Inside Zimbra's Critical Classic Web Client Code Execution Flaw

CVE Research

One Email, Full Session Takeover: Inside Zimbra's Critical Classic Web Client Code Execution Flaw

Jul 20, 2026