Last Updated On

DDAAIILLYY--22002266--00661177
CCrriittiiccaall
AAccttiivvee  EExxppllooiittaattiioonn  CCoonnffiirrmmeedd

Why Attackers Are Shifting Focus Straight To Your Control Planes

Critical control plane flaws across Cisco Catalyst SD-WAN Manager, LiteLLM, SimpleHelp, and FortiSandbox are under active exploitation globally. Concurrently, DragonForce ransomware operators are evading detection by routing command and control traffic through Microsoft Teams relays. Finally, the ShinyHunters extortion group is pressuring Kodak following a confirmed data compromise. Organizations must immediately isolate public facing management consoles, apply vendor updates, and run log audits to detect web shell activity.

10

CVSS Score

4

IOC Count

17

Source Count

82

Confidence Score

CVEs

CVE-2026-42271, CVE-2026-47101, CVE-2026-47102, CVE-2026-40217, CVE-2026-48710, CVE-2026-20262, CVE-2026-48558, CVE-2026-39813, CVE-2026-39808, CVE-2026-25089, CVE-2026-45657, CVE-2026-32193, CVE-2026-44815.

Actors

ShinyHunters, DragonForce, Under Attribution

Sectors

AI gateway and SaaS infrastructure, Enterprise network and SD-WAN deployments, Remote management and IT support environments, Security products relying on FortiSandbox verdicts, Photography and imaging technology, Telecommunications, Government, Enterprise Networking, Critical Infrastructure

Regions

United States, Worldwide internet‑exposed deployments

Chapter 01 - Executive Overview

Today's threat landscape is dominated by active exploitation targeting network infrastructure control planes, high priority remote management tools, and artificial intelligence proxy gateways. These incidents are compounded by stealthy Software as a Service delivery channels and extortion pressure against major enterprise brands.

Defenders must prioritize mitigating vulnerabilities that grant unauthenticated remote code execution or root level management plane access, as these flaws allow adversaries to bypass traditional boundaries.

+------------------------------------+-------------------------+------------------------+
| Incident Component                 | Primary CVEs / Elements | Operational Priority   |
+------------------------------------+-------------------------+------------------------+
| Cisco Catalyst SD-WAN Manager     | CVE-2026-20262          | Critical (KEV Listed)  |
| LiteLLM AI Proxy Gateway           | CVE-2026-42271 (Chain)  | Critical (KEV Listed)  |
| SimpleHelp Remote Management       | CVE-2026-48558          | Critical (CVSS 10.0)   |
| FortiSandbox Security Appliance    | Trio (CVE-2026-39813)   | High Risk              |
| DragonForce Ransomware Teams Relay | Backdoor.Turn Implant   | High Risk              |
| Kodak ShinyHunters Extortion       | 2.2 Million Records     | Medium Risk

  • Cisco Catalyst SD-WAN Manager Exploitation:

    • Threat Overview: An authenticated path traversal arbitrary file write vulnerability allows low privileged users to upload malicious web application archives.

    • Strategic Risk Context: Because this platform orchestrates wide area networks, compromise allows attackers to plant backdoors, manipulate routing, and pivot into edge routers.

    • Business Impact: Listed in the CISA Known Exploited Vulnerabilities catalog with a federal civilian patch deadline of 29 June 2026, forcing emergency maintenance.

    • Intelligence Confidence: Confirmed directly by Cisco PSIRT and CISA telemetry, establishing absolute certainty regarding exploitability despite a base CVSS of 6.5.

    • Urgent Leadership Decision: Decide whether to authorize immediate network isolation of the management console or fast track emergency patching windows within 24 hours.

  • LiteLLM AI Proxy Gateway Command Injection:

    • Threat Overview: A critical command injection vulnerability in test endpoints is chained with host header and authorization bypasses to allow unauthenticated remote code execution.

    • Strategic Risk Context: LiteLLM brokers multi vendor artificial intelligence models, meaning a server compromise leaks application programming interface keys, prompts, and training data.

    • Business Impact: Added to the CISA Known Exploited Vulnerabilities catalog due to active exploitation, threatening automated corporate decision workflows.

    • Intelligence Confidence: High, verified across multiple threat research firms and federal advisories, though specific victim telemetry is closely guarded.

    • Urgent Leadership Decision: Decide whether to block external traffic to artificial intelligence proxy test paths or completely rotate all upstream model application programming interface keys.

  • SimpleHelp Remote Management Authentication Bypass:

    • Threat Overview: Improper validation of OpenID Connect identity assertions allows unauthenticated attackers to forge tokens and register privileged technician accounts.

    • Strategic Risk Context: Remote monitoring and management applications provide unrestricted endpoint access, making this a turnkey entry point for ransomware groups.

    • Business Impact: Carries an explicit CVSS score of 10.0 with nearly 14,000 internet exposed servers vulnerable, presenting an extensive global attack surface.

    • Intelligence Confidence: Strong technical verification in controlled lab environments by security research groups, though in the wild mass exploitation remains unconfirmed.

    • Urgent Leadership Decision: Decide whether to temporarily disable OpenID Connect integrations on public facing portals or restrict technician access via strict network allowlists.

  • FortiSandbox Exploited Trio:

    • Threat Overview: Attackers are probing and chaining authentication bypass and command injection flaws to execute arbitrary shell utilities on sandbox security tools.

    • Strategic Risk Context: These appliances dictate file verdicts for corporate firewalls, meaning compromise can blind the security stack or blind malware detection capabilities.

    • Business Impact: Undermines trusted architecture security layers, with threat intelligence firms reporting active automated scanning and exploit attempts circulating publicly.

    • Intelligence Confidence: Medium, active exploitation is documented by independent security intelligence firms, though formal vendor confirmation is pending.

    • Urgent Leadership Decision: Decide whether to treat sandbox verdicts as untrusted until patches are verified, enforcing manual inspection for high risk files.

  • DragonForce Ransomware Teams Relay Traffic:

    • Threat Overview: Threat actors compromised a major services provider and deployed a custom Go based implant that tunnels command and control traffic through Microsoft Teams relays.

    • Strategic Risk Context: By routing callbacks through trusted Software as a Service environments, the backdoor completely evades standard network perimeter boundaries and allowlists.

    • Business Impact: Enabled two months of stealthy lateral movement, staging, and data discovery prior to the execution of full ransomware encryption.

    • Intelligence Confidence: High vendor telemetry detailing specific host signatures, though coverage is constrained to a singular, in depth forensic investigation.

    • Urgent Leadership Decision: Decide whether to enforce advanced endpoint behavioral controls on logging utilities or restrict outbound collaboration traffic from administrative servers.

  • Kodak ShinyHunters Data Breach:

    • Threat Overview: The extortion collective ShinyHunters has posted Kodak to its leak site, claiming the theft of 2.2 million corporate and customer records.

    • Strategic Risk Context: Kodak confirmed unauthorized access to a restricted environment, but the threat actors have set an active extortion deadline of 18 June 2026.

    • Business Impact: Presents regulatory exposure regarding personally identifiable information and brand damage, although operational infrastructure remains unaffected.

    • Intelligence Confidence: Medium, verified by corporate acknowledgement of an incident, though the validity and volume of the stolen data records are unproven.

    • Urgent Leadership Decision: Decide whether to trigger supply chain incident response playbooks for shared datasets or prepare media containment strategies.

  • Intelligence Quality Summary: Today's analysis is anchored by verified corporate disclosures and federal threat catalogs, ensuring excellent confidence regarding the mechanics of these exploits. Defenders face visibility gaps due to a lack of shared atomic indicators for the primary networking infrastructure flaws. This necessitates a pivot toward behavioral threat hunting and prompt log reviews.

