Back to all articles

Securing the Network Perimeter Against High-Velocity Threats and AI Vulnerabilities

With malicious actors reducing their vulnerability targeting cycles to mere hours, security teams face growing pressure to rapidly secure perimeter assets. This briefing examines the swift methodologies of groups like Storm-1175, details emerging AI prompt injection risks in tools like Grafana, and provides concrete hardening guidance to protect organizational infrastructure.

Triage Security Media Team
4 min read

The operational window for security teams to address new vulnerabilities is frequently measured in hours rather than weeks or days. The current environment involves continuous pressure from financially motivated malicious actors who have optimized their workflows to identify and target exposed perimeter assets. A primary example is the group tracked as Storm-1175. This group rapidly utilizes newly disclosed vulnerabilities to deploy Medusa ransomware, occasionally completing the sequence from initial access to data exfiltration in under 24 hours.

This compressed timeline, documented in recent reports from Microsoft Threat Intelligence and industry researchers, marks a shift in how ransomware groups interact with the vulnerability management lifecycle. Storm-1175 does not solely rely on public disclosures. In several instances, the group has leveraged zero-day vulnerabilities at least a week before public acknowledgment. This operational pace indicates the group may possess advanced internal development capabilities or access to specialized vulnerability brokers, enabling them to move faster than the standard patching cycles of many enterprise organizations.

These high-velocity campaigns have primarily affected the healthcare, education, professional services, and finance sectors, specifically within the United States, United Kingdom, and Australia. By targeting critical vulnerabilities in web-facing infrastructure, including remote support tools and file transfer software—Storm-1175 bypasses the traditional phishing-based entry methods that many security programs monitor. Instead, the group focuses on direct unauthorized access through the network perimeter.

While Storm-1175 illustrates the risk of rapid vulnerability targeting in traditional software, the integration of artificial intelligence introduces a different category of exposure. Security researchers recently identified a prompt injection vulnerability in Grafana’s AI assistant, designated "GrafanaGhost," which could have allowed unauthorized parties to access sensitive telemetry or financial data. Grafana has since patched the issue, but the discovery shows that as organizations adopt AI components to manage their environments, they inadvertently expand their digital footprint. This expansion includes risks like indirect prompt injection, a technique where unsafe instructions are hidden in data the AI processes.

From a technical standpoint, Storm-1175 operates with notable efficiency. Their recent activity includes the rapid targeting of CVE-2026-1731, a critical remote code execution vulnerability in BeyondTrust Remote Support. The group targeted this flaw almost immediately following its February 6 disclosure, leading to its inclusion in CISA’s Known Exploited Vulnerabilities (KEV) catalog just a week later. The group's "N-day" toolset is extensive, covering critical flaws in CrushFTP (CVE-2025-31161), JetBrains TeamCity (CVE-2024-27198), and older Microsoft Exchange vulnerabilities (CVE-2023-21529) that remain unpatched in various environments.

The group's use of undisclosed vulnerabilities presents a more complex challenge for defensive teams. Researchers linked Storm-1175 to the targeting of CVE-2026-23760, an authentication bypass in SmarterMail, and CVE-2025-10035, a maximum-severity flaw in GoAnywhere Managed File Transfer. In both instances, the group was active approximately seven days before public awareness of the issues. Once initial access is secured, the group follows a standardized sequence: they deploy legitimate remote monitoring and management (RMM) tools for lateral movement, use the Impacket framework for credential extraction, and utilize Rclone for data transfer before deploying ransomware.

A key technical component of the Medusa deployment is the group’s focus on security tampering. Storm-1175 actors modify Windows registry settings to interfere with Microsoft Defender Antivirus, effectively disabling endpoint detection so the ransomware can run unhindered. This technique requires highly privileged access, which makes the credential extraction phase, specifically the use of Impacket—a vital intervention point for defensive teams seeking to protect their environments.

The GrafanaGhost vulnerability details a different mechanism for unauthorized access. Researchers at Noma Security found they could bypass Grafana's image rendering protections by using protocol-relative URLs and a specific "INTENT" keyword within image tags. By placing these unintended instructions in a location the AI assistant naturally retrieves. Such as an entry log—the researchers could cause the AI to send sensitive data to an external server. There is a discrepancy between the researchers and the vendor regarding the interaction requirements for this flaw. Grafana Labs states that significant user interaction was necessary to trigger the bug, whereas the researchers report that the AI processed the instructions autonomously. Regardless of the interaction requirements, the core issue was remediated through a patch to Grafana’s Markdown renderer.

To protect their organizations, security teams must reduce the "mean time to patch" (MTTP) for critical perimeter assets to the absolute minimum. When a critical remote code execution or authentication bypass flaw is disclosed in a web-facing service, we recommend prioritizing the patch immediately, often within the same business day. This rapid response helps organizations stay ahead of the 24-hour targeting cycle observed in Storm-1175 operations.

Beyond patching, infrastructure hardening is essential for comprehensive protection. Organizations should prioritize the isolation of web-facing systems, placing any necessary public servers behind a Web Application Firewall (WAF) or within a strictly segmented DMZ. To counter the specific tampering techniques seen in Medusa deployments, security teams should enable Windows Defender Antivirus tamper protection and apply the DisableLocalAdminMerge setting. This configuration prevents malicious actors including using local admin privileges and establish antivirus exclusions. Furthermore, implementing Windows Credential Guard helps protect process memory including the credential extraction methods that Storm-1175 relies on to gain the privileges necessary for security tampering.

The high-tempo operations of Storm-1175 indicate that ransomware groups are increasingly mirroring the capabilities of state-sponsored actors in their ability to operationalize vulnerabilities. This structured approach and vulnerability targeting means that reactive security postures are no longer sufficient. Security programs must transition toward a model of continuous exposure management, ensuring the perimeter is consistently audited for the exposed assets that groups like Storm-1175 look for.

While prompt injection risks in tools like Grafana represent emerging methods for data access, the most immediate risk remains the rapid targeting of the network edge. The connection between these two areas is the credential. Whether an unauthorized party uses an N-day vulnerability or a prompt injection technique, the objective is often the privilege escalation required for broad environment control. Security teams that focus on hardening the identity layer while simultaneously narrowing their patching windows will be best positioned to protect their organizations against this cycle of high-velocity threats.