<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:content="http://purl.org/rss/1.0/modules/content/"><channel><title>Saas — CraftedSignal Threat Feed</title><link>https://feed.craftedsignal.io/tags/saas/</link><description>Trending threats, MITRE ATT&amp;CK coverage, and detection metadata — refreshed continuously.</description><generator>Hugo</generator><language>en</language><managingEditor>hello@craftedsignal.io</managingEditor><webMaster>hello@craftedsignal.io</webMaster><lastBuildDate>Thu, 09 Apr 2026 18:00:20 +0000</lastBuildDate><atom:link href="https://feed.craftedsignal.io/tags/saas/feed.xml" rel="self" type="application/rss+xml"/><item><title>SaaS Notification Pipeline Phishing and Medusa Ransomware Exploitation</title><link>https://feed.craftedsignal.io/briefs/2026-04-saas-phishing/</link><pubDate>Thu, 09 Apr 2026 18:00:20 +0000</pubDate><author>hello@craftedsignal.io</author><guid isPermaLink="true">https://feed.craftedsignal.io/briefs/2026-04-saas-phishing/</guid><description>Threat actors are weaponizing legitimate SaaS notification pipelines to deliver phishing and spam emails, bypassing traditional email authentication protocols, and Storm-1175 is exploiting CVE-2026-1731 to deploy Medusa ransomware.</description><content:encoded><![CDATA[<p>This threat brief highlights two significant attack vectors observed by Cisco Talos. First, threat actors are exploiting legitimate SaaS notification pipelines (e.g., GitHub, Jira) to deliver phishing and spam, bypassing traditional email security measures by using a &ldquo;Platform-as-a-Proxy&rdquo; (PaaP) technique. This abuses the implicit trust placed in system-generated notifications from trusted enterprise tools, primarily targeting credential harvesting. Second, the Storm-1175 group is actively deploying Medusa ransomware, rapidly exploiting n-day vulnerabilities, including CVE-2026-1731, a critical remote code execution flaw in BeyondTrust Remote Support and older versions of BeyondTrust Privileged Remote Access. Defenders must adapt to these evolving tactics, as they bypass standard perimeter defenses and require more nuanced detection strategies.</p>
<h2 id="attack-chain">Attack Chain</h2>
<ol>
<li>Attacker compromises a legitimate SaaS account (e.g., GitHub, Jira) or creates a malicious project.</li>
<li>Attacker configures the SaaS platform to send notifications (e.g., project updates, issue assignments).</li>
<li>The SaaS platform generates an email notification, appearing to originate from a trusted source.</li>
<li>The email bypasses traditional email security checks (SPF, DKIM, DMARC) due to its legitimate source.</li>
<li>The email contains a malicious link or attachment designed to harvest credentials or deliver malware.</li>
<li>The user clicks the link, leading to a phishing page or malware download.</li>
<li>If the user enters credentials, the attacker gains access to their account.</li>
<li>The attacker uses the compromised account for further malicious activities or lateral movement.</li>
</ol>
<h2 id="impact">Impact</h2>
<p>Successful exploitation of SaaS notification pipelines can lead to widespread credential compromise, potentially affecting numerous users within an organization. The &ldquo;automation fatigue&rdquo; associated with these notifications increases the likelihood of users falling victim to phishing attacks. Regarding Medusa ransomware, organizations face data encryption, system downtime, and potential financial losses from ransom demands, as Storm-1175 rapidly exploits vulnerabilities like CVE-2026-1731. The impact includes significant disruption to business operations and potential data breaches.</p>
<h2 id="recommendation">Recommendation</h2>
<ul>
<li>Ingest SaaS API logs into your SIEM to detect anomalous activities, such as suspicious project creation or mass invitations (see Overview).</li>
<li>Implement instance-level verification and cross-reference notifications against internal SaaS directories to detect PaaP attacks (see Overview).</li>
<li>Apply semantic intent analysis to identify notifications that deviate from a platform&rsquo;s established functional baseline (see Overview).</li>
<li>Patch CVE-2026-1731 on all BeyondTrust Remote Support instances immediately to prevent Medusa ransomware deployment (see Overview).</li>
<li>Deploy the Sigma rule to detect Coinminer malware via SHA256 hash (see Rules).</li>
<li>Monitor network connections for VID001.exe to identify potential Coinminer infections (see IOCs).</li>
</ul>
]]></content:encoded><category domain="severity">high</category><category domain="type">advisory</category><category>saas</category><category>phishing</category><category>ransomware</category><category>medusa</category></item><item><title>CrowdStrike Innovations Secure AI Agents and Govern Shadow AI</title><link>https://feed.craftedsignal.io/briefs/2026-03-shadow-ai-governance/</link><pubDate>Sat, 28 Mar 2026 21:52:45 +0000</pubDate><author>hello@craftedsignal.io</author><guid isPermaLink="true">https://feed.craftedsignal.io/briefs/2026-03-shadow-ai-governance/</guid><description>CrowdStrike is introducing innovations to secure AI agents and govern shadow AI across endpoints, SaaS, and cloud environments by extending AI detection and response (AIDR) capabilities to cover desktop AI applications and provide visibility into AI-related components, helping to prevent prompt attacks, data leaks, and policy violations.</description><content:encoded><![CDATA[<p>CrowdStrike is addressing the emerging threat landscape created by the rapid adoption of AI tools and agents within organizations. The increasing use of personal AI agents, particularly on developer machines, introduces new attack vectors such as &ldquo;living off the AI land&rdquo; (LOTAIL) exploits, indirect prompt injection, and agentic tool chain attacks. The rise of shadow AI, where employees adopt AI tools without oversight, exacerbates the issue. CrowdStrike&rsquo;s new innovations extend AI Detection and Response (AIDR) capabilities to cover desktop AI applications (ChatGPT, Gemini, Claude, DeepSeek, Microsoft Copilot, O365 Copilot, GitHub Copilot, and Cursor) and expand platform capabilities to secure AI workforce adoption and development across endpoints, SaaS environments, and cloud environments. Falcon AIDR will leverage the Falcon sensor to enable deployment of the Falcon AIDR browser extension from the Falcon console and obtain desktop application telemetry via the sensor&rsquo;s container network interface capability.</p>
<h2 id="attack-chain">Attack Chain</h2>
<ol>
<li><strong>Initial Access (via AI Agent):</strong> An attacker gains initial access by compromising an AI agent running on an endpoint, potentially through prompt injection or other vulnerabilities in the agent&rsquo;s design.</li>
<li><strong>Privilege Escalation:</strong> The attacker leverages the compromised AI agent&rsquo;s existing system permissions, which may be elevated, to gain further access to the system. AI agents often have high privileges to execute terminal commands, browse the web, and interact with files.</li>
<li><strong>Living off the AI Land (LOTAIL):</strong> The attacker uses the compromised AI agent to perform malicious actions that appear as legitimate user behavior, such as executing terminal commands, browsing websites, or interacting with files.</li>
<li><strong>Lateral Movement:</strong> The attacker utilizes the AI agent&rsquo;s network connectivity to discover and access other systems within the network, including LLM runtimes, MCP servers, and IDE extensions.</li>
<li><strong>Data Exfiltration:</strong> The attacker uses the AI agent to exfiltrate sensitive data from the compromised systems, such as source code, credentials, or other confidential information.</li>
<li><strong>Supply Chain Compromise:</strong> The attacker uses access to development environments via compromised AI tools to introduce malicious code into the software supply chain.</li>
<li><strong>Policy Violation:</strong> The attacker manipulates the AI agent to violate content policies or access control rules, potentially leading to unauthorized access to sensitive data or systems.</li>
</ol>
<h2 id="impact">Impact</h2>
<p>Successful attacks targeting AI agents and shadow AI can lead to significant data breaches, intellectual property theft, and supply chain compromises. The lack of visibility and governance over AI deployments creates a growing attack surface that traditional security controls are ill-equipped to handle. Compromised AI agents can be used to perform a wide range of malicious activities, including data exfiltration, lateral movement, and the introduction of malicious code into the software supply chain. The impact can range from financial losses and reputational damage to the compromise of critical infrastructure and sensitive government systems.</p>
<h2 id="recommendation">Recommendation</h2>
<ul>
<li>Deploy the Sigma rule &ldquo;AI Desktop Application Usage Detected&rdquo; to identify and monitor the use of AI desktop applications such as ChatGPT, Gemini, and others within your environment. This rule uses <code>process_creation</code> logs to detect the execution of these applications (see rule below).</li>
<li>Enable and configure AI Discovery in CrowdStrike Falcon Exposure Management to gain visibility into AI-related components running across endpoints, including AI apps, LLM runtimes, MCP servers, and IDE extensions. This leverages <code>Falcon for IT</code> telemetry as described in the overview.</li>
<li>Implement Falcon AIDR policies to monitor and protect agents built in Microsoft Copilot Studio against prompt injection attacks, data leaks, and policy violations.</li>
<li>Review and update access control policies for AI agents to minimize the potential impact of a compromise, focusing on the principle of least privilege.</li>
</ul>
]]></content:encoded><category domain="severity">medium</category><category domain="type">advisory</category><category>AI</category><category>AI-Security</category><category>Shadow-AI</category><category>Endpoint-Security</category><category>SaaS</category><category>Cloud</category></item><item><title>M-Trends 2026: Evolving Threat Landscape</title><link>https://feed.craftedsignal.io/briefs/2026-06-mtrends-2026/</link><pubDate>Wed, 25 Mar 2026 10:45:30 +0000</pubDate><author>hello@craftedsignal.io</author><guid isPermaLink="true">https://feed.craftedsignal.io/briefs/2026-06-mtrends-2026/</guid><description>The M-Trends 2026 report highlights the increasing sophistication of threat actors, including voice phishing attacks targeting SaaS environments, ransomware groups actively destroying recovery capabilities, and espionage groups exploiting edge devices for persistent access, revealing a shift towards faster hand-offs between initial access brokers and ransomware deployers.</description><content:encoded><![CDATA[<p>The Mandiant M-Trends 2026 report analyzes over 500,000 hours of incident investigations, revealing significant shifts in the cyber threat landscape. Cybercriminal groups are optimizing for immediate impact and recovery denial, while cyber espionage groups and insider threats prioritize extreme persistence, leveraging unmonitored edge devices and native network functionalities to evade detection. Voice phishing has surged, replacing email as a primary initial access vector, particularly targeting SaaS environments. The time between initial access and the hand-off to secondary actors deploying ransomware has collapsed dramatically. Targeted industries include the high-tech sector (17%) and the financial sector (14.6%). Ransomware groups are now actively targeting backup infrastructure, identity services, and virtualization management planes to ensure recovery is impossible without paying a ransom. Espionage groups are exploiting zero-day vulnerabilities in edge devices for long-term persistence.</p>
<h2 id="attack-chain">Attack Chain</h2>
<ol>
<li><strong>Initial Access:</strong> Attackers use voice phishing (vishing) to target IT help desks, bypassing MFA and gaining initial access to SaaS environments. Malicious advertisements or the ClickFix social engineering technique are also used to gain a foothold.</li>
<li><strong>Privilege Escalation:</strong> Exploitation of misconfigured Active Directory Certificate Services templates to create admin accounts that bypass password rotation.</li>
<li><strong>Credential Access:</strong> Harvesting long-lived OAuth tokens and session cookies to bypass standard defenses. Stealing hard-coded keys and personal access tokens from compromised third-party SaaS vendors. Leveraging native packet-capturing functionality on network appliances to intercept sensitive data and plaintext credentials.</li>
<li><strong>Lateral Movement:</strong> Using stolen credentials and tokens to pivot into downstream customer environments. Exploiting the &ldquo;Tier-0&rdquo; nature of hypervisors to bypass guest-level defenses.</li>
<li><strong>Defense Evasion:</strong> Deploying custom, in-memory malware like BRICKSTORM directly onto network appliances to establish deep persistence that survives standard remediation efforts. Targeting edge and core network devices lacking EDR telemetry.</li>
<li><strong>Impact:</strong> Encrypting hypervisor datastores to render all associated virtual machines inoperable simultaneously. Deleting backup objects from cloud storage.</li>
<li><strong>Exfiltration:</strong> Large-scale data theft from SaaS environments.</li>
</ol>
<h2 id="impact">Impact</h2>
<p>M-Trends 2026 highlights that ransomware groups are actively destroying the ability to recover data, impacting organizations across more than 16 industry verticals. The high-tech and financial sectors are particularly targeted. The collapse of the hand-off window from hours to seconds means organizations have less time to respond to initial intrusions before ransomware is deployed. The increasing dwell time of threats like BRICKSTORM, reaching nearly 400 days, leaves organizations blind to the full scope of the intrusion due to standard log retention policies.</p>
<h2 id="recommendation">Recommendation</h2>
<ul>
<li>Deploy the Sigma rule for detecting PowerShell commands from uncommon locations to identify potential malicious activity related to post-compromise actions (reference: Sigma rule &ldquo;Detect PowerShell from Uncommon Location&rdquo;).</li>
<li>Implement network monitoring on edge devices and VPNs to detect unauthorized packet capturing and credential interception attempts (reference: overview section about edge devices).</li>
<li>Review and harden Active Directory Certificate Services configurations to prevent the exploitation of misconfigured templates (reference: attack chain step 2).</li>
<li>Monitor for modifications to cloud storage backup objects, especially deletion attempts, to detect ransomware groups attempting to destroy recovery capabilities (reference: attack chain step 6).</li>
<li>Increase log retention policies beyond 90 days to improve visibility into long-term persistent threats like BRICKSTORM (reference: Overview section).</li>
</ul>
]]></content:encoded><category domain="severity">high</category><category domain="type">threat</category><category>threat-report</category><category>ransomware</category><category>phishing</category><category>saas</category></item></channel></rss>