Chapter 02 - Threat & Exposure Analysis

The current threat environment highlights a systematic shift toward manipulating network control planes, core security applications, and remote management architectures. Rather than focusing on low-level endpoint compromises, threat actors are weaponizing vulnerabilities that afford systemic command execution across hundreds of downstream assets simultaneously.

+--------------------------+---------------------+-----------------------+-----------------------+
| Threat Element           | Exploitation Vector | Structural Objective  | Core Exposure Context |
+--------------------------+---------------------+-----------------------+-----------------------+
| CVE-2026-42271 Chain     | AI Gateway API      | Prompt/API Key Theft  | Enterprise AI Proxies |
| CVE-2026-20262           | Web UI API Endpoint | Control Plane Seizure | Distributed WAN Fleets|
| CVE-2026-48558           | Public OIDC Portal  | Rogue Tech Creation   | Managed Service Providers
| FortiSandbox Trio        | JRPC/Web API        | Security Blinding     | Firewall Sandboxes    |
| Backdoor.Turn Implant    | MSSQL Initial Entry | SaaS Relay Evasion    | Collaboration App SaaS|
| ShinyHunters Extortion   | Third-Party Cloud   | Bulk Data Monetization| Brand & Supplier PII

  • AI Gateway Infrastructure Compromise (LiteLLM Chain):

    • Attack Progression: The exploit path targets the Model Context Protocol test endpoints within BerriAI LiteLLM. Attackers inject arbitrary operating system command strings into parameters handled by /mcp-rest/test/connection or /mcp-rest/test/tools/list. By chaining this command injection (CVE-2026-42271) with an authorization bypass (CVE-2026-47101), a local privilege escalation flaw (CVE-2026-47102), and a host header bypass known as BadHost (CVE-2026-48710), unauthenticated remote code execution is achieved. Once inside, attackers plant persistent configuration callbacks or deploy custom code guardrails to sustain access.

    • Exploitability Framework: Publicly rated with a chained impact scale matching critical thresholds up to 9.9. Exploitation requires minimal complexity once network access to the API gateway is established.

    • Sector and Geographic Blast Radius: Primarily threatens enterprise artificial intelligence deployment pipelines, financial technology operations, and cloud native software providers leveraging multi-vendor model proxies. CISA tracking indicates active targeting against public and private sector infrastructure across the United States and global developer nodes.

  • Network Management Plane Manipulation (Cisco Catalyst SD-WAN Manager):

    • Attack Progression: Attackers exploit an input validation flaw related to path traversal (CVE-2026-20262) within the file upload handler of the web user interface. An authenticated user with basic write level access sends a multipart HTTP POST request containing directory traversal sequences. This allows them to write or overwrite files outside the intended upload directory. The adversary drops a malicious web application archive into directories scanned by the WildFly application server, which auto-deploys the payload. The attacker then interacts via HTTP POST requests to execute shell commands and leverage local flaws to escalate to root.

    • Exploitability Framework: Carries a base CVSS score of 6.5 due to the post-authentication requirement. However, the operational severity is high because valid low-level credentials can be obtained via credential stuffing, phishing, or initial access brokers.

    • Sector and Geographic Blast Radius: Directly impacts telecommunications operators, federal agencies operating FedRAMP environments, and large distributed enterprises. Exposure is global, with a strict federal compliance directive highlighting immediate risk within North American government infrastructure.

  • Remote Management Tool Takeover (SimpleHelp OIDC Bypass):

    • Attack Progression: When OpenID Connect is configured for technician authentication, SimpleHelp fails to properly validate identity provider assertions. An unauthenticated remote attacker can forge an identity token or manipulate specific authentication claims. SimpleHelp processes the malicious assertion as trusted, automatically provisioning a new user profile inside a privileged technician group without requiring valid credentials or multi-factor authentication. This provides immediate remote desktop access, background scripting control, and software deployment capabilities over all managed end-user systems.

    • Exploitability Framework: Evaluated at a maximum CVSS rating of 10.0. The exploit yields instant remote management capabilities with zero pre-existing access, provided the public portal utilizes OpenID Connect automation rules.

    • Sector and Geographic Blast Radius: Concentrated among managed service providers, internal information technology helpdesks, and small to medium businesses. Global internet scanning reveals approximately 14,000 publicly exposed SimpleHelp servers vulnerable to discovery.

  • Defensive Tooling Blinding (FortiSandbox Exploit Trio):

    • Attack Progression: Adversaries utilize a path traversal flaw within the JSON Remote Procedure Call API (CVE-2026-39813) to completely bypass authentication mechanisms. Once unauthenticated access is achieved, they chain the attack with operating system command injection flaws residing in the administrative interface and cloud editions (CVE-2026-39808 and CVE-2026-25089). This allows them to execute arbitrary system shell utilities. Attackers manipulate internal malware analysis queues, alter file analysis verdicts, or use the security appliance as a hardened staging platform.

    • Exploitability Framework: Remotely exploitable over secure HTTP channels. Public security reports indicate that early exploit variants are circulating in the wild, enabling automated scanning scripts to identify unpatched systems.

    • Sector and Geographic Blast Radius: Threatens any enterprise or government network architecture utilizing Fortinet security ecosystems for real-time automated file analysis, creating risk globally across patch-lagging organizations.

  • SaaS Relayed Egress Evasion (DragonForce Backdoor.Turn):

    • Attack Progression: Following an initial compromise likely targeting database architectures via structured query language flaws, threat actors deploy a custom Go-based remote access trojan named Backdoor.Turn. The implant injects malicious code blocks into the legitimate Windows debugging tool DbgView64.exe. To evade network tracking, the backdoor utilizes Microsoft Teams relay infrastructure for all outbound command and control communication. This makes the beaconing traffic appear as standard, authorized communication with trusted cloud environments.

    • Exploitability Framework: Highly effective post-exploitation technique that circumvents traditional network security boundaries, protocol analysis, and standard domain allowlists.

    • Sector and Geographic Blast Radius: Documented in a targeted intrusion against a prominent services firm within the United States. This indicates high risk for corporations dependent on standardized Software as a Service collaboration platforms without host-level behavioral inspection.

  • Brand Threat and Commercial Extortion (Kodak ShinyHunters Breach):

    • Attack Progression: The extortion group ShinyHunters listed Kodak on its public data leak repository, asserting the theft of over 2.2 million customer and corporate files. The group established an active extortion deadline of 18 June 2026. Kodak confirmed an incident involving temporary unauthorized access to an isolated data segment. The technical vector remains unspecified, but the campaign aligns with historical patterns of targeting third-party cloud data brokers and analytics providers to harvest files.

    • Exploitability Framework: Focuses entirely on data exfiltration and public shaming, with no current evidence of system destruction or operational infrastructure disruption.

    • Sector and Geographic Blast Radius: Primarily impacts customer data privacy structures and supplier analytics frameworks within the corporate imaging and technology sectors, demonstrating the persistent risk of third-party supply chain aggregation.

  • Cross-Incident Strategic Vectors: A holistic view of these incidents reveals that threat actors are moving away from traditional, easily monitored exploit paths. By targeting artificial intelligence brokers, wide area network orchestrators, and security analysis appliances, adversaries maximize their lateral reach while minimizing detection. Concurrently, the use of trusted cloud platforms like Microsoft Teams for command and control demonstrates that traditional perimeter models cannot stop advanced egress evasion techniques.

