<?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/" xmlns:webfeeds="http://webfeeds.org/rss/1.0"><channel><title>Google Workspace - CraftedSignal Threat Feed</title><link>https://feed.craftedsignal.io/products/google-workspace/</link><description>Trending threats, MITRE ATT&amp;CK coverage, and detection metadata. Fed continuously.</description><generator>Hugo</generator><language>en</language><managingEditor>hello@craftedsignal.io</managingEditor><webMaster>hello@craftedsignal.io</webMaster><lastBuildDate>Thu, 29 Oct 2026 15:52:40 +0000</lastBuildDate><atom:link href="https://feed.craftedsignal.io/products/google-workspace/feed.xml" rel="self" type="application/rss+xml"/><image><url>https://feed.craftedsignal.io/favicon-32x32.png</url><title>CraftedSignal Threat Feed</title><link>https://feed.craftedsignal.io/</link><width>32</width><height>32</height></image><webfeeds:icon>https://feed.craftedsignal.io/favicon.svg</webfeeds:icon><item><title>Credential phishing campaign abusing AI themes and CAPTCHA evasion</title><link>https://feed.craftedsignal.io/briefs/2026-10-anthropic-phishing/</link><pubDate>Thu, 29 Oct 2026 15:52:40 +0000</pubDate><author>hello@craftedsignal.io</author><guid isPermaLink="true">https://feed.craftedsignal.io/briefs/2026-10-anthropic-phishing/</guid><description>Since September 2026, threat actors have leveraged fake Anthropic AI preview invitations, abused legitimate services, and utilized multi-layer CAPTCHA bypasses to harvest Google and Microsoft credentials.</description><content:encoded><![CDATA[<p>A credential phishing campaign identified by Cofense targets organizations with invitations to a fraudulent &quot;Anthropic AI&quot; private preview. The campaign successfully bypasses standard email security by abusing trusted platforms including GoTo Webinar, Zapier, and Cloudflare. The infrastructure utilizes multiple CAPTCHA challenges to impede automated sandbox analysis and credential harvesting pages designed to impersonate Google and Microsoft authentication portals.</p>
<h2 id="attack-chain">Attack Chain</h2>
<ol>
<li>Initial outreach via an email appearing to come from GoTo Webinar claiming to offer an exclusive Anthropic AI preview.</li>
<li>The email contains a link shortened through a legitimate service (Zapier) to evade email filtering.</li>
<li>Clicking the link triggers a Cloudflare CAPTCHA to verify the visitor.</li>
<li>The victim is redirected to a spoofed Zoom-branded meeting registration page.</li>
<li>The victim interacts with the registration form and selects &quot;Continue with Google&quot; or &quot;Continue with Microsoft&quot;.</li>
<li>A custom CAPTCHA slider appears to block automated scanners and VPN traffic.</li>
<li>A spoofed credential harvesting page captures the user email or login information.</li>
</ol>
<h2 id="impact">Impact</h2>
<p>Successful phishing leads to the compromise of corporate identity credentials, allowing attackers to access sensitive documentation or use the account for further internal infiltration.</p>
<h2 id="recommendation">Recommendation</h2>
<ul>
<li>Block the identified malicious domains at the web proxy and DNS levels.</li>
<li>Implement email authentication controls (DMARC/SPF/DKIM) to protect your domain and improve visibility into spoofed sender activity.</li>
<li>Advise employees to manually inspect URL domains for mismatches rather than relying on the branding present in the email or landing page.</li>
<li>Evaluate web filtering solutions that allow for browser isolation or manual analysis of sites that employ multi-stage CAPTCHA redirects.</li>
</ul>
]]></content:encoded><category domain="severity">high</category><category domain="type">advisory</category><category>phishing</category><category>credential-harvesting</category><category>social-engineering</category><category>cloud</category></item><item><title>APT Spear-Phishing Campaign Targeting Taiwan Research Organizations via AI-Assisted Lures and AitM</title><link>https://feed.craftedsignal.io/briefs/2026-10-uat-11985/</link><pubDate>Thu, 08 Oct 2026 10:33:40 +0000</pubDate><author>hello@craftedsignal.io</author><guid isPermaLink="true">https://feed.craftedsignal.io/briefs/2026-10-uat-11985/</guid><description>An APT actor is targeting Taiwan-based researchers with AI-assisted event-themed spear-phishing and quishing, leveraging an adversary-in-the-middle (AitM) framework to intercept Google credentials and bypass MFA.</description><content:encoded><![CDATA[<p>Cisco Talos has identified a coordinated spear-phishing campaign attributed to an advanced persistent threat (APT) actor targeting research organizations in Taiwan. The campaign exploits the reputation of academic and policy institutions to distribute invitations to fake, high-profile events. The threat actor employs AI-assisted content generation to create formulaic but highly personalized phishing lures, incorporating grandiose policy jargon to establish authority.</p>
<p>The delivery mechanisms include traditional email spear-phishing and QR code phishing (quishing), where malicious codes are embedded in scraped legitimate event posters. The campaign stands out for its use of an advanced adversary-in-the-middle (AitM) phishing framework. This framework utilizes a hybrid HTTP and WebSocket architecture to synchronize authentication workflows with legitimate Google services in real time, allowing the actor to intercept primary credentials and bypass MFA challenges seamlessly. Linguistic analysis of the phishing kit suggests a developer fluent in Simplified Chinese, with potential mainland-Chinese lexical origins. The campaign represents a sophisticated evolution in infrastructure, combining social engineering at scale with real-time credential theft.</p>
<h2 id="attack-chain">Attack Chain</h2>
<ol>
<li>The actor scrapes legitimate public event data and posters from official institutional websites.</li>
<li>The actor uses AI-assisted templates to generate personalized invitation lures featuring professional flattery and specific geopolitical contexts.</li>
<li>Phishing lures are distributed via email, some containing modified posters with malicious QR codes (quishing) for physical-to-digital attack pivoting.</li>
<li>Emails contain hyperlinked registration buttons where the visible text presents a benign domain (e.g., Google Forms) but the underlying href directs victims to actor-controlled infrastructure.</li>
<li>Upon clicking the link, the victim is presented with a proxy interface that clones a legitimate Google authentication page.</li>
<li>The AitM framework uses a hybrid HTTP/WebSocket connection to proxy the user's interaction with the actual Google authentication backend in real time.</li>
<li>The actor captures the submitted credentials and the secondary MFA token as they are relayed through the framework.</li>
<li>The final objective is the unauthorized takeover of Google Workspace accounts belonging to researchers, enabling exfiltration or lateral movement.</li>
</ol>
<h2 id="impact">Impact</h2>
<p>The primary impact is the unauthorized compromise of research credentials, potentially leading to the exfiltration of sensitive policy, geopolitical analysis, or intellectual property held by Taiwan-based institutions. The use of AitM frameworks renders standard MFA ineffective, significantly lowering the barrier for account takeover. The campaign's use of quishing also broadens the scope of impact, potentially compromising personnel who are not the original email recipients but encounter the malicious posters in public or internal office spaces.</p>
<h2 id="recommendation">Recommendation</h2>
<ul>
<li>Implement phishing-resistant MFA, such as FIDO2/WebAuthn hardware security keys, which are natively immune to AitM credential harvesting.</li>
<li>Configure email security gateways to perform deep URL inspection and alert on discrepancies between visible link text and actual destination domains.</li>
<li>Conduct employee awareness training focusing on the risks of QR code (quishing) scanning in unverified physical materials.</li>
<li>Implement and enforce strict conditional access policies, such as geo-blocking or device health attestation, for all Google Workspace access.</li>
<li>Monitor proxy and firewall logs for unusual WebSocket traffic patterns directed toward non-standard or newly registered domains.</li>
</ul>
]]></content:encoded><category domain="severity">high</category><category domain="type">advisory</category><category>phishing</category><category>spear-phishing</category><category>aitm</category><category>quishing</category><category>google-workspace</category></item><item><title>Detection of Google Workspace Suspicious Login Events</title><link>https://feed.craftedsignal.io/briefs/2026-09-gworkspace-suspicious-login/</link><pubDate>Thu, 24 Sep 2026 12:13:04 +0000</pubDate><author>hello@craftedsignal.io</author><guid isPermaLink="true">https://feed.craftedsignal.io/briefs/2026-09-gworkspace-suspicious-login/</guid><description>Google Workspace audit logs identify suspicious authentication attempts including unauthorized application access, programmatic login anomalies, and general suspicious sign-in events.</description><content:encoded><![CDATA[<p>Google Workspace maintains audit logs that categorize specific login activities as suspicious based on Google's internal heuristics. These events, reported via the 'login.googleapis.com' service within GCP/Workspace audit logs, flag sign-in attempts that deviate from established patterns or violate security policies. Specifically, the system identifies three primary categories: standard suspicious logins, usage of less secure applications, and anomalous programmatic login patterns. Monitoring these audit events is critical for detecting potential account takeover, credential harvesting, or automated abuse by malicious actors targeting corporate identities. Defenders should ingest these audit logs to identify compromised accounts, unauthorized third-party integrations, and automated exploitation of service accounts.</p>
<h2 id="impact">Impact</h2>
<p>Successful exploitation of account credentials or programmatic interfaces can lead to unauthorized data exfiltration, persistent access to organizational resources, and the use of the corporate environment as a platform for further lateral movement or phishing campaigns.</p>
<h2 id="recommendation">Recommendation</h2>
<ol>
<li>Configure GCP Admin Audit logs to export 'login.googleapis.com' event data to a centralized SIEM or security data lake.</li>
<li>Deploy the Sigma detection rule below to flag and alert on 'suspicious_login', 'suspicious_login_less_secure_app', and 'suspicious_programmatic_login' event names.</li>
<li>Perform regular reviews of flagged accounts to distinguish between malicious activity and misconfigured but legitimate legacy applications.</li>
</ol>
]]></content:encoded><category domain="severity">medium</category><category domain="type">advisory</category><category>cloud</category><category>identity-security</category><category>gcp</category><category>gworkspace</category></item><item><title>Operation Fake KickOff: Attackers Abuse Recruiters and SaaS to Harvest Work Credentials</title><link>https://feed.craftedsignal.io/briefs/2026-07-operation-fake-kickoff/</link><pubDate>Wed, 15 Jul 2026 20:50:29 +0000</pubDate><author>hello@craftedsignal.io</author><guid isPermaLink="true">https://feed.craftedsignal.io/briefs/2026-07-operation-fake-kickoff/</guid><description>O-UNC-038 is conducting a multi-stage Adversary-in-the-Middle (AiTM) phishing operation that abuses legitimate SaaS platforms and recruiter identities to steal corporate Google Workspace credentials and bypass multi-factor authentication.</description><content:encoded><![CDATA[<p>Intel 471 has investigated &quot;Operation Fake KickOff,&quot; an ongoing, multi-stage phishing campaign attributed to O-UNC-038, which has been active since at least April 2025. This operation systematically abuses legitimate software-as-a-service (SaaS) platforms like Salesforce, SendGrid, and Zoho for email distribution to orchestrate corporate credential theft. Attackers impersonate real recruiters from major global brands across 15 industry verticals, primarily human resources consulting, to lure victims to deceptive, corporate-themed interview-scheduling interfaces. An adversary-in-the-middle (AiTM) toolkit, leveraging the Browser-in-the-Box (BitB) technique, is then deployed to harvest corporate Google Workspace credentials and live session tokens in real time, effectively bypassing standard multi-factor authentication (MFA) mechanisms. The campaign has identified 232 dedicated phishing domains and 80 command-and-control (C2) servers, with stolen data exfiltrated to Render cloud hosting infrastructure and subsequently to Telegram bots.</p>
<h2 id="attack-chain">Attack Chain</h2>
<ol>
<li>Attackers use legitimate SaaS marketing and email-delivery platforms such as Salesforce, SendGrid, and Zoho to distribute email lures.</li>
<li>Email lures impersonate real recruiters from well-known organizations across various industries, often using typosquatted domains like <code>fifahr-careers.com</code> or <code>adidas-hiring.com</code>.</li>
<li>Victims click on links within these emails, directing them to deceptive landing pages designed to mimic standard interview-scheduling interfaces, such as Calendly.</li>
<li>The phishing landing page performs email validation, blocking standard personal email providers and compelling victims to enter corporate email addresses.</li>
<li>Upon corporate email submission, the page initiates an Adversary-in-the-Middle (AiTM) attack, presenting a visually identical Google sign-in replica page via the Browser-in-the-Box (BitB) technique within the current tab to harvest credentials.</li>
<li>As victims enter their corporate Google Workspace credentials, the AiTM toolkit orchestrates MFA bypasses by dynamically prompting for various second-factor challenges, including email codes, TOTP from Google Authenticator, SMS codes, and Google prompt notifications.</li>
<li>The attackers capture corporate Google Workspace credentials and live session tokens in real-time as they are entered and authenticated.</li>
<li>Stolen credentials and session data are transmitted via HTTP POST requests to C2 servers hosted primarily on the Render cloud platform (<code>onrender.com</code>) and then exfiltrated downstream to Telegram bots.</li>
</ol>
<h2 id="impact">Impact</h2>
<p>This operation has resulted in the theft of corporate Google Workspace login credentials and live session tokens, effectively bypassing multi-factor authentication. Organizations across 15 distinct industry verticals have been impersonated, with human resources consulting firms accounting for approximately 54% of observed phishing infrastructure. The campaign has been active since April 2025 and continues to successfully deploy live phishing pages and harvest corporate access, leading to unauthorized access to enterprise cloud environments. The broad impersonation and abuse of legitimate SaaS platforms increase the success rate of the attacks, making them difficult for targeted users to discern.</p>
<h2 id="recommendation">Recommendation</h2>
<ul>
<li>Deploy Sigma rules detecting suspicious DNS queries to <code>onrender.com</code>, as this domain is used for C2 infrastructure.</li>
<li>Implement Sigma rules identifying suspicious network connections to <code>onrender.com</code> from corporate endpoints.</li>
<li>Enhance email gateway and proxy logs monitoring for phishing attempts originating from legitimate SaaS platforms (e.g., Salesforce, SendGrid, Zoho) but redirecting to external, typosquatted, or unknown domains.</li>
<li>Conduct regular security awareness training emphasizing the risks of sophisticated phishing, recruiter impersonation, and the visual cues of legitimate OAuth pop-ups versus in-tab login redirects.</li>
<li>Implement FIDO2 or other phishing-resistant MFA solutions where feasible to mitigate the risk of AiTM attacks and session token theft.</li>
</ul>
]]></content:encoded><category domain="severity">high</category><category domain="type">threat</category><category>phishing</category><category>credential-theft</category><category>aitm</category><category>social-engineering</category><category>mfa-bypass</category><category>saas-abuse</category><category>google-workspace</category></item><item><title>Google Security Updates — July 2026</title><link>https://feed.craftedsignal.io/briefs/2026-07-google-security-updates/</link><pubDate>Fri, 03 Jul 2026 10:41:13 +0000</pubDate><author>hello@craftedsignal.io</author><guid isPermaLink="true">https://feed.craftedsignal.io/briefs/2026-07-google-security-updates/</guid><description>Roundup of Google security advisories published in July 2026.</description><content:encoded><![CDATA[<p>Aggregated Google security advisories for July 2026. CVEs from this cycle are folded
into the list below as they are published.</p>
<h2 id="recommendation">Recommendation</h2>
<p>Review affected products and apply Google's July 2026 security updates.</p>
]]></content:encoded><category domain="severity">high</category><category domain="type">advisory</category><category>roundup</category></item><item><title>Google Workspace Custom Admin Role Created for Persistence</title><link>https://feed.craftedsignal.io/briefs/2026-06-google-workspace-custom-admin-role-created/</link><pubDate>Thu, 18 Jun 2026 15:32:16 +0000</pubDate><author>hello@craftedsignal.io</author><guid isPermaLink="true">https://feed.craftedsignal.io/briefs/2026-06-google-workspace-custom-admin-role-created/</guid><description>Adversaries may create custom administrative roles in Google Workspace to establish persistence with tailored, elevated permissions, which are then assigned to compromised or attacker-controlled accounts to bypass security controls, grant OAuth access, or modify mail routing.</description><content:encoded><![CDATA[<p>Adversaries targeting Google Workspace environments may create custom administrative roles to establish a persistent foothold and achieve granular, elevated privileges. Unlike predefined admin roles, custom roles allow threat actors to craft permissions precisely tailored to their objectives, such as modifying security controls, granting illicit OAuth access, or altering mail routing. This technique enables attackers to maintain access and perform follow-on actions even if initial access vectors are remediated or the original compromised account is secured. The creation of such a role, often followed by assigning it to a compromised or attacker-controlled account, provides a stealthy persistence mechanism that avoids alerting on modifications to well-known prebuilt roles. This activity, observed in various cloud environments, highlights the need for continuous monitoring of IAM changes.</p>
<h2 id="attack-chain">Attack Chain</h2>
<ol>
<li>An attacker gains unauthorized access to a Google Workspace administrator account, typically through phishing, credential compromise, or exploitation of vulnerabilities.</li>
<li>The attacker logs into the Google Workspace Admin Console using the compromised administrative credentials, assuming the identity of a legitimate administrator.</li>
<li>Within the Admin Console, the attacker navigates to the 'Admin roles' section to initiate the creation of a new custom administrative role.</li>
<li>The attacker defines specific, granular privileges for the new custom role, carefully selecting permissions that align with their objectives (e.g., user management, security settings, Gmail routing).</li>
<li>To establish persistence, the attacker assigns this newly created custom role to a pre-existing compromised user account or a newly provisioned attacker-controlled account, granting it the defined permissions.</li>
<li>With the custom role assigned, the attacker can now leverage its tailored permissions to maintain access, bypass security controls, modify system configurations, or exfiltrate data, even if the initial administrator account's access is revoked.</li>
</ol>
<h2 id="impact">Impact</h2>
<p>Successful exploitation of this technique grants adversaries persistent and tailored access to the Google Workspace environment, enabling them to bypass existing security controls and perform various malicious activities. Attackers can modify critical security settings, grant unauthorized OAuth access to third-party applications, alter mail routing rules for data exfiltration or interception, or manipulate user accounts. The granular nature of custom roles makes detection challenging, potentially leading to prolonged undetected access, significant data breaches, and compromise of the organization's communication and collaboration infrastructure.</p>
<h2 id="recommendation">Recommendation</h2>
<ul>
<li>Deploy the Sigma rule &quot;Google Workspace Custom Admin Role Created&quot; in this brief to your SIEM and tune for your environment.</li>
<li>Configure Google Workspace logging to capture <code>CREATE_ROLE</code> and <code>ASSIGN_ROLE</code> events to ensure visibility into administrative changes.</li>
<li>Review Google Workspace admin logs for <code>event.action: ASSIGN_ROLE</code> actions following a detected <code>CREATE_ROLE</code> event to identify principals receiving the new role.</li>
<li>Reduce the <code>var.interval</code> of the Google Workspace Filebeat module to 10 minutes (from the default 2 hours) to minimize event lag as described in the Setup section.</li>
</ul>
]]></content:encoded><category domain="severity">medium</category><category domain="type">advisory</category><category>google-workspace</category><category>cloud-security</category><category>persistence</category><category>privilege-escalation</category><category>iam</category></item><item><title>Google Workspace Admin Role Assigned to a User or Group</title><link>https://feed.craftedsignal.io/briefs/2026-06-google-workspace-admin-role-assigned/</link><pubDate>Thu, 18 Jun 2026 15:31:12 +0000</pubDate><author>hello@craftedsignal.io</author><guid isPermaLink="true">https://feed.craftedsignal.io/briefs/2026-06-google-workspace-admin-role-assigned/</guid><description>Adversaries leverage the assignment of administrative roles within Google Workspace to an existing or new user/group, establishing persistence and escalating privileges to gain broad control over the tenant, including bypassing single sign-on.</description><content:encoded><![CDATA[<p>Adversaries are known to target cloud environments like Google Workspace to establish persistent access and escalate privileges. A critical technique involves assigning administrative roles, such as the <code>SUPER_ADMIN_ROLE</code> or other <code>*_ADMIN_ROLE</code> types, to existing or newly created user accounts or groups. This action, often occurring post-initial compromise, grants attackers broad control over the Google Workspace tenant, including the ability to manage users, devices, security settings, and applications. Such elevated privileges enable adversaries to bypass security mechanisms like Single Sign-On (SSO), ensure long-term presence, and facilitate follow-on activities like data exfiltration, modifying mail routing, or altering other critical configurations, posing a significant risk to organizational data and operations.</p>
<h2 id="attack-chain">Attack Chain</h2>
<ol>
<li><strong>Initial Compromise</strong>: Adversary obtains initial access to a Google Workspace account, potentially an administrator account or an account with privileges to create users or manage groups.</li>
<li><strong>Privilege Discovery</strong>: The adversary identifies existing user accounts or creates new ones that can be granted elevated administrative roles within Google Workspace.</li>
<li><strong>Role Assignment</strong>: The adversary assigns a high-privilege administrative role (e.g., <code>SUPER_ADMIN_ROLE</code>, <code>GROUP_ADMIN_ROLE</code>) to a compromised or newly created user account or an existing group.</li>
<li><strong>Persistence Establishment</strong>: The elevated role provides the adversary with sustained access to the Google Workspace environment, often bypassing standard security controls like Single Sign-On (SSO).</li>
<li><strong>Further Actions</strong>: Utilizing the newly acquired administrative privileges, the adversary performs additional malicious activities, such as creating OAuth tokens, modifying security controls, changing mail routing, or altering SSO settings.</li>
<li><strong>Data Exfiltration/Impact</strong>: The adversary may then proceed with data exfiltration, service disruption, or other objectives, maintaining broad control over the tenant's identity, device, and application settings.</li>
</ol>
<h2 id="impact">Impact</h2>
<p>The successful assignment of administrative roles to an adversary-controlled account grants comprehensive control over the affected Google Workspace tenant. This can lead to unauthorized access to sensitive organizational data, alteration of critical security controls (such as SSO settings), disruption of email communications, and creation of backdoors (e.g., OAuth tokens) for sustained access. Organizations across all sectors are vulnerable, and the impact can range from severe data breaches and compliance failures to operational paralysis and reputational damage.</p>
<h2 id="recommendation">Recommendation</h2>
<ul>
<li>Deploy the Sigma rules in this brief to your SIEM and tune for your environment, specifically focusing on <code>google_workspace.admin.role.name</code> values.</li>
<li>Ensure Google Workspace Admin logs are being ingested into your security monitoring platform to enable detection of <code>event.action: &quot;ASSIGN_ROLE&quot;</code> events.</li>
<li>Regularly audit existing administrative role assignments within Google Workspace, paying close attention to <code>*_ADMIN_ROLE</code> types.</li>
<li>Implement security best practices outlined by Google, available at <code>https://support.google.com/a/answer/7587183</code>.</li>
<li>Investigate <code>user.email</code> and <code>source.ip</code> for any user performing <code>ASSIGN_ROLE</code> actions that appear unusual.</li>
</ul>
]]></content:encoded><category domain="severity">high</category><category domain="type">advisory</category><category>cloud-security</category><category>google-workspace</category><category>persistence</category><category>privilege-escalation</category><category>account-manipulation</category><category>saas-security</category></item><item><title>Google Workspace Admin Role Deletion</title><link>https://feed.craftedsignal.io/briefs/2026-06-google-workspace-admin-role-deletion/</link><pubDate>Thu, 18 Jun 2026 15:30:09 +0000</pubDate><author>hello@craftedsignal.io</author><guid isPermaLink="true">https://feed.craftedsignal.io/briefs/2026-06-google-workspace-admin-role-deletion/</guid><description>Adversaries with elevated privileges within Google Workspace may delete custom administrative roles to impede security operations, remove delegated administrator access, or obfuscate their activities during an active incident, leading to disrupted delegated administration, loss of security team access, or hindrance of incident response efforts.</description><content:encoded><![CDATA[<p>Adversaries with elevated privileges within Google Workspace may delete custom administrative roles to impede security operations, remove delegated administrator access, or obfuscate their activities during an active incident. This action, often observed post-compromise, targets roles specifically configured for security teams or those granting granular access to critical services like audit logs or user management. The deletion of a custom role immediately revokes all associated privileges from assigned users and groups, potentially creating significant operational disruption and blind spots for defenders. Understanding the details of such deletions requires thorough review of historical audit logs to reconstruct the role's original permissions and assigned principals. This tactic hinders incident response capabilities and allows threat actors to maintain persistence or further their objectives undetected.</p>
<h2 id="attack-chain">Attack Chain</h2>
<ol>
<li><strong>Initial Access</strong>: An attacker gains unauthorized access to a Google Workspace administrator account, often through phishing, credential stuffing, or exploiting a vulnerable connected application.</li>
<li><strong>Privilege Escalation/Maintenance</strong>: The attacker leverages the compromised account, or further elevates privileges if necessary, to ensure sufficient permissions to modify or delete administrative roles within Google Workspace.</li>
<li><strong>Reconnaissance</strong>: The attacker enumerates existing custom administrative roles to identify those granting sensitive permissions, particularly roles held by security personnel or those with broad access to audit logs or security settings.</li>
<li><strong>Defense Evasion Preparation</strong>: The attacker plans to remove roles that could enable detection or response, such as roles held by incident responders or those that monitor critical security events.</li>
<li><strong>Admin Role Deletion</strong>: The attacker executes the deletion of one or more identified custom administrative roles via the Google Admin console or API, specifying the <code>google_workspace.admin.role.name</code>. This action triggers an <code>event.action: DELETE_ROLE</code> in audit logs.</li>
<li><strong>Impact Activation</strong>: The deletion instantly revokes all associated privileges from users and groups previously assigned to the role, leading to disrupted delegated administration, loss of security team access, or hindrance of incident response efforts.</li>
<li><strong>Continued Operations</strong>: With security monitoring or administrative oversight potentially impaired, the attacker proceeds with their primary objectives, such as data exfiltration or further system compromise, with reduced risk of detection.</li>
</ol>
<h2 id="impact">Impact</h2>
<p>The deletion of custom administrative roles in Google Workspace can severely impact an organization's security posture and operational continuity. It directly results in the immediate revocation of privileges for all users and groups previously assigned to the deleted role, potentially disrupting delegated administration and critical security functions. This action can blind security teams to ongoing threats by removing their access to audit logs or security settings, thereby hindering incident response efforts. Organizations may experience operational downtime, increased risk of data breaches, or delayed threat containment due to compromised administrative capabilities. Understanding the full blast radius requires reviewing historical audit logs to identify all affected principals and permissions, complicating recovery.</p>
<h2 id="recommendation">Recommendation</h2>
<ul>
<li>Enable comprehensive logging for Google Workspace administrative events, specifically ensuring <code>data_stream.dataset: google_workspace.admin</code> and <code>event.action: DELETE_ROLE</code> are collected and forwarded to your SIEM.</li>
<li>Deploy the <code>Detect Google Workspace Admin Role Deletion</code> and <code>Detect Google Workspace Admin Role Unassignment</code> Sigma rules in this brief to your SIEM and tune for your environment.</li>
<li>Upon detection of admin role deletion or unassignment, immediately investigate the <code>user.email</code> and <code>source.ip</code> of the initiating account, and the <code>google_workspace.admin.role.name</code> affected.</li>
<li>Cross-reference all role deletion/unassignment events with approved change management requests and validate the authorization of the performing administrator to distinguish between legitimate and malicious activity.</li>
<li>If an unauthorized role deletion is confirmed, prioritize recreating the affected role with equivalent privileges and reassigning previously impacted users and groups to restore critical administrative functions.</li>
</ul>
]]></content:encoded><category domain="severity">medium</category><category domain="type">advisory</category><category>cloud</category><category>google-workspace</category><category>identity-and-access-audit</category><category>impact</category><category>defense-evasion</category><category>admin-role-deletion</category></item><item><title>Google Workspace User Organizational Unit Changed</title><link>https://feed.craftedsignal.io/briefs/2026-05-google-workspace-user-ou-change/</link><pubDate>Fri, 29 May 2026 15:15:18 +0000</pubDate><author>hello@craftedsignal.io</author><guid isPermaLink="true">https://feed.craftedsignal.io/briefs/2026-05-google-workspace-user-ou-change/</guid><description>Detects when a Google Workspace user's organizational unit is changed, potentially indicating an adversary attempting to inherit permissions and gain unauthorized access to resources and applications.</description><content:encoded><![CDATA[<p>This detection rule identifies when a user's organizational unit is changed within Google Workspace. Google Workspace organizational units are used to manage access and permissions for groups of users. An attacker who has compromised a valid account may attempt to move that account to a different organizational unit to inherit permissions to applications and resources that were previously inaccessible. This can facilitate privilege escalation and lateral movement within the Google Workspace environment. The rule leverages Google Workspace admin audit logs to detect <code>MOVE_USER_TO_ORG_UNIT</code> events, providing visibility into potentially malicious configuration changes. This rule is designed for production environments.</p>
<h2 id="attack-chain">Attack Chain</h2>
<ol>
<li>An attacker compromises a Google Workspace user account through credential theft or other means.</li>
<li>The attacker authenticates to the Google Workspace admin console using the compromised account.</li>
<li>The attacker navigates to the user management section of the admin console.</li>
<li>The attacker locates the target user account whose privileges they want to escalate.</li>
<li>The attacker modifies the organizational unit assignment for the target user.</li>
<li>The attacker moves the target user to an organizational unit with higher privileges or access to sensitive resources.</li>
<li>The target user now inherits the permissions and privileges associated with the new organizational unit.</li>
<li>The attacker leverages the newly acquired privileges to access restricted applications, data, or resources within the Google Workspace environment.</li>
</ol>
<h2 id="impact">Impact</h2>
<p>A successful attack could allow an adversary to escalate privileges within the Google Workspace environment, gain access to sensitive data, and potentially compromise critical business applications. While the rule's severity is low, the impact of a successful privilege escalation can be significant. It is important to investigate all instances of organizational unit changes to determine if they are legitimate.</p>
<h2 id="recommendation">Recommendation</h2>
<ul>
<li>Deploy the Sigma rule to your SIEM to detect unauthorized organizational unit changes.</li>
<li>Investigate any alerts generated by the Sigma rule, focusing on identifying the actor, target user, and the previous and new organizational units involved.</li>
<li>Review the permissions assigned to the implicated user to ensure that the least privilege principle is being followed.</li>
<li>Reduce the interval that the Google Workspace Filebeat module polls Google's reporting API for new events to minimize potential false negatives. Refer to the <a href="https://www.elastic.co/guide/en/beats/filebeat/current/filebeat-module-google_workspace.html">Filebeat module documentation</a>.</li>
<li>Implement security best practices outlined by Google to protect against account compromise and privilege escalation. See <a href="https://support.google.com/a/answer/7587183">Google Workspace security best practices</a>.</li>
</ul>
]]></content:encoded><category domain="severity">low</category><category domain="type">advisory</category><category>cloud</category><category>google_workspace</category><category>persistence</category><category>privilege_escalation</category></item><item><title>Google Workspace Suspended User Account Renewed</title><link>https://feed.craftedsignal.io/briefs/2026-05-google-workspace-suspended-user-renewed/</link><pubDate>Fri, 29 May 2026 15:15:03 +0000</pubDate><author>hello@craftedsignal.io</author><guid isPermaLink="true">https://feed.craftedsignal.io/briefs/2026-05-google-workspace-suspended-user-renewed/</guid><description>Detection of a renewed suspended user account in Google Workspace, potentially indicating an adversary regaining access to the organization.</description><content:encoded><![CDATA[<p>This detection identifies when a previously suspended user's account is renewed in Google Workspace. Attackers may reactivate suspended accounts to regain unauthorized access, circumventing security measures. Google Workspace administrators use suspended user accounts to remove access while transferring documents and roles before complete account deletion. This rule focuses on the <code>UNSUSPEND_USER</code> event within Google Workspace admin logs, aiding analysts in identifying potential misuse of account reactivation and maintaining secure access controls. The rule is configured to run every 10 minutes with a lookback time of 130 minutes to account for Google Workspace event lag times which can range from minutes up to 3 days.</p>
<h2 id="attack-chain">Attack Chain</h2>
<ol>
<li>An attacker compromises a Google Workspace administrator account or gains unauthorized access.</li>
<li>The attacker identifies a suspended user account within the Google Workspace environment.</li>
<li>Using the compromised administrator account, the attacker executes the <code>UNSUSPEND_USER</code> action.</li>
<li>The Google Workspace account is reactivated, granting the attacker access to associated services.</li>
<li>The attacker leverages the renewed account to access sensitive data and resources.</li>
<li>The attacker may then escalate privileges, move laterally, or establish persistence.</li>
<li>The attacker exfiltrates data or performs other malicious activities within the Google Workspace environment.</li>
</ol>
<h2 id="impact">Impact</h2>
<p>A successful attack could allow unauthorized access to sensitive data within Google Workspace, potentially leading to data breaches, financial losses, or reputational damage. Even though the severity is low, it can be part of a broader attack that leads to sensitive information getting into the wrong hands.</p>
<h2 id="recommendation">Recommendation</h2>
<ul>
<li>Deploy the Sigma rule <code>Google Workspace Suspended User Account Renewed</code> to your SIEM and tune for your environment.</li>
<li>Review the event logs for the <code>UNSUSPEND_USER</code> action to identify the user account that was renewed and gather details about the timing and context of the action.</li>
<li>Investigate the identity of the administrator or service account that performed the <code>UNSUSPEND_USER</code> action to determine if the action was authorized.</li>
<li>Implement additional monitoring on affected accounts to detect any further suspicious activity.</li>
</ul>
]]></content:encoded><category domain="severity">low</category><category domain="type">advisory</category><category>google_workspace</category><category>initial_access</category><category>persistence</category></item><item><title>External User Added to Google Workspace Group</title><link>https://feed.craftedsignal.io/briefs/2026-05-external-user-added-to-google-workspace-group/</link><pubDate>Fri, 29 May 2026 15:14:51 +0000</pubDate><author>hello@craftedsignal.io</author><guid isPermaLink="true">https://feed.craftedsignal.io/briefs/2026-05-external-user-added-to-google-workspace-group/</guid><description>Detects an external Google Workspace user account being added to an existing group, potentially allowing adversaries to intercept shared files or emails.</description><content:encoded><![CDATA[<p>This detection rule identifies instances where an external user account is added to an existing Google Workspace group within an organization. Adversaries may leverage this technique to gain unauthorized access to shared resources, intercept sensitive communications, or potentially weaponize documents shared with editorial privileges for further intrusion. The rule focuses on identifying scenarios where the domain name of the user being added does not match the Google Workspace domain of the target organization, indicating an external user account. This activity can be indicative of initial access or persistence attempts by malicious actors seeking to compromise an organization's Google Workspace environment. The rule is designed to run every 10 minutes with a lookback time of 130 minutes, accounting for potential lag times in Google Workspace event logs.</p>
<h2 id="attack-chain">Attack Chain</h2>
<ol>
<li><strong>Initial Compromise:</strong> An attacker compromises a legitimate user account within the organization or uses social engineering to trick an administrator.</li>
<li><strong>Privilege Escalation (if needed):</strong> The attacker may attempt to escalate privileges to gain the necessary permissions to add users to Google Workspace groups.</li>
<li><strong>Target Group Selection:</strong> The attacker identifies a Google Workspace group containing valuable information or critical communications.</li>
<li><strong>External Account Creation:</strong> The attacker creates an external Google account (e.g., a @gmail.com account) or uses a pre-existing one.</li>
<li><strong>Group Membership Modification:</strong> The attacker adds the external account to the selected Google Workspace group using the compromised or tricked admin account.</li>
<li><strong>Data Interception:</strong> The external account now receives all communications and has access to resources shared with the group, allowing the attacker to intercept data.</li>
<li><strong>Lateral Movement/Further Exploitation:</strong> The attacker uses the intercepted data to gain further access to the organization's systems, launch further attacks, or exfiltrate sensitive information.</li>
</ol>
<h2 id="impact">Impact</h2>
<p>A successful attack can lead to unauthorized access to sensitive data shared within the Google Workspace group, including confidential documents, internal communications, and proprietary information. This can result in data breaches, financial losses, reputational damage, and potential legal liabilities. The compromise can also serve as a stepping stone for further attacks, such as lateral movement within the organization's network or the deployment of malware. The severity depends on the sensitivity of the data shared within the compromised group.</p>
<h2 id="recommendation">Recommendation</h2>
<ul>
<li>Deploy the provided Sigma rule to your SIEM to detect external users being added to Google Workspace groups, and tune the rule based on your environment (see rule titled &quot;Detect External User Added to Google Workspace Group&quot;).</li>
<li>Review the permissions assigned to users who have the ability to add members to Google Workspace groups, ensuring that the principle of least privilege is followed.</li>
<li>Investigate any alerts generated by this rule by reviewing the <code>user.name</code> or <code>user.email</code> and <code>user.target.email</code> fields to identify the user who added the external member and the external user added.</li>
<li>Monitor Google Workspace logs for other suspicious activity, such as unauthorized access attempts or unusual changes to group memberships.</li>
<li>Implement security defaults as <a href="https://cloud.google.com/security-command-center/docs/how-to-investigate-threats">provided by Google</a>.</li>
</ul>
]]></content:encoded><category domain="severity">medium</category><category domain="type">advisory</category><category>google_workspace</category><category>initial_access</category><category>persistence</category><category>cloud</category></item><item><title>Google Workspace Drive Data Transfer or Takeout Export Initiated</title><link>https://feed.craftedsignal.io/briefs/2026-05-google-workspace-drive-data-transfer/</link><pubDate>Thu, 28 May 2026 15:40:55 +0000</pubDate><author>hello@craftedsignal.io</author><guid isPermaLink="true">https://feed.craftedsignal.io/briefs/2026-05-google-workspace-drive-data-transfer/</guid><description>This rule detects when Google Workspace administrators initiate bulk movement or export of user Drive data, including admin data transfer requests and Customer Takeout export jobs which can be abused by adversaries with administrative access to stage or exfiltrate sensitive files.</description><content:encoded><![CDATA[<p>The Google Workspace environment allows administrators to perform bulk data transfers of user Drive files to other in-domain accounts, as well as create Customer Takeout exports that package user or organizational data for download or transfer to external destinations. An adversary with compromised administrator credentials may abuse these features to collect sensitive files without needing to modify per-file sharing permissions. This activity is often conducted during the collection and exfiltration phases of an attack. The rule detects <code>CREATE_DATA_TRANSFER_REQUEST</code> events with Drive application scope and <code>CUSTOMER_TAKEOUT_CREATED</code> events within Google Workspace admin logs, providing visibility into potential data theft by malicious insiders or external attackers who have gained administrative privileges. Defenders should investigate any unexpected data transfer or takeout export activities to determine their legitimacy and potential impact.</p>
<h2 id="attack-chain">Attack Chain</h2>
<ol>
<li>An attacker gains unauthorized access to a Google Workspace administrator account, potentially through credential compromise or phishing.</li>
<li>The attacker authenticates to the Google Workspace Admin console using the compromised credentials.</li>
<li>The attacker initiates a data transfer request to reassign a user's Drive files to another account within the same Google Workspace domain using <code>CREATE_DATA_TRANSFER_REQUEST</code>.</li>
<li>Alternatively, the attacker initiates a Customer Takeout export job (<code>CUSTOMER_TAKEOUT_CREATED</code>) to package organizational data for download. This may involve specifying a Google-provided bucket or a customer-owned Cloud Storage location.</li>
<li>The Google Workspace system processes the data transfer or export request.</li>
<li>For data transfer requests, the designated target account receives ownership or access to the transferred files.</li>
<li>For Customer Takeout exports, the data is packaged into an archive.</li>
<li>The attacker downloads the archive from the designated storage location or accesses the data through the target account, achieving exfiltration or staging of sensitive data.</li>
</ol>
<h2 id="impact">Impact</h2>
<p>A successful attack could result in the exfiltration of sensitive company data, intellectual property, or personal information stored within Google Drive. The number of affected users depends on the scope of the data transfer or takeout export. Targeted sectors could vary depending on the nature of the compromised administrator account and the data it has access to. The damage could include financial loss, reputational damage, legal liabilities, and compromise of competitive advantages.</p>
<h2 id="recommendation">Recommendation</h2>
<ul>
<li>Deploy the Sigma rule &quot;Google Workspace Drive Data Transfer or Takeout Export Initiated&quot; to your SIEM to detect suspicious data transfer or takeout export activities.</li>
<li>Review admin logs for involved user accounts as described in the rule's &quot;Possible investigation steps&quot; section.</li>
<li>For Customer Takeout events, pivot on <code>google_workspace.admin.OBFUSCATED_CUSTOMER_TAKEOUT_REQUEST_ID</code> in Elasticsearch to find related admin events for the same export job.</li>
<li>Implement security best practices outlined by Google to prevent credential compromise and unauthorized access to administrator accounts as referenced in the <a href="https://support.google.com/a/answer/7587183">Google security best practices</a> reference.</li>
<li>Monitor the <code>user.email</code>, <code>user.target.email</code>, and <code>google_workspace.admin.new_value</code> fields in the logs to track the initiator, source, and destination users involved in data transfer requests.</li>
<li>Reduce the interval that the Google Workspace Filebeat module polls Google's reporting API for new events to mitigate event lag times as mentioned in the Setup section.</li>
</ul>
]]></content:encoded><category domain="severity">medium</category><category domain="type">advisory</category><category>google_workspace</category><category>data_exfiltration</category><category>cloud</category></item><item><title>Google Workspace Device Registration Burst for Single User</title><link>https://feed.craftedsignal.io/briefs/2026-05-google-workspace-device-registration-burst/</link><pubDate>Thu, 28 May 2026 14:10:07 +0000</pubDate><author>hello@craftedsignal.io</author><guid isPermaLink="true">https://feed.craftedsignal.io/briefs/2026-05-google-workspace-device-registration-burst/</guid><description>Detects bursts of Google Workspace device registration events for a single user exceeding three distinct device registrations within one minute, indicative of AiTM phishing or stolen OAuth token replay attacks.</description><content:encoded><![CDATA[<p>This detection identifies anomalous Google Workspace device registration activity indicative of adversary-in-the-middle (AiTM) phishing or stolen OAuth token replay attacks. The rule focuses on bursts of <code>DEVICE_REGISTER_UNREGISTER_EVENT</code> logs where a single user registers three or more distinct device IDs within a one-minute window. While legitimate session/sync registrations can trigger this event, a high-cardinality burst is rare and suggests malicious activity, such as a phishing kit relaying user sign-ins or token-replay tooling driving multiple sessions against a stolen OAuth refresh token. This activity can lead to account compromise, data exfiltration, and unauthorized access to Google Workspace resources. The rule leverages Google Workspace device logs.</p>
<h2 id="attack-chain">Attack Chain</h2>
<ol>
<li>The attacker initiates a phishing campaign targeting Google Workspace users (T1566).</li>
<li>The victim clicks a malicious link, leading to an AiTM phishing kit or a credential harvesting page (T1566.001).</li>
<li>The attacker relays the victim's credentials to Google, successfully authenticating and bypassing multi-factor authentication (MFA) if present (T1557).</li>
<li>The attacker's relay or stolen OAuth token replay tooling registers multiple device contexts in rapid succession, generating multiple <code>DEVICE_REGISTER_UNREGISTER_EVENT</code> logs with distinct <code>google_workspace.device.id</code> values (T1098.005).</li>
<li>The attacker leverages the newly registered devices or replayed tokens to gain persistent access to the victim's Google Workspace account (T1078.004).</li>
<li>The attacker performs unauthorized actions, such as accessing sensitive data, modifying account settings, or sending malicious emails (T1530).</li>
</ol>
<h2 id="impact">Impact</h2>
<p>Successful exploitation can lead to account compromise, unauthorized access to sensitive data within Google Workspace, and potential business email compromise (BEC). The attacker could exfiltrate data, modify account settings, or use the compromised account to further propagate attacks within the organization. The impact is magnified if the compromised user has elevated privileges or access to critical resources.</p>
<h2 id="recommendation">Recommendation</h2>
<ul>
<li>Deploy the provided Sigma rule <code>Detect Google Workspace Device Registration Burst for Single User</code> to detect suspicious bursts of device registrations (Log Source: Google Workspace Device Logs).</li>
<li>Investigate users triggering the rule, focusing on device fingerprint consistency and preceding login events, as described in the rule's <code>note</code> section.</li>
<li>Cross-reference <code>logs-google_workspace.login</code> events for successful logins preceding the burst, examining <code>source.geo.country_name</code>, <code>source.as.organization.name</code>, and <code>user_agent.original</code> for anomalies.</li>
<li>Revoke OAuth tokens for affected users (<code>DELETE /admin/directory/v1/users/&lt;email&gt;/tokens/&lt;clientId&gt;</code>) if compromise is suspected, as mentioned in the rule's <code>note</code> section.</li>
</ul>
]]></content:encoded><category domain="severity">medium</category><category domain="type">advisory</category><category>google_workspace</category><category>device_registration</category><category>persistence</category><category>initial_access</category><category>credential_access</category></item><item><title>Google Workspace User Sign-in from Atypical Device Type</title><link>https://feed.craftedsignal.io/briefs/2026-05-google-workspace-atypical-device/</link><pubDate>Thu, 28 May 2026 14:09:50 +0000</pubDate><author>hello@craftedsignal.io</author><guid isPermaLink="true">https://feed.craftedsignal.io/briefs/2026-05-google-workspace-atypical-device/</guid><description>This rule detects when a Google Workspace user authenticates from a device type that hasn't been observed for that user in the past 14 days, potentially indicating account compromise via AiTM kits or stolen OAuth refresh tokens.</description><content:encoded><![CDATA[<p>This detection rule identifies anomalous Google Workspace device registrations, specifically focusing on deviations from a user's typical device type. It leverages Google Workspace device logs to detect when a user authenticates from a device type (e.g., WINDOWS, MAC, ANDROID, IOS, LINUX) that has not been associated with them within a 14-day historical window. The rule does not flag new physical device enrollments, as the Google Reports API generates fresh device IDs on each event. Instead, it highlights situations where an attacker, using compromised credentials obtained through AiTM kits or stolen OAuth tokens, accesses a Workspace account from a device type different from the user's established pattern. This is a strong indicator of compromise, as these kits often relay sessions through unusual device fingerprints, such as a Windows session for a macOS user, or concurrent sessions from different OS types. Because refresh tokens persist across password resets, focus on token revocation for remediation.</p>
<h2 id="attack-chain">Attack Chain</h2>
<ol>
<li>Attacker compromises a user's Google Workspace credentials through AiTM phishing or steals an OAuth refresh token.</li>
<li>Attacker uses the stolen credentials or token to authenticate to Google Workspace.</li>
<li>Google Workspace logs a <code>DEVICE_REGISTER_UNREGISTER_EVENT</code> with a new <code>google_workspace.device.id</code> associated with the session.</li>
<li>The attacker accesses Google Workspace resources like Gmail, Drive, or Calendar.</li>
<li>The attacker may create new OAuth tokens for persistence.</li>
<li>The attacker exfiltrates sensitive data.</li>
<li>The attacker may attempt to move laterally to other cloud resources accessible via the compromised account.</li>
<li>The attacker persists by maintaining access through the stolen credentials and newly created OAuth tokens.</li>
</ol>
<h2 id="impact">Impact</h2>
<p>A successful attack can result in unauthorized access to sensitive data within Google Workspace, including emails, documents, and calendar information. Attackers can exfiltrate data, escalate privileges, and potentially move laterally to other cloud resources. The compromise can persist even after a password reset due to the nature of OAuth refresh tokens. Affected sectors depend on the victim organization but may include any industry using Google Workspace.</p>
<h2 id="recommendation">Recommendation</h2>
<ul>
<li>Deploy the Sigma rule &quot;Google Workspace User Sign-in from Atypical Device Type&quot; to detect anomalous device registrations (rule).</li>
<li>When an atypical device registration is detected, immediately suspend the user, revoke all OAuth tokens, reset the password, and clear recovery email/phone, as detailed in the rule's &quot;Response and remediation&quot; section.</li>
<li>Investigate <code>logs-google_workspace.login</code> events for the same user in the 24 hours leading up to the device registration, looking for suspicious ASN, country, and user agent patterns, as described in the rule's &quot;Possible investigation steps&quot; section.</li>
<li>Monitor <code>logs-google_workspace.token</code> events for <code>event.action: &quot;authorize&quot;</code> events around the device registration time to identify newly minted OAuth tokens (rule's &quot;Possible investigation steps&quot;).</li>
</ul>
]]></content:encoded><category domain="severity">medium</category><category domain="type">advisory</category><category>google_workspace</category><category>persistence</category><category>account_compromise</category><category>device_registration</category></item><item><title>Google Workspace Device Registration After OAuth from Suspicious ASN</title><link>https://feed.craftedsignal.io/briefs/2026-05-google-workspace-device-registration/</link><pubDate>Mon, 18 May 2026 10:29:07 +0000</pubDate><author>hello@craftedsignal.io</author><guid isPermaLink="true">https://feed.craftedsignal.io/briefs/2026-05-google-workspace-device-registration/</guid><description>Detects a sequence of events in Google Workspace where OAuth authorization from a suspicious ASN is immediately followed by device registration, potentially indicating attacker-controlled device enrollment after user authorization of a sensitive client, possibly related to Tycoon2FA.</description><content:encoded><![CDATA[<p>This detection identifies suspicious Google Workspace device registrations potentially linked to compromised accounts or malicious device enrollment. The rule focuses on detecting a specific sequence of events: a user authorizing a Google OAuth client from a high-risk Autonomous System Number (ASN), followed closely by a device registration event with the device's account state set to &quot;REGISTERED&quot;. The goal is to identify instances where attackers might be using compromised credentials or residential proxies to enroll devices into an organization's Google Workspace environment after gaining unauthorized OAuth access. This activity has been linked to threat actors such as Tycoon2FA and is further detailed in Elastic's Google Workspace attack surface research.</p>
<h2 id="attack-chain">Attack Chain</h2>
<ol>
<li>Attacker gains access to user credentials through phishing (T1566.002) or other methods.</li>
<li>Attacker uses compromised credentials to initiate OAuth authorization for a sensitive Google OAuth client (client ID: 77185425430.apps.googleusercontent.com) from a high-risk ASN (e.g., 9009, 45102, 215540, 29802, 62240, 204957, 395092).</li>
<li>User unknowingly grants OAuth permissions to the malicious application.</li>
<li>Immediately following OAuth authorization, the attacker triggers a device registration event within Google Workspace.</li>
<li>The device registration event reports the account state as &quot;REGISTERED,&quot; indicating successful device enrollment.</li>
<li>The attacker can then potentially access sensitive data or perform actions as the user from the newly registered device.</li>
<li>The attacker leverages the registered device for persistence and lateral movement within the Google Workspace environment (T1098.005).</li>
<li>The final objective can include data exfiltration, business email compromise, or further compromise of other accounts and systems within the organization.</li>
</ol>
<h2 id="impact">Impact</h2>
<p>Successful exploitation can lead to unauthorized access to sensitive Google Workspace data, including emails, documents, and applications. This can result in data breaches, financial loss, and reputational damage. The attacker can potentially maintain persistence within the Google Workspace environment, allowing them to continue accessing and manipulating data over an extended period. This rule aims to detect early stages of this attack, potentially preventing a full compromise of the victim's Google Workspace account.</p>
<h2 id="recommendation">Recommendation</h2>
<ul>
<li>Deploy the provided Sigma rule to your SIEM to detect suspicious Google Workspace device registrations following OAuth authorization from high-risk ASNs. Tune the rule for your environment based on known VPNs and trusted ASNs.</li>
<li>Investigate any alerts generated by the Sigma rule by reviewing <code>user.name</code>, <code>user.email</code>, <code>source.ip</code>, <code>source.as.organization.name</code>, and <code>google_workspace.token.client.id</code> from the logs.</li>
<li>Review and restrict OAuth app access policies within Google Workspace to prevent unauthorized applications from gaining access to sensitive data.</li>
<li>Monitor Google Workspace <code>google_workspace.token</code> and <code>google_workspace.device</code> audit streams as mentioned in the setup section to ingest relevant events.</li>
<li>Consider increasing the <code>from</code> field to account for Google Workspace event lag, as suggested in the documentation.</li>
</ul>
]]></content:encoded><category domain="severity">high</category><category domain="type">advisory</category><category>cloud</category><category>google-workspace</category><category>persistence</category><category>initial-access</category><category>tycoon2fa</category></item><item><title>ClickFix 'BackgroundFix' Campaign Delivers CastleLoader, NetSupport RAT, and CastleStealer</title><link>https://feed.craftedsignal.io/briefs/2026-04-clickfix-backgroundfix/</link><pubDate>Thu, 30 Apr 2026 13:00:00 +0000</pubDate><author>hello@craftedsignal.io</author><guid isPermaLink="true">https://feed.craftedsignal.io/briefs/2026-04-clickfix-backgroundfix/</guid><description>The 'BackgroundFix' ClickFix campaign uses social engineering to trick victims into downloading malware disguised as a free image-editing tool, leading to the deployment of CastleLoader, NetSupport RAT for remote access, and CastleStealer for credential theft.</description><content:encoded><![CDATA[<p>The BackgroundFix campaign is a social engineering scheme using fake &quot;remove your photo background&quot; services to deliver malware. Victims are lured to malicious sites mimicking legitimate image editing tools. The sites feature fake upload interfaces, progress bars, and download buttons to appear authentic. This campaign delivers a multi-stage payload, starting with CastleLoader. CastleLoader then drops NetSupport RAT, enabling remote access for the attackers, and CastleStealer, a custom .NET stealer designed to exfiltrate browser credentials, wallet extension data, and Telegram session files. This campaign appears to be active, with multiple domains sharing the same template.</p>
<h2 id="attack-chain">Attack Chain</h2>
<ol>
<li>Victim searches for an online background removal tool and lands on a malicious BackgroundFix site.</li>
<li>The victim uploads an image to the fake website.</li>
<li>After clicking a checkbox, the site instructs the victim to copy a command to their clipboard.</li>
<li>The copied command executes <code>finger.exe</code> to query <code>cheeshomireciple[.]com</code></li>
<li><code>finger.exe</code> retrieves a batch script from the C2 server.</li>
<li>The batch script executes commands to download and execute further payloads.</li>
<li>CastleLoader is deployed, subsequently dropping NetSupport RAT and CastleStealer.</li>
<li>NetSupport RAT grants the attacker remote access, while CastleStealer exfiltrates sensitive data.</li>
</ol>
<h2 id="impact">Impact</h2>
<p>Successful attacks result in the installation of NetSupport RAT, granting attackers remote control over the compromised system. Additionally, CastleStealer exfiltrates sensitive information such as browser credentials, wallet extension data, and Telegram session files. This stolen data can be used for further malicious activities, including financial fraud, identity theft, and unauthorized access to sensitive accounts. The active nature of the campaign and the use of multiple domains suggest a broad targeting scope.</p>
<h2 id="recommendation">Recommendation</h2>
<ul>
<li>Monitor process creation events for the execution of <code>finger.exe</code> with command-line arguments pointing to external domains (IOC: <code>cheeshomireciple[.]com</code>).</li>
<li>Deploy the Sigma rule to detect the execution of <code>finger.exe</code> to identify potential initial access attempts.</li>
<li>Block the C2 domain <code>cheeshomireciple[.]com</code> at the DNS resolver to prevent initial payload delivery.</li>
<li>Monitor network connections for NetSupport RAT C2 communications on port 688 to detect compromised systems (IOCs: <code>poronto[.]com:688</code>, <code>giovettiadv[.]com:688</code>).</li>
</ul>
]]></content:encoded><category domain="severity">high</category><category domain="type">advisory</category><category>clickfix</category><category>malware</category><category>social-engineering</category><category>rat</category><category>infostealer</category><category>castleloader</category><category>netsupport</category></item><item><title>Google Workspace Login Attempt with Government Attack Warning</title><link>https://feed.craftedsignal.io/briefs/2024-01-23-gworkspace-govattack/</link><pubDate>Tue, 28 Apr 2026 00:48:14 +0000</pubDate><author>hello@craftedsignal.io</author><guid isPermaLink="true">https://feed.craftedsignal.io/briefs/2024-01-23-gworkspace-govattack/</guid><description>A Google Workspace login attempt flagged as a potential attack by a government-backed threat actor, indicating potential privilege escalation, defense evasion, persistence, initial access, or impact.</description><content:encoded><![CDATA[<p>This alert focuses on identifying potentially malicious login attempts within Google Workspace environments. The detection is based on Google's own flagging of a login as a potential &quot;gov_attack_warning,&quot; suggesting that Google's threat intelligence attributes the activity to a government-backed actor. While specific targeting information is unavailable, this alert highlights a critical area for investigation within organizations utilizing Google Workspace, especially those handling sensitive data or operating in sectors of interest to nation-state actors. This detection provides an early warning of potential compromise or data exfiltration attempts.</p>
<h2 id="attack-chain">Attack Chain</h2>
<ol>
<li><strong>Initial Access:</strong> An attacker attempts to log into a Google Workspace account using compromised or brute-forced credentials.</li>
<li><strong>Login Attempt:</strong> The login attempt triggers a &quot;gov_attack_warning&quot; within Google Workspace, indicating a potential government-backed threat actor.</li>
<li><strong>Privilege Escalation (Potential):</strong> If the compromised account has elevated privileges, the attacker may attempt to escalate privileges within the Google Workspace environment.</li>
<li><strong>Defense Evasion (Potential):</strong> The attacker may attempt to disable security features or modify audit logs to evade detection.</li>
<li><strong>Persistence (Potential):</strong> The attacker may establish persistent access through methods such as creating rogue apps or modifying account settings.</li>
<li><strong>Data Access:</strong> The attacker gains access to sensitive data stored within Google Workspace, such as documents, emails, and files.</li>
<li><strong>Exfiltration (Potential):</strong> The attacker exfiltrates the stolen data to an external location.</li>
<li><strong>Impact:</strong> The organization suffers a data breach, reputational damage, and potential financial losses.</li>
</ol>
<h2 id="impact">Impact</h2>
<p>A successful attack could lead to the compromise of sensitive data within the Google Workspace environment, including confidential documents, emails, and other business-critical information. The potential consequences range from reputational damage and legal liabilities to financial losses and disruption of business operations. The number of affected users and the severity of the impact will depend on the scope of the attacker's access and the sensitivity of the compromised data.</p>
<h2 id="recommendation">Recommendation</h2>
<ul>
<li>Deploy the provided Sigma rule to your SIEM to detect &quot;gov_attack_warning&quot; events in Google Workspace logs.</li>
<li>Investigate any triggered alerts promptly, focusing on the affected user account and associated activity.</li>
<li>Review the Google Workspace audit logs for any suspicious activity leading up to the &quot;gov_attack_warning&quot; event.</li>
<li>Implement multi-factor authentication (MFA) for all Google Workspace accounts, especially those with elevated privileges.</li>
<li>Monitor Google Workspace activity logs for suspicious patterns, such as unusual login locations, failed login attempts, and changes to account settings.</li>
</ul>
]]></content:encoded><category domain="severity">medium</category><category domain="type">advisory</category><category>googleworkspace</category><category>intrusion</category><category>initial-access</category><category>persistence</category><category>privilege-escalation</category></item><item><title>Google Workspace Object Copied from External Drive Followed by OAuth Consent</title><link>https://feed.craftedsignal.io/briefs/2024-05-09-gworkspace-drive-copy-oauth/</link><pubDate>Thu, 09 May 2024 14:22:00 +0000</pubDate><author>hello@craftedsignal.io</author><guid isPermaLink="true">https://feed.craftedsignal.io/briefs/2024-05-09-gworkspace-drive-copy-oauth/</guid><description>Detects a sequence of events where a user copies a Google Workspace object (spreadsheet, form, document, or script) from an external drive and subsequently grants OAuth permissions to a custom application, potentially indicating a phishing attack leveraging container-bound scripts.</description><content:encoded><![CDATA[<p>This detection identifies a specific attack vector within Google Workspace where a user is tricked into copying a file (such as a Google Sheet, Doc, Form, or Script) from an external Google Drive to their own. This is often achieved through phishing emails containing links with the &quot;copy&quot; parameter. These copied files may contain container-bound scripts. Upon opening the file, the user may be prompted to grant OAuth permissions to a seemingly legitimate application, which in reality is malicious and controlled by the attacker. The attacker leverages the user's granted permissions to access data or perform actions within the Google Workspace environment. This technique can be used to establish persistence, exfiltrate data, or further compromise the organization. This activity has been observed since March 2023.</p>
<h2 id="attack-chain">Attack Chain</h2>
<ol>
<li>The attacker crafts a phishing email containing a link to a Google Drive object (e.g., Spreadsheet, Document) hosted on an external drive. The URL includes the &quot;copy&quot; parameter, tricking the victim into creating a copy of the object in their own Google Drive.</li>
<li>The victim clicks the link and a copy of the Google Drive object is created in the victim's personal or corporate Google Drive. The object could be a script, form, spreadsheet, or document which can have container-bound scripts.</li>
<li>The copied Google Drive object contains a container-bound script, designed to execute malicious code upon opening.</li>
<li>When the user opens the copied object, the container-bound script triggers an OAuth prompt, requesting permissions to access the user's Google Workspace account. The prompt displays a custom application name.</li>
<li>The user, believing the application is legitimate, grants the requested OAuth permissions. These permissions can include access to Gmail, Drive, Contacts, and other Google Workspace services.</li>
<li>The malicious application, now possessing the granted OAuth tokens, gains access to the user's Google Workspace account and data.</li>
<li>The attacker uses the compromised account to perform malicious actions, such as exfiltrating sensitive data, sending further phishing emails, or establishing persistence within the environment.</li>
</ol>
<h2 id="impact">Impact</h2>
<p>A successful attack can result in unauthorized access to sensitive data stored in Google Workspace, including emails, documents, and spreadsheets. The attacker can also use the compromised account to spread malware or phishing attacks to other users within the organization. Depending on the granted OAuth permissions, the attacker may gain full control over the victim's Google Workspace account, leading to significant data loss, financial damage, and reputational harm. There has been no specific victim count or sector information.</p>
<h2 id="recommendation">Recommendation</h2>
<ul>
<li>Deploy the Sigma rule &quot;Google Workspace Drive Object Copy with OAuth Consent&quot; to detect this attack pattern by monitoring Google Workspace logs for the &quot;copy&quot; event followed by OAuth authorization events.</li>
<li>Educate users on the risks of opening files from untrusted sources and granting OAuth permissions to unknown applications.</li>
<li>Review and audit OAuth applications that have been granted access to Google Workspace accounts, focusing on those with broad permissions and custom application IDs, as identified in the rule's description.</li>
<li>Monitor Google Workspace logs for the creation of new container-bound scripts, especially in files originating from external drives.</li>
<li>Reduce the <code>var.interval</code> within the Google Workspace Filebeat module to reduce the event lag time.</li>
</ul>
]]></content:encoded><category domain="severity">medium</category><category domain="type">advisory</category><category>google-workspace</category><category>oauth</category><category>phishing</category><category>initial-access</category><category>persistence</category></item><item><title>Google Workspace Application Removed from Blocklist</title><link>https://feed.craftedsignal.io/briefs/2024-02-gworkspace-blocklist-removal/</link><pubDate>Thu, 29 Feb 2024 10:00:00 +0000</pubDate><author>hello@craftedsignal.io</author><guid isPermaLink="true">https://feed.craftedsignal.io/briefs/2024-02-gworkspace-blocklist-removal/</guid><description>An adversary with Google Workspace administrative privileges may remove an application from the explicit blocklist to enable its distribution and usage, potentially indicating unauthorized activity and defense evasion.</description><content:encoded><![CDATA[<p>Google Workspace administrators use blocklists to prevent users from installing or using potentially malicious applications from the Google Workspace Marketplace. An attacker who has gained administrative privileges within a Google Workspace environment can remove applications from this blocklist, effectively allowing the applications to be installed and used by unsuspecting users. This activity can be indicative of an attacker attempting to distribute malware or gain unauthorized access to sensitive data. The observed activity revolves around the modification of application settings within Google Workspace, specifically related to the &quot;allowed&quot; status of applications. The impact of this activity can range from data breaches to compromised user accounts. Defenders need to monitor for unauthorized changes to application blocklists and investigate any unexpected modifications.</p>
<h2 id="attack-chain">Attack Chain</h2>
<ol>
<li>Attacker gains unauthorized administrative privileges within the Google Workspace environment.</li>
<li>Attacker navigates to the Google Workspace admin console.</li>
<li>Attacker accesses the application settings for Google Workspace Marketplace.</li>
<li>Attacker identifies a previously blocked application within the blocklist.</li>
<li>Attacker modifies the application settings, changing the &quot;allowed&quot; status from &quot;false&quot; to &quot;true.&quot;</li>
<li>The change is saved, and the application is effectively removed from the blocklist.</li>
<li>Users within the Google Workspace environment are now able to install and use the previously blocked application.</li>
<li>The malicious application is distributed and used to perform malicious actions like exfiltration or lateral movement.</li>
</ol>
<h2 id="impact">Impact</h2>
<p>The removal of an application from the Google Workspace blocklist can have significant consequences. Users may install and use malicious applications, leading to data breaches, compromised accounts, and the introduction of malware into the environment. The specific impact depends on the permissions and capabilities of the malicious application. Affected sectors are broad, as Google Workspace is used across various industries. Successful attacks can lead to financial loss, reputational damage, and legal ramifications.</p>
<h2 id="recommendation">Recommendation</h2>
<ul>
<li>Implement the Sigma rule &quot;Google Workspace Application Blocklist Removed&quot; to detect when an application is removed from the blocklist by monitoring Google Workspace admin logs (logsource: google_workspace.admin).</li>
<li>Investigate any alerts generated by the Sigma rule, focusing on identifying the user account that made the change and the application that was unblocked.</li>
<li>Regularly review Google Workspace administrative accounts to ensure the principle of least privilege is enforced.</li>
<li>Monitor the Google Workspace admin logs for unusual account activity, such as changes to roles or permissions.</li>
<li>Reference Google's security best practices and implement them in your Google Workspace environment to increase overall security.</li>
<li>Tune the &quot;Google Workspace Application Blocklist Removed&quot; Sigma rule for your environment to filter out expected behavior by legitimate administrators.</li>
</ul>
]]></content:encoded><category domain="severity">medium</category><category domain="type">advisory</category><category>google_workspace</category><category>defense_evasion</category><category>cloud</category></item><item><title>Google Workspace Suspicious Login Activity</title><link>https://feed.craftedsignal.io/briefs/2024-01-26-gworkspace-suspicious-login/</link><pubDate>Fri, 26 Jan 2024 10:00:00 +0000</pubDate><author>hello@craftedsignal.io</author><guid isPermaLink="true">https://feed.craftedsignal.io/briefs/2024-01-26-gworkspace-suspicious-login/</guid><description>Detect Google Workspace login activity that Google has classified as suspicious, potentially indicating initial access, privilege escalation, defense evasion, or persistence attempts.</description><content:encoded><![CDATA[<p>This brief focuses on detecting suspicious login activity within Google Workspace environments, as flagged by Google's internal risk assessment mechanisms. Google Workspace logs login events and classifies them based on various risk factors, including the use of less secure applications, programmatic logins, and other anomalies. This detection capability is crucial for identifying potential compromises, unauthorized access attempts, and malicious activities within the Google Workspace ecosystem. Analyzing these flagged events allows security teams to proactively respond to threats before they escalate, preventing data breaches and maintaining the integrity of sensitive information. This alert focuses on logins classified as 'suspicious_login_less_secure_app', 'suspicious_login', and 'suspicious_programmatic_login'.</p>
<h2 id="attack-chain">Attack Chain</h2>
<ol>
<li><strong>Initial Access:</strong> An attacker gains initial access using compromised credentials or brute-force techniques targeting Google Workspace accounts.</li>
<li><strong>Login Attempt:</strong> The attacker attempts to log in to a Google Workspace account using a less secure application (e.g., an older email client without modern authentication) or via programmatic login.</li>
<li><strong>Suspicious Activity Detection:</strong> Google's internal systems analyze the login attempt and flag it as suspicious based on various risk factors, such as unusual location, time of day, or login method.</li>
<li><strong>Event Logging:</strong> Google Workspace logs the suspicious login event, including the reason for the classification (e.g., 'suspicious_login_less_secure_app').</li>
<li><strong>Potential Privilege Escalation:</strong> Upon successful login, the attacker may attempt to escalate privileges within the Google Workspace environment to gain broader access.</li>
<li><strong>Defense Evasion:</strong> The attacker might use techniques to evade detection, such as disabling security features or modifying audit logs.</li>
<li><strong>Persistence:</strong> The attacker establishes persistence by creating new accounts, modifying existing ones, or installing malicious apps.</li>
<li><strong>Data Exfiltration/Malicious Activity:</strong> The attacker uses the compromised account to exfiltrate sensitive data or perform other malicious activities, such as sending phishing emails.</li>
</ol>
<h2 id="impact">Impact</h2>
<p>Successful exploitation can lead to unauthorized access to sensitive data stored within Google Workspace, including emails, documents, and other files. This can result in data breaches, financial loss, and reputational damage. The number of affected users depends on the scope of the compromised account and the attacker's ability to escalate privileges. Targeted sectors are broad, affecting any organization relying on Google Workspace for collaboration and data storage.</p>
<h2 id="recommendation">Recommendation</h2>
<ul>
<li>Deploy the provided Sigma rule to your SIEM to detect suspicious login activity classified by Google Workspace (logsource: <code>gcp</code>, service: <code>google_workspace.login</code>).</li>
<li>Investigate any alerts generated by the Sigma rule to determine the legitimacy of the login attempt and take appropriate action, such as resetting passwords or disabling compromised accounts.</li>
<li>Enforce multi-factor authentication (MFA) for all Google Workspace accounts to mitigate the risk of credential compromise.</li>
<li>Disable or restrict the use of less secure apps within Google Workspace to reduce the attack surface.</li>
<li>Monitor Google Workspace audit logs for other suspicious activities, such as unusual file access or data exfiltration attempts.</li>
</ul>
]]></content:encoded><category domain="severity">medium</category><category domain="type">advisory</category><category>initial-access</category><category>privilege-escalation</category><category>defense-evasion</category><category>persistence</category><category>gworkspace</category></item><item><title>Google Workspace BitLocker Setting Disabled</title><link>https://feed.craftedsignal.io/briefs/2024-01-gworkspace-bitlocker-disable/</link><pubDate>Tue, 09 Jan 2024 12:00:00 +0000</pubDate><author>hello@craftedsignal.io</author><guid isPermaLink="true">https://feed.craftedsignal.io/briefs/2024-01-gworkspace-bitlocker-disable/</guid><description>Detection of Google Workspace administrators disabling the BitLocker setting, potentially allowing adversaries with valid account access to decrypt sensitive data on managed Windows devices.</description><content:encoded><![CDATA[<p>This threat brief focuses on the detection of unauthorized BitLocker disabling within Google Workspace environments. Google Workspace administrators with Windows device management enabled have the ability to manage BitLocker drive encryption on registered Windows endpoints. An adversary who has gained valid account access to a Google Workspace administrator account may attempt to disable BitLocker on managed Windows devices. This action decrypts data at rest and makes it accessible, increasing the risk of sensitive data exposure. This activity is typically logged as a &quot;CHANGE_APPLICATION_SETTING&quot; event within the Google Workspace admin audit logs. Defenders should monitor for unexpected or unauthorized changes to BitLocker settings. The reported Google Workspace event lag times ranging from minutes up to 3 days between the time of an event's occurrence should be considered.</p>
<h2 id="attack-chain">Attack Chain</h2>
<ol>
<li>The adversary gains valid credentials for a Google Workspace administrator account.</li>
<li>The adversary authenticates to the Google Workspace admin console.</li>
<li>The adversary navigates to the device management section of the console.</li>
<li>The adversary identifies a target Windows device that is managed through Google Workspace and has BitLocker enabled.</li>
<li>The adversary modifies the BitLocker setting for the target device, setting the new value to &quot;Disabled&quot;.</li>
<li>This action triggers a &quot;CHANGE_APPLICATION_SETTING&quot; event within the Google Workspace admin audit logs, specifically targeting the BitLocker setting.</li>
<li>The endpoint decrypts the data, allowing unauthorized access.</li>
</ol>
<h2 id="impact">Impact</h2>
<p>The successful disabling of BitLocker can lead to the unauthorized access of sensitive data stored on Windows endpoints managed by Google Workspace. This can result in data breaches, compliance violations, and reputational damage. The severity of the impact depends on the type and amount of data stored on the affected devices. If BitLocker is disabled on a large number of devices, the impact can be widespread and significant.</p>
<h2 id="recommendation">Recommendation</h2>
<ul>
<li>Deploy the Sigma rule &quot;Google Workspace Bitlocker Setting Disabled&quot; to detect unauthorized BitLocker disabling events in your Google Workspace environment.</li>
<li>Review the permissions assigned to Google Workspace users to adhere to the principle of least privilege.</li>
<li>Reduce the <code>var.interval</code> setting of the Google Workspace Filebeat module to minimize event lag and improve detection timeliness (reference: <a href="https://www.elastic.co/guide/en/beats/filebeat/current/filebeat-module-google_workspace.html">https://www.elastic.co/guide/en/beats/filebeat/current/filebeat-module-google_workspace.html</a>).</li>
<li>Investigate any alerts generated by the Sigma rule by checking the Google Workspace admin console audit logs for related events involving the affected user (Reporting &gt; Audit and Investigation &gt; Device logs).</li>
</ul>
]]></content:encoded><category domain="severity">medium</category><category domain="type">advisory</category><category>google_workspace</category><category>bitlocker</category><category>defense_evasion</category></item><item><title>GCP Account Compromise via Single-Factor Authentication</title><link>https://feed.craftedsignal.io/briefs/2024-01-09-gcp-single-factor-auth/</link><pubDate>Tue, 09 Jan 2024 12:00:00 +0000</pubDate><author>hello@craftedsignal.io</author><guid isPermaLink="true">https://feed.craftedsignal.io/briefs/2024-01-09-gcp-single-factor-auth/</guid><description>Detection of successful single-factor authentication against Google Cloud Platform (GCP) for an account without Multi-Factor Authentication (MFA) enabled, potentially leading to account compromise and unauthorized access to GCP resources.</description><content:encoded><![CDATA[<p>This analytic detects successful single-factor authentication attempts against Google Cloud Platform (GCP) accounts where multi-factor authentication (MFA) is not enabled. This detection is based on Google Workspace login event data and identifies instances where MFA is not utilized during account login. The lack of MFA can stem from misconfigurations, policy violations, or successful credential compromise. The successful exploitation of this gap by an attacker can provide initial access to GCP resources, potentially leading to data breaches, service disruptions, or further lateral movement within the cloud environment. This activity should be investigated promptly to ensure appropriate security policies are enforced and potentially compromised accounts are remediated.</p>
<h2 id="attack-chain">Attack Chain</h2>
<ol>
<li><strong>Credential Compromise:</strong> An attacker obtains valid credentials through phishing, credential stuffing, or purchasing leaked credentials.</li>
<li><strong>Initial Access:</strong> The attacker uses the compromised credentials to attempt login to a Google Workspace account associated with a GCP tenant.</li>
<li><strong>Single-Factor Authentication:</strong> The attacker successfully authenticates using only a username and password because MFA is not enabled or enforced for the target account.</li>
<li><strong>GCP Access:</strong> Upon successful authentication, the attacker gains access to the Google Cloud Platform (GCP) resources associated with the compromised account.</li>
<li><strong>Privilege Escalation (Optional):</strong> Depending on the compromised account's permissions, the attacker may attempt to escalate privileges within the GCP environment.</li>
<li><strong>Lateral Movement (Optional):</strong> The attacker uses the initial access to move laterally within the GCP environment, accessing other resources and accounts.</li>
<li><strong>Data Exfiltration / Service Disruption:</strong> The attacker exfiltrates sensitive data from GCP storage or disrupts critical services within the GCP environment.</li>
<li><strong>Persistence (Optional):</strong> The attacker establishes persistence mechanisms to maintain access to the GCP environment, such as creating new accounts or modifying existing roles.</li>
</ol>
<h2 id="impact">Impact</h2>
<p>Successful exploitation of single-factor authentication vulnerabilities can result in significant damage, including data breaches, service disruptions, and financial losses. The impact can range from a few affected accounts to complete compromise of a GCP environment depending on access levels. The Forbes article referenced indicates billions of stolen logins are available, meaning credential compromise is a likely initial vector. Organizations in all sectors are at risk, particularly those with lax MFA enforcement policies.</p>
<h2 id="recommendation">Recommendation</h2>
<ul>
<li>Deploy the Sigma rule <code>GCP Successful Single-Factor Authentication</code> to your SIEM and tune for your environment to detect logins without MFA based on Google Workspace logs.</li>
<li>Investigate any alerts generated by the <code>GCP Successful Single-Factor Authentication</code> rule, prioritizing accounts with elevated privileges or access to sensitive data.</li>
<li>Enforce multi-factor authentication (MFA) for all Google Workspace accounts, especially those with access to GCP resources, as per Google's recommendations in the references.</li>
<li>Regularly audit Google Workspace and GCP configurations to ensure that MFA policies are properly configured and enforced.</li>
<li>Use the drilldown searches included in this brief to investigate users triggering the initial detection.</li>
</ul>
]]></content:encoded><category domain="severity">high</category><category domain="type">advisory</category><category>gcp</category><category>cloud</category><category>authentication</category><category>account-takeover</category></item><item><title>Google Drive Ownership Transferred via Google Workspace</title><link>https://feed.craftedsignal.io/briefs/2024-01-05-google-drive-ownership-transfer/</link><pubDate>Fri, 05 Jan 2024 18:23:00 +0000</pubDate><author>hello@craftedsignal.io</author><guid isPermaLink="true">https://feed.craftedsignal.io/briefs/2024-01-05-google-drive-ownership-transfer/</guid><description>Adversaries may transfer files to an adversary account for potential exfiltration by abusing Google Workspace administration permissions to transfer file ownership within Google Drive.</description><content:encoded><![CDATA[<p>Google Drive and Docs is a Google Workspace service that allows users to leverage Google Drive and Google Docs. Access to files is based on inherited permissions from the child organizational unit the user belongs to which is scoped by administrators. If a user is removed, their files can be transferred to another user by the administrator. This service can be abused by adversaries to transfer files to an adversary account for potential exfiltration. Google Workspace administrators consider users' roles and organizational units when assigning permissions to files or shared drives. This rule identifies when the ownership of a shared drive within a Google Workspace organization is transferred to another internal user.</p>
<h2 id="attack-chain">Attack Chain</h2>
<ol>
<li>An adversary gains initial access to a compromised Google Workspace account or obtains administrative privileges.</li>
<li>The adversary identifies a target user or shared drive containing sensitive data within the Google Workspace environment.</li>
<li>The adversary initiates a data transfer request within Google Workspace, targeting an account under their control. This is achieved by creating a &quot;CREATE_DATA_TRANSFER_REQUEST&quot; event for the Drive application.</li>
<li>The Google Workspace administrator reviews and approves the data transfer request (or the adversary leverages compromised admin credentials to approve the request).</li>
<li>Google Workspace initiates the transfer of files and folders from the original owner to the adversary-controlled account.</li>
<li>Data is staged in the adversary's account.</li>
<li>The adversary exfiltrates the transferred data from their Google Drive account to an external location.</li>
<li>The adversary covers their tracks by deleting logs or modifying permissions (actions not explicitly detailed in source).</li>
</ol>
<h2 id="impact">Impact</h2>
<p>A successful Google Drive ownership transfer can lead to the exfiltration of sensitive data, including confidential documents, financial records, and proprietary information. This could result in financial loss, reputational damage, and legal liabilities. While the specific number of victims and sectors targeted is not mentioned in the provided context, any organization using Google Workspace is potentially vulnerable.</p>
<h2 id="recommendation">Recommendation</h2>
<ul>
<li>Deploy the Sigma rule <code>Detect Google Workspace Drive Ownership Transfer</code> to your SIEM to detect unauthorized data transfer requests based on <code>event.action:&quot;CREATE_DATA_TRANSFER_REQUEST&quot;</code> and <code>google_workspace.admin.application.name:Drive*</code>.</li>
<li>Review Google Workspace admin logs for involved user accounts as mentioned in the investigation guide to identify potentially compromised accounts.</li>
<li>Enforce the principle of least privilege by regularly reviewing and restricting Google Drive permissions for users and shared drives, following Google's security best practices outlined <a href="https://support.google.com/a/answer/7587183">here</a>.</li>
<li>Reduce the <code>var.interval</code> of the Google Workspace Filebeat module to 10 minutes (10m) to minimize the risk of missing data transfer events due to Google Workspace event lag times.</li>
</ul>
]]></content:encoded><category domain="severity">medium</category><category domain="type">advisory</category><category>google-workspace</category><category>data-exfiltration</category><category>cloud</category></item><item><title>External User Added to Google Workspace Group</title><link>https://feed.craftedsignal.io/briefs/2024-01-gworkspace-external-user-group/</link><pubDate>Wed, 03 Jan 2024 18:23:00 +0000</pubDate><author>hello@craftedsignal.io</author><guid isPermaLink="true">https://feed.craftedsignal.io/briefs/2024-01-gworkspace-external-user-group/</guid><description>Detection of an external Google Workspace user account being added to an existing group, potentially indicating an adversary attempting to intercept shared files or emails by adding accounts where the domain name of the target doesn't match the Google Workspace domain.</description><content:encoded><![CDATA[<p>This detection identifies instances where an external user account is added to a Google Workspace group. Attackers may leverage this technique to intercept shared files or emails directed to the group. The rule focuses on identifying user accounts where the domain name of the target does not match the Google Workspace domain. The attack often starts with phishing or exploiting container-bound scripts to add external Google accounts to an organization's groups, sometimes granting editorial privileges. This allows the attacker to receive any information shared with the group, leading to potential data leaks or weaponization of documents for further intrusion. Google Workspace administrators may observe lag times ranging from minutes up to 3 days between the time of an event's occurrence and the event being visible in the Google Workspace admin/audit logs.</p>
<h2 id="attack-chain">Attack Chain</h2>
<ol>
<li>The attacker performs reconnaissance to identify a target Google Workspace organization and its group structure.</li>
<li>A phishing email is crafted to steal credentials of a user with group management privileges or to directly add an external user to a group via a malicious link.</li>
<li>Alternatively, the attacker compromises a container-bound script with sufficient privileges to modify group memberships.</li>
<li>The compromised user or script adds an external user account (e.g., a Gmail account controlled by the attacker) to a target Google Workspace group.</li>
<li>The external user account receives emails and shared files intended for the group, potentially containing sensitive information.</li>
<li>The attacker monitors the intercepted communications for valuable data, such as credentials, financial information, or proprietary documents.</li>
<li>The stolen information is exfiltrated to an external location.</li>
<li>The attacker uses the stolen information to further compromise the organization or its partners.</li>
</ol>
<h2 id="impact">Impact</h2>
<p>Compromising Google Workspace groups can lead to significant data breaches, with potentially thousands of internal documents and communications exposed to unauthorized external actors. Successful attacks can result in the loss of confidential business data, intellectual property theft, and regulatory compliance violations. The targeted groups could range from small teams to company-wide distribution lists, affecting customer data, financial records, and strategic plans. Depending on the group's function, the impact could range from minor data leakage to severe reputational and financial damage, depending on the sensitivity and volume of data accessed.</p>
<h2 id="recommendation">Recommendation</h2>
<ul>
<li>Deploy the Sigma rule &quot;External User Added to Google Workspace Group&quot; to your SIEM to detect suspicious group membership changes.</li>
<li>Investigate alerts generated by the Sigma rule by examining the <code>user.name</code> or <code>user.email</code> and the <code>group.name</code> fields to identify involved accounts and groups.</li>
<li>Review Google Workspace audit logs for <code>event.action: &quot;ADD_GROUP_MEMBER&quot;</code> to identify other group modifications and potential external user additions.</li>
<li>Implement multi-factor authentication (MFA) for all Google Workspace accounts, particularly those with administrative privileges, to mitigate credential theft.</li>
<li>Enforce strict access control policies and regularly review group memberships to ensure only authorized users have access to sensitive data.</li>
<li>Configure alerts for unusual activity, such as external account additions to internal groups, to reduce the mean time to detect (MTTD).</li>
</ul>
]]></content:encoded><category domain="severity">medium</category><category domain="type">advisory</category><category>google_workspace</category><category>initial_access</category><category>account_manipulation</category></item><item><title>GSuite Suspicious File Share with Phishing Filenames</title><link>https://feed.craftedsignal.io/briefs/2024-01-03-gsuite-suspicious-file-share/</link><pubDate>Wed, 03 Jan 2024 12:00:00 +0000</pubDate><author>hello@craftedsignal.io</author><guid isPermaLink="true">https://feed.craftedsignal.io/briefs/2024-01-03-gsuite-suspicious-file-share/</guid><description>This analytic detects suspicious file sharing activity in Google Workspace where files are shared with names commonly associated with phishing campaigns, such as 'invoice,' 'shipment,' or 'delivery', potentially leading to credential theft or malware infection.</description><content:encoded><![CDATA[<p>This brief focuses on detecting spear phishing attempts within Google Workspace environments through the identification of suspicious filenames associated with shared files. The detection leverages GSuite Drive logs to identify documents with titles that include keywords such as &quot;dhl,&quot; &quot;ups,&quot; &quot;invoice,&quot; and &quot;shipment&quot;. These filenames are commonly used in phishing campaigns to trick users into opening malicious documents or clicking harmful links. The successful exploitation of this technique can lead to unauthorized access to sensitive information, data theft, or further compromise of the user's system. This analytic helps defenders identify and respond to potential phishing attacks targeting their organization via Google Drive.</p>
<h2 id="attack-chain">Attack Chain</h2>
<ol>
<li>Attacker crafts a document with a malicious payload or link and names it with a phishing-related term (e.g., &quot;invoice,&quot; &quot;shipment&quot;).</li>
<li>The attacker shares the malicious file via Google Drive with a target user within the organization. The file is intentionally named to entice the recipient.</li>
<li>The target user receives a notification or email about the shared file in Google Drive.</li>
<li>The user, believing the file is legitimate, opens the shared document in Google Drive.</li>
<li>If the document contains a malicious link, the user clicks on it, redirecting them to a phishing website.</li>
<li>The phishing website prompts the user to enter their credentials, which are then captured by the attacker.</li>
<li>Alternatively, if the document contains a malicious script, it executes upon opening, potentially installing malware on the user's system.</li>
<li>The attacker gains unauthorized access to the user's account or system, enabling data theft, lateral movement, or further malicious activities.</li>
</ol>
<h2 id="impact">Impact</h2>
<p>A successful phishing attack via Google Drive can compromise user accounts, leading to unauthorized access to sensitive data and potential data breaches. The impact can range from individual account compromise to widespread organizational damage, including financial losses, reputational damage, and legal liabilities. Organizations can experience a significant disruption of services, especially if critical accounts are compromised. The number of potential victims depends on the scale of the phishing campaign and the attacker's targets within the organization.</p>
<h2 id="recommendation">Recommendation</h2>
<ul>
<li>Deploy the <code>GSuite Suspicious Shared File Name</code> Sigma rule to your SIEM to identify potentially malicious file sharing activity in Google Drive (rules).</li>
<li>Configure your GSuite environment to log Drive events, specifically file sharing activities, to enable the Sigma rule to function correctly (data_source).</li>
<li>Educate users about the risks of opening shared files with suspicious filenames and clicking on links from unknown sources (references).</li>
<li>Review and customize the keyword list in the Sigma rule to align with your organization's specific threat landscape and common phishing themes (search).</li>
<li>Investigate any alerts generated by the Sigma rule, prioritizing those involving sensitive data or high-value targets (summary).</li>
<li>Implement multi-factor authentication (MFA) to mitigate the impact of compromised credentials obtained through phishing attacks (summary).</li>
</ul>
]]></content:encoded><category domain="severity">medium</category><category domain="type">advisory</category><category>phishing</category><category>gsuite</category><category>google_workspace</category></item><item><title>Google Workspace Suspended User Account Renewed</title><link>https://feed.craftedsignal.io/briefs/2024-01-google-workspace-suspended-user-renewed/</link><pubDate>Wed, 03 Jan 2024 12:00:00 +0000</pubDate><author>hello@craftedsignal.io</author><guid isPermaLink="true">https://feed.craftedsignal.io/briefs/2024-01-google-workspace-suspended-user-renewed/</guid><description>Detection of a renewed, previously suspended user account in Google Workspace, potentially indicating unauthorized access or persistence by an adversary.</description><content:encoded><![CDATA[<p>This alert identifies instances where a user account, previously suspended within a Google Workspace environment, is reactivated. While legitimate administrative actions can trigger this event, adversaries may exploit the account renewal process to regain unauthorized access to the Google Workspace organization. This technique allows them to bypass typical access controls and maintain a valid account for malicious activities. The rule focuses on detecting the <code>UNSUSPEND_USER</code> event within Google Workspace admin/audit logs. Google Workspace event logs may have lag times ranging from minutes up to 3 days, defenders should adjust polling intervals to mitigate false negatives.</p>
<h2 id="attack-chain">Attack Chain</h2>
<ol>
<li>An attacker gains initial access to a privileged Google Workspace account, potentially through compromised credentials or social engineering.</li>
<li>The attacker identifies a suspended user account within the Google Workspace environment.</li>
<li>The attacker renews the suspended user account using the compromised privileged account, triggering the <code>UNSUSPEND_USER</code> event.</li>
<li>The renewed account is now active within the Google Workspace environment, allowing the attacker to bypass initial access controls.</li>
<li>The attacker leverages the renewed user account to access sensitive data and resources within Google Workspace.</li>
<li>The attacker may attempt to escalate privileges further from the renewed account.</li>
<li>The attacker maintains persistence by using the renewed account as a long-term backdoor into the organization's Google Workspace environment.</li>
</ol>
<h2 id="impact">Impact</h2>
<p>A successful account renewal by an attacker can lead to unauthorized access to sensitive data, business disruption, and potential data exfiltration within the Google Workspace environment. The impact can range from minor data breaches to significant operational compromises depending on the permissions and data access of the renewed user account. It's a low severity but important signal that may indicate malicious activity.</p>
<h2 id="recommendation">Recommendation</h2>
<ul>
<li>Deploy the Sigma rule provided in this brief to your SIEM and tune it for your specific Google Workspace environment.</li>
<li>Review the event logs associated with the <code>UNSUSPEND_USER</code> action, focusing on the administrator or service account that performed the action, as mentioned in the investigation guide.</li>
<li>Implement additional monitoring and alerting on reactivated user accounts to detect any suspicious activity following the account's renewal.</li>
<li>Adjust the Google Workspace Filebeat module polling interval to a lower value (e.g., 10 minutes) to reduce the risk of false negatives due to event lag times, as described in the Setup section.</li>
<li>Review and update security policies related to account suspension and reactivation to prevent similar incidents in the future.</li>
</ul>
]]></content:encoded><category domain="severity">low</category><category domain="type">advisory</category><category>google_workspace</category><category>initial_access</category><category>persistence</category></item><item><title>GCP Authentication Failure During MFA Challenge</title><link>https://feed.craftedsignal.io/briefs/2024-01-gcp-failed-mfa/</link><pubDate>Wed, 03 Jan 2024 12:00:00 +0000</pubDate><author>hello@craftedsignal.io</author><guid isPermaLink="true">https://feed.craftedsignal.io/briefs/2024-01-gcp-failed-mfa/</guid><description>Detection of failed MFA challenges in Google Cloud Platform (GCP) using Google Workspace login failure events, potentially indicating credential compromise and unauthorized access attempts.</description><content:encoded><![CDATA[<p>This analytic identifies failed authentication attempts during Multi-Factor Authentication (MFA) challenges within a Google Cloud Platform (GCP) environment. It leverages Google Workspace login failure events to detect instances where MFA methods were challenged but not successfully completed. The detection is based on Google Workspace login failure events where MFA methods were challenged. This activity could signify an adversary attempting to gain unauthorized access to an account using compromised credentials, even with MFA enabled. Successful exploitation could lead to data breaches, resource hijacking, or other malicious activities within the targeted GCP environment. The Splunk Add-on for Google Workspace (app ID 5556) is required for data ingestion.</p>
<h2 id="attack-chain">Attack Chain</h2>
<ol>
<li>The attacker obtains valid or partially valid credentials through phishing (T1566), credential stuffing, or purchasing them from the dark web.</li>
<li>The attacker attempts to log in to a GCP account using the obtained credentials (T1078.004).</li>
<li>GCP's login process identifies the need for MFA and issues a login challenge using a configured method.</li>
<li>The attacker fails to complete the MFA challenge, indicating they do not possess the correct MFA token or cannot respond correctly (T1621).</li>
<li>Multiple failed MFA attempts may occur from the same IP address or user account.</li>
<li>If the attacker eventually succeeds in bypassing MFA (e.g., through a vulnerability or social engineering), they gain unauthorized access to the GCP environment.</li>
<li>Once inside, the attacker can perform reconnaissance, escalate privileges, and access sensitive data.</li>
<li>The attacker exfiltrates data or deploys malicious resources within the GCP environment, causing damage or disruption.</li>
</ol>
<h2 id="impact">Impact</h2>
<p>A successful attack can lead to unauthorized access to sensitive data and resources within the GCP environment. This could result in data breaches, financial loss, reputational damage, and disruption of services. The severity depends on the compromised account's permissions and the attacker's objectives within the GCP environment.</p>
<h2 id="recommendation">Recommendation</h2>
<ul>
<li>Deploy the Sigma rule <code>GCP Authentication Failed During MFA Challenge</code> to your SIEM and tune the threshold based on your environment's baseline for failed MFA attempts.</li>
<li>Investigate any alerts generated by the <code>GCP Authentication Failed During MFA Challenge</code> rule to determine if the failed MFA attempts are legitimate or indicative of malicious activity.</li>
<li>Monitor login events for unusual patterns, such as multiple failed MFA attempts from the same IP address or user account.</li>
<li>Ensure all users have strong, unique passwords and are enrolled in MFA.</li>
<li>Review and enforce Conditional Access policies to restrict access based on location, device, and other factors.</li>
<li>Install the latest version of Splunk Add-on for Google Workspace from Splunkbase (<a href="https://splunkbase.splunk.com/app/5556">https://splunkbase.splunk.com/app/5556</a>) to collect the required Google Workspace login events.</li>
</ul>
]]></content:encoded><category domain="severity">medium</category><category domain="type">advisory</category><category>gcp</category><category>cloud</category><category>mfa</category><category>credential-access</category></item><item><title>Detection of Out-of-Domain Email Forwarding in Google Workspace</title><link>https://feed.craftedsignal.io/briefs/2024-01-gworkspace-email-forwarding/</link><pubDate>Wed, 03 Jan 2024 12:00:00 +0000</pubDate><author>hello@craftedsignal.io</author><guid isPermaLink="true">https://feed.craftedsignal.io/briefs/2024-01-gworkspace-email-forwarding/</guid><description>Detects automatic email forwarding to external domains in Google Workspace, which may indicate data leakage or misuse by malicious insiders or compromised accounts.</description><content:encoded><![CDATA[<p>This brief focuses on detecting unauthorized email forwarding to external domains within Google Workspace environments. The primary concern is the potential for data exfiltration or misuse by malicious insiders or threat actors who have compromised user accounts. The activity is logged by Google Workspace and can be monitored using the Google Workspace Admin Reports API. The event name associated with this activity is <code>email_forwarding_out_of_domain</code>, which is generated when a user configures automatic email forwarding to an address outside the organization's domain. Successful exploitation of this technique can lead to the leakage of sensitive information, intellectual property theft, or compliance violations.</p>
<h2 id="attack-chain">Attack Chain</h2>
<ol>
<li>An attacker gains unauthorized access to a Google Workspace user account, potentially through phishing, credential stuffing, or other methods.</li>
<li>The attacker navigates to the Gmail settings for the compromised account.</li>
<li>The attacker configures automatic email forwarding to an external email address controlled by the attacker (e.g., a Gmail, Outlook, or ProtonMail address).</li>
<li>The attacker sets up filters to forward specific types of emails, such as those containing sensitive keywords or originating from key personnel.</li>
<li>Legitimate emails are received by the compromised user and automatically forwarded to the external address.</li>
<li>The attacker collects the forwarded emails, extracting sensitive data or using it for further malicious activities.</li>
<li>The attacker covers their tracks by deleting audit logs or modifying forwarding rules.</li>
</ol>
<h2 id="impact">Impact</h2>
<p>Successful exploitation of unauthorized email forwarding can lead to significant data breaches, intellectual property theft, and compliance violations. The impact can range from exposure of sensitive customer data to the loss of competitive advantage due to stolen trade secrets. Depending on the volume and nature of the data exfiltrated, organizations may face legal and regulatory penalties, as well as reputational damage.</p>
<h2 id="recommendation">Recommendation</h2>
<ul>
<li>Deploy the provided Sigma rule to your SIEM to detect <code>email_forwarding_out_of_domain</code> events in Google Workspace logs (logsource: <code>gcp</code>, service: <code>google_workspace.login</code>).</li>
<li>Investigate any alerts generated by the Sigma rule to determine the legitimacy of the email forwarding configuration.</li>
<li>Implement multi-factor authentication (MFA) for all Google Workspace accounts to reduce the risk of account compromise.</li>
<li>Regularly review and audit email forwarding rules to identify and remove any unauthorized configurations.</li>
<li>Train users to recognize and report phishing attempts to prevent account compromise.</li>
</ul>
]]></content:encoded><category domain="severity">medium</category><category domain="type">advisory</category><category>data-leakage</category><category>gworkspace</category><category>email-forwarding</category></item><item><title>Google Workspace MFA Enforcement Disabled</title><link>https://feed.craftedsignal.io/briefs/2024-01-google-workspace-mfa-disabled/</link><pubDate>Tue, 02 Jan 2024 12:00:00 +0000</pubDate><author>hello@craftedsignal.io</author><guid isPermaLink="true">https://feed.craftedsignal.io/briefs/2024-01-google-workspace-mfa-disabled/</guid><description>Detection of multi-factor authentication (MFA) enforcement being disabled for Google Workspace users, potentially weakening security controls and leading to account compromise.</description><content:encoded><![CDATA[<p>The disabling of multi-factor authentication (MFA) enforcement in Google Workspace can severely weaken an organization's security posture. Attackers may target MFA settings to gain unauthorized access to user accounts and sensitive data. This activity, often performed by compromised administrative accounts, allows attackers to bypass an important control mechanism designed to protect user identities. Google Workspace administrators should closely monitor changes to MFA enforcement policies, as these changes can expose the organization to significant risk. The default Filebeat module polls Google's reporting API every 2 hours, but the Google documentation states there can be lag times ranging from minutes up to 3 days between an event occurrence and its visibility in the admin/audit logs. Reducing this interval can help reduce false negatives.</p>
<h2 id="attack-chain">Attack Chain</h2>
<ol>
<li>An attacker compromises a Google Workspace administrator account, potentially through phishing or credential stuffing.</li>
<li>The attacker authenticates to the Google Workspace admin console using the compromised credentials.</li>
<li>The attacker navigates to the MFA settings within the Google Workspace admin console.</li>
<li>The attacker modifies the MFA enforcement policy, disabling MFA for specific users or the entire organization.</li>
<li>The attacker attempts to log in to target user accounts without being prompted for a second factor.</li>
<li>The attacker gains access to sensitive data and resources within Google Workspace, such as email, documents, and applications.</li>
<li>The attacker may move laterally to other systems or cloud services using the compromised user accounts.</li>
</ol>
<h2 id="impact">Impact</h2>
<p>Disabling MFA enforcement exposes Google Workspace accounts to unauthorized access, potentially impacting all users within the organization. This can lead to data breaches, financial losses, and reputational damage. Depending on the compromised accounts, attackers can access and exfiltrate sensitive information, disrupt business operations, and launch further attacks against the organization and its customers.</p>
<h2 id="recommendation">Recommendation</h2>
<ul>
<li>Deploy the Sigma rule <code>Google Workspace MFA Enforcement Disabled</code> to your SIEM to detect when MFA enforcement is disabled.</li>
<li>Enable Google Workspace Fleet integration, Filebeat module, or similar data ingestion pipeline to collect the necessary logs for the Sigma rule.</li>
<li>Investigate any detected instances of MFA being disabled, as this could indicate a compromised administrator account.</li>
<li>Review the permissions assigned to the implicated user to ensure that the least privilege principle is being followed.</li>
<li>Implement security best practices outlined by Google.</li>
</ul>
]]></content:encoded><category domain="severity">medium</category><category domain="type">advisory</category><category>google-workspace</category><category>mfa</category><category>account-compromise</category></item><item><title>Google Workspace 2SV Policy Disabled</title><link>https://feed.craftedsignal.io/briefs/2024-01-google-workspace-2sv-disabled/</link><pubDate>Tue, 02 Jan 2024 12:00:00 +0000</pubDate><author>hello@craftedsignal.io</author><guid isPermaLink="true">https://feed.craftedsignal.io/briefs/2024-01-google-workspace-2sv-disabled/</guid><description>An adversary may disable 2-Step Verification (2SV) in Google Workspace to weaken account security and facilitate unauthorized access.</description><content:encoded><![CDATA[<p>Google Workspace administrators can enforce 2-Step Verification (2SV) to enhance user account security, requiring users to verify their identity beyond simple login credentials. This policy can be configured with various verification methods and enrollment periods. However, a malicious actor with administrative privileges may disable 2SV policies to reduce the security requirements for accessing targeted accounts. This could be a precursor to credential access or data exfiltration. The Elastic detection rule &quot;Google Workspace 2SV Policy Disabled&quot; was released on 2022-08-26 and updated on 2026-04-10 to detect this activity. This activity is important for defenders because it can lead to unauthorized access to sensitive data and systems.</p>
<h2 id="attack-chain">Attack Chain</h2>
<ol>
<li>An attacker gains unauthorized access to a Google Workspace administrator account, possibly through credential compromise or phishing.</li>
<li>The attacker authenticates to the Google Workspace admin console using the compromised credentials.</li>
<li>The attacker navigates to the Security settings within the admin console.</li>
<li>The attacker locates the 2-Step Verification settings.</li>
<li>The attacker disables the 2SV enforcement policy for specific organizational units or the entire domain. This generates a <code>google_workspace.login</code> event with <code>event.action: &quot;2sv_disable&quot;</code>.</li>
<li>The attacker may then attempt to access user accounts without the 2SV requirement, potentially using previously obtained credentials.</li>
<li>Upon successful login, the attacker performs malicious actions such as accessing sensitive data, modifying configurations, or establishing persistence.</li>
<li>The attacker covers their tracks by deleting audit logs or creating new admin accounts with modified permissions.</li>
</ol>
<h2 id="impact">Impact</h2>
<p>Disabling 2SV weakens the overall security posture of a Google Workspace environment. If successful, attackers can gain unauthorized access to user accounts, leading to data breaches, financial losses, and reputational damage. The number of affected users depends on the scope of the 2SV policy change and the extent of the attacker's access. Organizations in any sector relying on Google Workspace for email, file storage, or other services are vulnerable.</p>
<h2 id="recommendation">Recommendation</h2>
<ul>
<li>Deploy the provided Sigma rule to your SIEM to detect instances of 2SV policy being disabled and tune for your environment.</li>
<li>Review Google Workspace audit logs (<code>filebeat-*</code>, <code>logs-google_workspace*</code>) for unexpected 2SV configuration changes.</li>
<li>Implement the security best practices outlined by Google: <a href="https://support.google.com/a/answer/7587183">https://support.google.com/a/answer/7587183</a></li>
<li>Monitor <code>user.name</code> or <code>source.user.email</code> in the alert and filter <code>event.dataset</code> for <code>google_workspace.login</code> and aggregate by <code>user.name</code>, <code>event.action</code> to identify impacted users and authentication events.</li>
<li>Reduce the <code>var.interval</code> in the Google Workspace Filebeat module to 10 minutes (10m) to decrease the risk of missed events.</li>
</ul>
]]></content:encoded><category domain="severity">medium</category><category domain="type">advisory</category><category>google-workspace</category><category>2sv</category><category>persistence</category></item><item><title>GCP Multi-Factor Authentication Disabled</title><link>https://feed.craftedsignal.io/briefs/2024-01-gcp-mfa-disable/</link><pubDate>Tue, 02 Jan 2024 12:00:00 +0000</pubDate><author>hello@craftedsignal.io</author><guid isPermaLink="true">https://feed.craftedsignal.io/briefs/2024-01-gcp-mfa-disable/</guid><description>Detection of disabled multi-factor authentication (MFA) for a Google Cloud Platform (GCP) user, potentially leading to unauthorized access and data exfiltration.</description><content:encoded><![CDATA[<p>This brief focuses on detecting the disabling of multi-factor authentication (MFA) within a Google Cloud Platform (GCP) environment. The activity is detected by monitoring Google Workspace Admin logs for the <code>UNENROLL_USER_FROM_STRONG_AUTH</code> command. An attacker who has compromised an account may disable MFA to maintain persistent access without triggering typical account compromise alerts. This allows them to bypass an important security control. This activity has been observed in GCP environments and is critical for defenders to monitor. Successful exploitation can lead to unauthorized access, data exfiltration, or further malicious activity within the organization.</p>
<h2 id="attack-chain">Attack Chain</h2>
<ol>
<li>An attacker gains initial access to a valid user account through credential compromise (e.g., phishing, password spraying).</li>
<li>The attacker authenticates to the Google Workspace Admin console using the compromised account.</li>
<li>The attacker navigates to the user management section within the Google Workspace Admin console.</li>
<li>The attacker locates the target user account for which they intend to disable MFA.</li>
<li>The attacker initiates the process to unenroll the target user from strong authentication, triggering the <code>UNENROLL_USER_FROM_STRONG_AUTH</code> command.</li>
<li>The system processes the request, disabling MFA for the target user account.</li>
<li>The attacker now maintains persistent access to the compromised account without MFA.</li>
<li>The attacker leverages the compromised account to perform unauthorized actions, such as accessing sensitive data, modifying configurations, or launching further attacks.</li>
</ol>
<h2 id="impact">Impact</h2>
<p>Successful disabling of MFA can lead to significant security breaches. A single compromised account can provide attackers with persistent access to sensitive data and systems. This can result in data exfiltration, financial losses, reputational damage, and disruption of business operations. The number of affected users depends on the scope of the initial compromise.</p>
<h2 id="recommendation">Recommendation</h2>
<ul>
<li>Deploy the Sigma rule <code>Detect GCP MFA Disable via GWS Admin Logs</code> to your SIEM to identify instances of MFA being disabled.</li>
<li>Investigate any alerts generated by the Sigma rule, focusing on the <code>user</code> and <code>actor.email</code> fields to determine the source and target of the action.</li>
<li>Implement alerting on other critical admin actions in Google Workspace, beyond just MFA disabling, to give better context around potential account compromise (reference: Google Workspace Admin logs).</li>
<li>Review and enforce strong MFA policies across your organization to minimize the attack surface (reference: <a href="https://support.google.com/cloudidentity/answer/2537800?hl=en">https://support.google.com/cloudidentity/answer/2537800?hl=en</a>).</li>
</ul>
]]></content:encoded><category domain="severity">high</category><category domain="type">advisory</category><category>cloud</category><category>gcp</category><category>mfa</category><category>persistence</category><category>defense-evasion</category></item><item><title>Google Workspace Marketplace Restrictions Modified to Allow Any App</title><link>https://feed.craftedsignal.io/briefs/2024-01-gworkspace-marketplace-evasion/</link><pubDate>Tue, 02 Jan 2024 10:00:00 +0000</pubDate><author>hello@craftedsignal.io</author><guid isPermaLink="true">https://feed.craftedsignal.io/briefs/2024-01-gworkspace-marketplace-evasion/</guid><description>An adversary may modify Google Workspace Marketplace restrictions to allow installation of any application, potentially enabling the deployment of malicious APKs to end users within the Google Workspace environment, bypassing security restrictions.</description><content:encoded><![CDATA[<p>This rule detects when Google Marketplace restrictions within a Google Workspace environment are modified to allow the installation of any application. Such a configuration change can severely weaken the security posture of the organization, as it bypasses the intended restrictions that prevent users from installing potentially malicious applications. Adversaries could upload malicious APKs to the Google Marketplace and, by enabling the &quot;allow any app&quot; setting, facilitate their installation on mobile devices managed within the Google Workspace. Google clearly states that they are not responsible for any product on the Marketplace that originates from a source other than Google. This change allows any application from the marketplace to be installed and executed on mobile devices within a Google Workspace environment prior to distributing the malicious APK to the end user. This rule identifies when the global allow-all setting is enabled for Google Workspace Marketplace applications.</p>
<h2 id="attack-chain">Attack Chain</h2>
<ol>
<li>An attacker gains administrative access to the Google Workspace environment, potentially through compromised credentials or exploiting a vulnerability in the administrative interface.</li>
<li>The attacker navigates to the Google Workspace admin console and accesses the Google Workspace Marketplace Apps settings.</li>
<li>The attacker modifies the &quot;Apps Access Setting Allowlist access&quot; setting for the Google Workspace Marketplace application.</li>
<li>The attacker changes the setting from a restricted state (e.g., only allowing whitelisted applications) to &quot;ALLOW_ALL&quot;.</li>
<li>The attacker uploads a malicious APK to the Google Marketplace.</li>
<li>Users within the Google Workspace environment are now able to install the malicious APK without restriction.</li>
<li>The malicious APK executes on users' mobile devices, potentially leading to data theft, malware infection, or other malicious activities.</li>
<li>The attacker leverages the compromised devices to gain further access to the Google Workspace environment or other connected systems.</li>
</ol>
<h2 id="impact">Impact</h2>
<p>If successful, this attack can lead to widespread compromise of mobile devices within the Google Workspace environment. The number of affected users depends on the size of the organization and the number of users who install the malicious application. This can result in data breaches, financial losses, and reputational damage. The sectors targeted are broad, encompassing any organization using Google Workspace.</p>
<h2 id="recommendation">Recommendation</h2>
<ul>
<li>Deploy the Sigma rule <code>Google Workspace Marketplace Allow-All Setting</code> to detect when the &quot;Apps Access Setting Allowlist access&quot; is set to <code>ALLOW_ALL</code> in Google Workspace admin logs.</li>
<li>Investigate any instances where the <code>google_workspace.admin.new_value</code> field is set to <code>ALLOW_ALL</code> for the <code>Google Workspace Marketplace</code> application, as identified by the Sigma rule <code>Google Workspace Marketplace Allow-All Setting</code>.</li>
<li>Regularly review and audit Google Workspace Marketplace app settings to ensure they align with security best practices, as mentioned in the references.</li>
<li>Implement multi-factor authentication (MFA) for all administrative accounts in Google Workspace to prevent unauthorized access, which is the initial requirement for this attack.</li>
<li>Monitor the <code>event.action</code> is <code>ADD_APPLICATION</code> to identify applications installed after these changes were made. as described in the Overview</li>
</ul>
]]></content:encoded><category domain="severity">medium</category><category domain="type">advisory</category><category>google_workspace</category><category>defense_evasion</category><category>cloud</category></item><item><title>GCP Multiple Failed MFA Requests Imply MFA Fatigue Attack</title><link>https://feed.craftedsignal.io/briefs/2024-01-02-gcp-failed-mfa/</link><pubDate>Tue, 02 Jan 2024 10:00:00 +0000</pubDate><author>hello@craftedsignal.io</author><guid isPermaLink="true">https://feed.craftedsignal.io/briefs/2024-01-02-gcp-failed-mfa/</guid><description>Detection of multiple failed multi-factor authentication (MFA) requests for a single user in Google Cloud Platform (GCP) within a short time window, potentially indicating an MFA fatigue attack attempting to bypass MFA and gain unauthorized access.</description><content:encoded><![CDATA[<p>This analytic focuses on identifying potential MFA fatigue attacks targeting Google Cloud Platform (GCP) users. The technique involves an attacker repeatedly sending MFA push notifications or other authentication requests to a victim, overwhelming them in the hope they will eventually approve a request, either accidentally or to stop the barrage. This attack is particularly effective against users who are not technically savvy or who are under pressure to quickly resolve issues. The detection logic triggers when a user experiences 10 or more failed MFA attempts within a 5-minute window, based on Google Workspace login failure events. This is a notable indicator of a potential compromise attempt, as legitimate users rarely fail MFA multiple times in such a short period. Identifying and responding to these events promptly is crucial to prevent unauthorized access and potential privilege escalation within the GCP environment. The activity aligns with observed techniques used by threat actors like LAPSUS$ and Russian government-backed groups.</p>
<h2 id="attack-chain">Attack Chain</h2>
<ol>
<li>Attacker obtains a valid username and password through phishing, credential stuffing, or purchasing stolen credentials.</li>
<li>Attacker attempts to log in to a GCP service or application using the compromised credentials.</li>
<li>The GCP environment prompts the user for MFA.</li>
<li>Attacker initiates a large number of login attempts within a short timeframe.</li>
<li>Each login attempt triggers an MFA request to the legitimate user's device (phone, authenticator app, etc.).</li>
<li>The user is bombarded with MFA push notifications or prompts, leading to &quot;MFA fatigue.&quot;</li>
<li>The user, either accidentally or intentionally, approves one of the MFA requests.</li>
<li>Attacker successfully authenticates and gains unauthorized access to the GCP account.</li>
</ol>
<h2 id="impact">Impact</h2>
<p>Successful MFA bypass can lead to complete account takeover, allowing the attacker to access sensitive data, modify configurations, escalate privileges, and potentially deploy malicious workloads within the GCP environment. Depending on the compromised account's permissions, the attacker could gain control over critical infrastructure, leading to data breaches, service disruptions, or financial losses. Previous MFA fatigue attacks have resulted in significant compromises, including access to government and business systems.</p>
<h2 id="recommendation">Recommendation</h2>
<ul>
<li>Deploy the provided Sigma rule to your SIEM to detect multiple failed MFA requests (see <code>rules</code>).</li>
<li>Review and tune the threshold and time window in the Sigma rule based on your organization's baseline MFA behavior (see <code>rules</code>).</li>
<li>Investigate any alerts generated by the Sigma rule to determine the legitimacy of the failed MFA attempts.</li>
<li>Enforce stricter MFA policies, such as requiring number matching or hardware security keys, to mitigate MFA fatigue attacks.</li>
<li>Educate users about MFA fatigue attacks and the importance of carefully reviewing MFA requests.</li>
<li>Consider implementing adaptive authentication measures that analyze login behavior and block suspicious requests.</li>
</ul>
]]></content:encoded><category domain="severity">high</category><category domain="type">advisory</category><category>gcp</category><category>mfa</category><category>mfa-fatigue</category><category>credential-access</category></item></channel></rss>