Chapter 03 - Operational Response

Immediate operational response must emphasize the separation of management portals from public networks, rapid patch application on core infrastructure elements, and host-based behavioral analysis to detect infrastructure manipulation.

+------------------------------------+----------------------------------+----------------------------------+
| Critical Asset                     | Immediate Isolation Priority     | Remediation / Hardening Action   |
+------------------------------------+----------------------------------+----------------------------------+
| BerriAI LiteLLM Servers            | Restrict Model Context Paths     | Upgrade to v1.83.14-stable       |
| Cisco Catalyst SD-WAN Manager      | Restrict UI to Trusted Jump Hosts| Deploy Official PSIRT Hotfixes  |
| SimpleHelp Remote Portals          | Disable OIDC Token Auto-Mapping  | Apply Version 5.5.16 / 6.0 RC2  |
| FortiSandbox Appliances            | Segregate JRPC API Access Paths  | Install June 2026 Patches       |
| Production Database Servers        | Audit Egress to SaaS Ranges      | Inspect DbgView64.exe Processes  |
| Third-Party Vendor Data Pipelines  | Review Active Cloud Export Tasks | Implement Least-Privilege Export

  • LiteLLM Containment and Remediation Playbook:

    • Immediate Isolation Steps: Identify every running container, standalone server, or sidecar deployment executing LiteLLM. Modify edge firewalls, reverse proxies, and API gateways to block external traffic directed toward Model Context Protocol test endpoints including /mcp-rest/test/connection and /mcp-rest/test/tools/list. Restrict administrative system access exclusively to local loopback or authenticated internal management zones.

    • Hardening and Configuration Requirements: Force an immediate upgrade of all LiteLLM components to version v1.83.14-stable or higher. Inspect the central config.yaml layout to verify that no unauthorized callbacks have been inserted within the litellm_settings.callbacks directive. Purge any unknown entries.

    • Coordination Tasks: Notify application engineering groups and artificial intelligence stakeholders regarding potential credential exposure. Revoke and completely rotate all upstream large language model application programming interface keys, database connection secrets, and administrative access tokens that transit the proxy layer.

  • Cisco Catalyst SD-WAN Manager Containment and Remediation Playbook:

    • Immediate Isolation Steps: Map all deployment instances across On-Prem, Cloud-Pro, Cisco Managed, and Government FedRAMP architectures. Enforce strict network access control lists to ensure the management interface is only reachable via authorized administrative jump servers or encrypted virtual private network connections.

    • Hardening and Configuration Requirements: Deploy official Cisco fixed software versions according to the product matrix: update version 20.9 to 20.9.9.2, version 20.12 to 20.12.7.2, version 20.15 to 20.15.4.5 or 20.15.5.3, version 20.18 to 20.18.3.1, and version 26.1 to 26.1.1.2. Execute file integrity checks within the WildFly application server environment. Search for unauthorized web application archives or unexpected Java server pages.

    • Coordination Tasks: Alert network operations centers and security operations teams to monitor the platform for anomalous configuration adjustments or secondary user profile additions. Ensure any third-party managed service providers managing wide area network assets confirm compliance and verify logs immediately.

  • SimpleHelp Containment and Remediation Playbook:

    • Immediate Isolation Steps: Scan external network blocks to locate internet-accessible SimpleHelp instances. Access the primary configuration interface and immediately suspend OpenID Connect automated user mapping for Azure Active Directory or generic identity providers until hotfixes are fully deployed.

    • Hardening and Configuration Requirements: Install SimpleHelp version 5.5.16 or 6.0 RC2 to resolve the assertion validation flaw. Review the current active technician directory. Terminate any profiles with unrecognized email domains or unusual creation timestamps. Restrict technician portal login access to authorized corporate subnets using built-in IP filtering rules.

    • Coordination Tasks: Advise information technology support leaders and managed service providers regarding the risk profile. Coordinate with legal counsels to evaluate reporting mandates if log audits indicate that unauthorized technician accounts executed remote scripts or accessed client endpoints.

  • FortiSandbox Containment and Remediation Playbook:

    • Immediate Isolation Steps: Isolate administrative and JSON Remote Procedure Call API portals from non-administrative internal zones and external interfaces. Ensure firewalls feeding files to the sandbox use secure validation methods that cannot be subverted by a compromised appliance.

    • Hardening and Configuration Requirements: Update all FortiSandbox physical, virtual, and cloud installations to the recommended June 2026 patch baseline to clear the vulnerabilities. Review transaction logs for anomalous calls directed toward JRPC endpoints. Look for unexpected local command activities outside standard diagnostic windows.

    • Coordination Tasks: Inform security architecture leads to verify that network security blocks do not blindly trust sandbox verdict data until the integrity of the sandbox operating system is confirmed.

  • DragonForce Teams Relay Containment and Hunt Playbook:

    • Immediate Isolation Steps: Load the verified indicators of compromise, including domains projetosmecanicos.com.br, mysimerp.net, the source IP 62.164.177.25, and the staging path 192.36.27.51/TechSupV18Fix3.zip, into all network blocking and endpoint protection frameworks.

    • Hardening and Configuration Requirements: Enforce advanced host-monitoring controls over standard utility applications, specifically looking for code injection or unauthorized network connections originating from DbgView64.exe. Establish conditional access rules to limit Microsoft Teams relay connections from core infrastructure components, particularly database systems.

    • Coordination Tasks: Update ransomware incident response playbooks to include specific playbooks for analyzing software as a service relayed command and control channels. Brief the collaboration platform management teams regarding behavioral tracking requirements.

  • Kodak Extortion Containment and Risk Playbook:

    • Immediate Isolation Steps: Identify all current enterprise data flows, cloud replication tasks, or automated backups interacting with Kodak or comparable third-party imaging and analytics pipelines.

    • Hardening and Configuration Requirements: Audit historical cloud storage access records for anomalous bulk transfers or credential changes around data synchronization accounts. Ensure all third-party integration pipelines operate under strict least-privilege configurations and utilize encrypted, monitored endpoints.

    • Coordination Tasks: Engage vendor risk assessment groups to re-verify security protocols for all third-party data handlers. Prepare communications frameworks with corporate public relations teams to handle potential supply chain exposure questions as the extortion deadline passes.

The chronologies of these active threat vectors span multiple weeks of identification, rapid exploitation tracking, and sudden escalation events across global networks.

  • LiteLLM Remote Code Execution Chain Timeline:

    • 2026-05-15: Independent security researchers at Obsidian Security and Horizon3.ai identify an unauthenticated remote code execution exploit path combining multiple vulnerabilities within BerriAI LiteLLM pipelines.

    • 2026-06-08: Following verified weaponization by threat actors against public and private server frameworks, CISA places CVE-2026-42271 within the Known Exploited Vulnerabilities catalog, establishing a binding mitigation target for federal agencies.

    • 2026-06-15: Threat management group Rescana releases an operational advisory detailing active exploitation mechanisms. The advisory notes that attackers are distributing backdoored variations of versions 1.82.7 and 1.82.8 across open source repositories.

    • 2026-06-17: Enterprise defensive groups coordinate global patch actions, focusing on upgrading installations to version 1.83.14-stable and conducting extensive key rotation campaigns.

  • Cisco Catalyst SD-WAN Manager File Write Timeline:

    • 2026-06-01: Cisco security specialists observe anomalies during internal testing and isolate early indicators of targeted exploitation targeting specific customer management planes.

    • 2026-06-15: Cisco PSIRT publishes an official vulnerability alert for CVE-2026-20262, simultaneously coordinating patch distribution.

    • 2026-06-15: CISA flags the vulnerability within the Known Exploited Vulnerabilities registry, mandating complete remediation for all federal civilian executive branch systems.

    • 2026-06-16: Security research teams at Tenable and SOC Prime deliver deep engineering reports and technical log indicators to assist blue teams with compromise assessments.

    • 2026-06-17: Global network administrators implement urgent firewall controls and begin checking application server logs for rogue web application deployments.

    • 2026-06-29: Target deadline for mandatory federal civilian executive branch patching under directive requirements.

  • SimpleHelp Authentication Bypass Timeline:

    • 2026-05-21: Cyber security researchers uncover the OpenID Connect identity assertion exploit path and provide comprehensive technical documentation to the vendor.

    • 2026-06-09: SimpleHelp publishes emergency updates including versions 5.5.16 and 6.0 RC2 to address the authentication bypass flaw.

    • 2026-06-12: Public vulnerability databases release formal listings for CVE-2026-48558, prompting wider security awareness.

    • 2026-06-14: Defensive response groups at Blackpoint Cyber and BleepingComputer release threat notices warning that laboratory tests confirm highly reliable exploit mechanics.

    • 2026-06-17: Active scanning activity escalates globally as defense teams work to secure an estimated 14,000 exposed systems.

  • FortiSandbox Exploit Trio Timeline:

    • 2026-04-15: Fortinet details underlying API flaws including CVE-2026-39813 and CVE-2026-39808, providing standard updates to their client base.

    • 2026-06-10: Internal code audits locate a parallel web interface vulnerability indexed as CVE-2026-25089, affecting web, cloud, and platform as a service iterations.

    • 2026-06-15: Threat intelligence specialists at Defused track active, multi-stage automated exploitation campaigns targeting unpatched installations using a combined exploit payload.

    • 2026-06-17: Security teams begin upgrading sandbox infrastructure and reviewing JSON API transaction records for unexpected administrative calls.

  • DragonForce SaaS Relay Campaign Timeline:

    • 2026-04-10: Threat actors exploit unpatched structured query language endpoints to compromise a major corporate services provider.

    • 2026-04-15 to 2026-06-14: DragonForce operatives maintain quiet access across the corporate environment. They execute lateral movement and stage internal data files while routing all command and control transactions through authorized Microsoft Teams relay paths.

    • 2026-06-15: Forensic response teams publish a comprehensive structural analysis outlining the Backdoor.Turn implant, process injection markers, and specific infrastructure domains.

    • 2026-06-17: Security operations centers ingest indicators of compromise to check for historical network matches across corporate collaboration channels.

  • Kodak Extortion Operation Timeline:

    • 2026-06-15: The ShinyHunters syndicate places Kodak on its commercial data leak portal, demanding payment contact and establishing an explicit negotiation deadline.

    • 2026-06-16: Kodak leadership issues a corporate statement acknowledging a temporary security compromise involving an isolated environment, while confirming that manufacturing and primary operations are unaffected.

    • 2026-06-17: Threat analysts monitor dark web communication channels for file sample leaks as the group's extortion clock runs down.

    • 2026-06-18: Scheduled extortion deadline established by the ShinyHunters syndicate.

Chapter 04 - Detection Intelligence

An engineering review of the primary threats highlights significant implementation flaws in data ingestion interfaces, token verification routines, and process isolation methods.

  • LiteLLM Command Injection Mechanics (CVE-2026-42271 Chain): The flaw stems from poor input sanitization within the Model Context Protocol testing components of BerriAI LiteLLM. When an administrator utilizes the /mcp-rest/test/connection endpoint, incoming parameters are passed directly to system command execution functions without parameterization. An attacker can inject shell metacharacters like semicolons, backticks, or vertical bars into these parameters to execute arbitrary code with the privileges of the LiteLLM container. When combined with CVE-2026-47101 and CVE-2026-47102, an attacker can bypass frontend proxy checks and elevate their privileges from a guest role to a full proxy administrator. This grants them the ability to intercept multi-vendor large language model token streams, extract stored API keys, and insert unauthorized guardrail code blocks.

  • Cisco Catalyst SD-WAN Manager Arbitrary File Write Mechanics (CVE-2026-20262): This vulnerability involves a classic directory traversal path vulnerability (CWE-22) embedded within the file upload API interface of the network management console. The endpoint fails to strip directory traversal sequences like ../ from the filename parameter in multipart form data submissions. An authenticated attacker can manipulate the destination path to place files outside the designated upload directory. By saving a custom web application archive file directly into the deployment directory of the internal WildFly application server, the container automatically unpacks and executes the payload. This establishes a persistent web shell that operates with the privileges of the application manager process. Attackers can then leverage local operating system configuration flaws to elevate their access to a root shell.

+----------------------------------------------------------------------------+
| [Step 1] Authenticate to SD-WAN Manager web UI with low-level credentials |
+----------------------------------------------------------------------------+
                                     |
                                     v
+----------------------------------------------------------------------------+
| [Step 2] Send HTTP POST containing path-traversal filename payload         |
|          Target Path: ../../jboss/standalone/deployments/malicious.war      |
+----------------------------------------------------------------------------+
                                     |
                                     v
+----------------------------------------------------------------------------+
| [Step 3] WildFly Application Server parses deployment directory and        |
|          auto-deploys the rogue Java archive payload                       |
+----------------------------------------------------------------------------+
                                     |
                                     v
+----------------------------------------------------------------------------+
| [Step 4] Access deployed web shell via internal service proxy paths        |
|          URL: /dataservice/proxy/malicious/shell.jsp                        |
+----------------------------------------------------------------------------+
                                     |
                                     v
+----------------------------------------------------------------------------+
| [Step 5] Execute arbitrary OS commands with process context privileges     |
|          and apply local exploits to seize root shell control

  • SimpleHelp OpenID Connect Token Forgery Mechanics (CVE-2026-48558): The SimpleHelp vulnerability involves a failure to validate token signatures and identity claims during OpenID Connect authentication workflows. When processing an authentication payload from a client, the server checks the group mapping claims but fails to cryptographically verify that the incoming token was signed by the configured identity provider. An attacker can set up a local token generation script, populate the email field with an arbitrary address, and set the group claim to match a privileged technician group. Upon receiving the forged assertion, SimpleHelp processes the login as valid, bypasses multi-factor authentication rules, creates a matching internal technician account, and opens a privileged support session.

  • FortiSandbox API and UI Command Injection Mechanics (Trio Flaws): The exploit path relies on a path traversal flaw inside the JSON Remote Procedure Call API (CVE-2026-39813) that allows attackers to access privileged method calls without providing an authentication token. Once bypassed, the attacker targets parallel vulnerabilities indexed as CVE-2026-39808 and CVE-2026-25089, which contain input sanitization errors within web dashboard parameters. The interface passes unsanitized user inputs to backend operating system command shells during diagnostic logging or file transfer tasks, allowing an unauthenticated remote attacker to execute arbitrary command strings.

  • DragonForce Backdoor.Turn Process Injection Architecture: The Backdoor.Turn implant is compiled via Go and employs advanced process injection tactics to evade host defenses. Upon execution, it calls standard API sequences like VirtualAllocEx, WriteProcessMemory, and CreateRemoteThread to inject its payload into the legitimate system logging helper DbgView64.exe. Once execution transfers to the remote thread, the malware opens outbound connections over secure HTTP ports. Instead of communicating with a dedicated server, it directs its traffic to legitimate Microsoft Teams relay nodes. The command and control data is encapsulated within standard session requests, allowing the backdoor to pass through corporate proxies and deep packet inspection firewalls without triggering alerts.

  • Third-Party Cloud Data Harvesting Patterns: While specific exploit code for the Kodak incident remains private, threat analysis of the ShinyHunters operation indicates a reliance on credential reuse or cloud storage access token theft. The group scans public code repositories for exposed configuration secrets or phishes employees of downstream analytics companies. Once they secure access to cloud database instances or bulk file storage buckets, they run automated extraction scripts to clone information repositories before the victim organization detects the data leak.

Comprehensive monitoring requires the integration of atomic indicators alongside system level behavioral patterns. While some campaigns do not present public file hashes, specific log strings serve as high fidelity detection signals.

+---------------+--------------------------------------+--------------------------------------+----------+
| Indicator Type| Value/Pattern Identifier             | Context Description                  | Status   |
+---------------+--------------------------------------+--------------------------------------+----------+
| Domain        | projetsmecanicos.com.br              | DragonForce Backdoor.Turn C2 Endpoint| Active   |
| Domain        | mysimerp.net                         | DragonForce Tool Retrieval Domain    | Active   |
| IP Address    | 62.164.177.25                        | Backdoor.Turn Command Infrastructure | Active   |
| URL           | 192.36.27.51/TechSupV18Fix3.zip      | Malicious Staging Tooling Archive    | Active   |
| Log String    | /mcp-rest/test/connection            | LiteLLM Exploitation Probe Attempt   | Threat   |
| Log String    | /mcp-rest/test/tools/list            | LiteLLM Target Scanning Phase        | Threat   |
| Log String    | vmanage-server.log (index.jsp)       | Cisco SD-WAN Web Shell Write Trigger | Critical |
| Log String    | server.log (Technician registration) | SimpleHelp Rogue Account Provision   | Critical

  • DragonForce Infrastructure Patterns:

    • Network Artifacts: The command and control nodes utilize standard hosting setups across international infrastructure providers to shield their primary servers.

    • Evasion Properties: The Backdoor.Turn implant encapsulates all operational instructions inside legitimate payload blocks directed to Microsoft Teams relay infrastructure. This prevents standard blocking mechanisms from closing the communications loop without impacting corporate communications.

  • Behavioral Infrastructure Identifiers:

    • Cisco Catalyst SD-WAN Manager Log Footprints: Exploitation attempts do not rely on static IP networks, choosing instead to route traffic through random virtual private networks. Blue teams must hunt for internal filesystem records tracking the sudden extraction of compressed web application files inside WildFly staging directories.

    • SimpleHelp Server Modifying Indicators: Threat indicators manifest as anomalous modifications to the default configuration schema located under /opt/SimpleHelp/logs/. These entries capture local technician registration flows executing outside scheduled deployment routines.

Blue teams must deploy multi layered detection models spanning security information event management platforms, endpoint protection suites, and network correlation logic to disrupt these operational paths.

  • LiteLLM API Gateway Attack Detection Engineering:

    • SIEM Field Extraction Logic: Security tools should process web server traffic to isolate incoming queries targeting Model Context Protocol subdirectories.

    • Detection Pattern: Flag any inbound HTTP POST requests containing symbols such as backticks, semicolons, or horizontal dividers inside parameters passed to /mcp-rest/test/.

    • EDR Process Containment Logic: Create immediate alerting definitions for situations where container processes associated with LiteLLM call low level operating system shells including /bin/sh, /bin/bash, or python package utilities.

    • Threat Hunting Stance: "Adversaries exploiting LiteLLM infrastructure will generate sequential test method queries followed immediately by outbound encrypted data flows directed toward untrusted external hosting environments." Focus historical validation over a trailing thirty day sequence.

  • Cisco Catalyst SD-WAN Manager Exploitation Detection Engineering:

    • SIEM Splunk Search Processing Language Template:

      index=cisco_sdwan sourcetype=vmanage_server 
      | search "index.jsp" OR "*.war" OR "../" OR "%2e%2e" 
      | eval risk_indicator = case(
          match(_raw, "index\.jsp|\.war"), "file_write_attempt",
          match(_raw, "\.\./|%2e%2e"), "path_traversal",
          true(), "unknown"
        )
      | stats count by src_ip, user, risk_indicator, _time 
      | where count > 0 
      | sort -_time 
      | eval priority = if(risk_indicator="file_write_attempt", "HIGH", "MEDIUM")
    • SIEM QRadar AQL Engine Correlation Template:

      SELECT sourceip, username, "File Write Indicator", logsourcename(logsourceid), starttime 
      FROM events 
      WHERE devicetype = 'CiscoSDWAN' 
        AND (UTF8(payload) ILIKE '%index.jsp%' 
          OR UTF8(payload) ILIKE '%.war%' 
          OR UTF8(payload) ILIKE '%../%' 
          OR UTF8(payload) ILIKE '%2e%2e%') 
      LAST 24 HOURS
    • Sigma Engineering Rule Definition (Pseudocode):

      title: Cisco SD-WAN Manager Suspicious File Upload (CVE-2026-20262)
      id: 4a2b1c3d-e5f6-7a8b-9c0d-1e2f3a4b5c6d
      status: experimental
      description: Detects suspicious JSP/WAR file upload attempts in Cisco Catalyst SD-WAN Manager logs indicative of CVE-2026-20262 exploitation
      logsource:
          category: application
          product: cisco-sdwan-manager
          service: vmanage-server
      detection:
          keywords_upload:
              message|contains:
                  - 'index.jsp'
                  - '.war'
                  - 'file upload'
                  - 'multipart'
          keywords_path_traversal:
              message|contains:
                  - '../'
                  - '%2e%2e'
                  - '%252e'
          api_endpoint:
              cs-uri-stem|contains:
                  - '/dataservice/template'
                  - '/dataservice/device/action'
          condition: keywords_upload OR (keywords_path_traversal AND api_endpoint)
      falsepositives:
          - Legitimate template uploads by authorized admins (tune by user/IP baseline)
      level: high
      tags:
          - attack.initial_access
          - attack.privilege_escalation
          - attack.t1190
          - attack.t1505.003
          - attack.t1548
          - cve.2026-20262
    • YARA File System Inspection Logic:

      rule Cisco_SDWAN_SuspiciousWAR_CVE_2026_20262 {
          meta:
              description = "Suspicious WAR/JSP artifact written to Cisco SD-WAN Manager filesystem"
              author = "Inferlume CTI"
              date = "2026-06-17"
              reference = "CVE-2026-20262"
              severity = "HIGH"
          strings:
              $jsp_exec1 = "Runtime.getRuntime().exec(" ascii
              $jsp_exec2 = "ProcessBuilder" ascii
              $jsp_exec3 = "cmd.exe" nocase ascii
              $jsp_exec4 = "/bin/bash" ascii
              $jsp_exec5 = "java.lang.Runtime" ascii
              $web_shell_marker = "<%@ page import=" ascii
              $war_magic = { 50 4B 03 04 }  // ZIP/WAR magic bytes
          condition:
              ($war_magic at 0) and (any of ($jsp_exec*) or $web_shell_marker)
      }
  • SimpleHelp Remote Portal Exploitation Detection Engineering:

    • Log Evaluation Directives: Review authentication transactions to extract entry creation sequences executed by OpenID Connect assertions where the source IP address coordinates outside standard operating constraints.

    • EDR Validation Logic: Monitor client machines for instances where SimpleHelp support tools trigger backend command processors or remote batch utilities.

  • DragonForce Teams Relay Egress Detection Engineering:

    • Host Process Injection Correlation: Create behavioral patterns tracking memory space injection events impacting DbgView64.exe.

    • Network Egress Optimization: Cross check active communication sessions hitting Microsoft Teams server addresses against endpoints hosting database software engines.

The structural mapping of active techniques isolates the precise actions executed by adversaries across current campaigns. This model prevents defensive gaps by tracing the complete life cycle of infrastructure compromises.

+-------------------------+-------------+-------------------------------------------------------------+
| ATT&CK Tactic           | Technique ID| Specific Operational Exploitation Mapping                   |
+-------------------------+-------------+-------------------------------------------------------------+
| Initial Access          | T1190       | Web UI vulnerability abuse across LiteLLM, Cisco, Fortinet  |
| Persistence             | T1505.003   | Malicious JSP/WAR file injection supporting long term access|
| Privilege Escalation    | T1548       | Local system elevation to exploit root contexts on managers |
| Defense Evasion         | T1078       | Use of valid low level write access credentials to authenticate|
| Defense Evasion         | T1055       | Backdoor.Turn code injection into DbgView64.exe frameworks  |
| Discovery               | T1083       | Automated filesystem scanning following root level takeover

  • Exploitation of Edge Services: Attackers manipulate input pathways inside web dashboards to establish a technical foothold without triggering perimeter validation blocks.

  • Web Shell Architecture Deployment: Adversaries inject custom code containers directly into backend web server processing engines, creating permanent, internal command pathways.

  • Privilege Elevation Vectors: Operating system configuration errors are weaponized locally to migrate low privilege web session access into full administrative control.

Chapter 05 - Governance, Risk & Compliance

Enterprise leadership must process these combined technical campaigns through a formal corporate governance lens to assess compliance liabilities and operational exposures.

  • LiteLLM Regulatory Impact:

    • Data Privacy Concerns: Data streams flowing through artificial intelligence proxies often contain sensitive enterprise records. Compromise of these streams may violate strict parameters defined within GDPR or DPDP frameworks.

    • Commercial Exposure: Incidents threaten core automation models, creating significant intellectual property exposure and driving immediate operational remediation costs.

  • Cisco Catalyst SD-WAN Manager Compliance Profile:

    • Critical Infrastructure Directives: Wide area network orchestration failures fall under the reporting thresholds of NIS2 and DORA frameworks, necessitating prompt disclosure to regulatory authorities.

    • CISO Strategic Stance: Upgrade the tracking priority of all management interface frameworks within corporate risk ledgers. Enforce continuous validation metrics.

  • SimpleHelp Remote Support Compliance Profile:

    • Third-Party Risk Concerns: Remote management exploitation allows attackers to move laterally across interconnected supplier networks, which triggers multi-jurisdictional breach reporting requirements.

    • Commercial Exposure: Threatens core client trust structures, exposing service providers to severe operational churn and potential breach of contract actions.

  • FortiSandbox Appliance Risk Profile:

    • Security Framework Standards: Failures in automated file validation mechanisms compromise the defensive baselines required by SOC2 and ISO27001 architectures.

    • CISO Strategic Stance: Ensure security teams run independent integrity checks across core security devices rather than assuming default configuration trust.

  • DragonForce Collaborative C2 Risk Profile:

    • Dwell Time Liabilities: The extended concealment achieved by routing traffic through trusted Software as a Service providers expands corporate data exposure windows.

    • Commercial Exposure: Drives significant forensic investigation outlays and highlights the need to re-evaluate cloud trust models.

  • Kodak Commercial Extortion Risk Profile:

    • Material Breaches: Public disclosures regarding stolen datasets draw immediate class-action litigation risks and require extensive notification operations.

    • CISO Strategic Stance: Conduct vendor threat reviews to limit data aggregation across third-party supply chain targets.

+------------------------------------+------------------------+---------------------------------------+
| Regulatory Target Context          | Primary Framework      | Mandated Remediation Window           |
+------------------------------------+------------------------+---------------------------------------+
| Federal Civilian Executive Branch  | CISA BOD 22-01         | Complete execution by 29 June 2026   |
| Critical Infrastructure Operators  | DORA / NIS2 Guidelines | Immediate incident threshold triage   |
| AI Data Processing Pipelines       | GDPR / DPDP Privacies  | Validation within 72 hour discovery

Chapter 06 - Adversary Emulation

Defenders should conduct controlled security exercises to validate that local detection rules can successfully catch the technical behaviors seen across today's infrastructure threat campaigns.

  • Cisco Catalyst SD-WAN Manager Emulation Flow:

    • Target Setup: Deploy a non-production instance running a vulnerable version of the management software with diagnostic logging enabled.

    • Emulation Execution Path: Authenticate via a low level test profile and transmit a multipart HTTP POST request containing directory traversal indicators targeting application deploy directories.

    • Verification Metrics: Verify that SIEM alerts correctly trigger on the presence of directory traversal characters and unexpected web archive creations.

    • Validation Bounds: "Perform all test executions inside isolated lab environments. Do not target production networking instances without explicit, written authorization."

  • LiteLLM Attack Path Emulation Flow:

    • Target Setup: Configure a test container executing an unpatched proxy version.

    • Emulation Execution Path: Deliver structured command injection strings directly into Model Context Protocol check subroutines.

    • Verification Metrics: Confirm that host monitoring tools flag the subsequent execution of system shell actions originating from the proxy application container space.

Intelligence Confidence82%

The confidence scoring framework balances strong validation indicators against specific gaps in threat actor visibility.

+-----------------------------------+---------------+------------------------------------+
| Evaluation Factor Criterion       | Weight Impact | Operational Assessment Evaluation  |
+-----------------------------------+---------------+------------------------------------+
| CISA KEV Registry Inclusion       | +25           | Confirmed active exploitation index|
| Cisco PSIRT Technical Advisory    | +20           | Authoritative vendor self disclosure|
| Multi Source Research Alignment   | +17           | Consistent reporting across peers  |
| Official NVD Record Synchronization| +10           | Confirmed vulnerability frameworks |
| Absence of Public Atomic Indicators| -10           | Constraints on immediate indicators|
| Incomplete Actor Attribution Telemetry -10         | Identity remains under attribution |
| Unverified Data Extortion Samples | -10           | Leak volume claims remain unproven

  • Positive Validation Indicators: The presence of vulnerabilities on the CISA Known Exploited Vulnerabilities catalog combined with formal vendor disclosures provides a highly reliable technical baseline for the Cisco, LiteLLM, and SimpleHelp campaigns.

  • Visibility Constraints: Operational visibility is limited by a lack of public atomic indicators for core networking flaws. This requires defenders to rely on behavioral hunting models rather than static blocklists. Concurrently, unconfirmed actor profiles for the active exploitation campaigns restrict multi incident tracking.