tag: Phishing-as-a-Service · 5 items
- Engineer — Plan: AiTM phishing that defeats standard MFA is a config problem, not a patch problem — audit your Entra ID Conditional Access policies and prioritize migrating M365 users to phishing-resistant MFA (FIDO2/passkeys) this quarter, as TOTP and SMS are insufficient against this class of attack.
- SOC/IR — Act: This campaign is active and broadly targeting US enterprises via M365; hunt for AiTM indicators in Entra ID sign-in logs now — flag token issuance from unexpected IPs, session establishment followed by unusual API activity, and impossible-travel events from the same session cookie.
- Leader — Act: With 4,500 organizations targeted and ~48% of targeted addresses potentially compromised, confirm with your team this week that phishing-resistant MFA is enforced for M365 and assess whether your domain appeared in ANY.RUN’s targeting data; this is board-question territory given the scale.
- Engineer — Skip
- SOC/IR — Learn: The use of automated voice AI agents in a PhaaS platform to socially engineer victims is a meaningful escalation in vishing sophistication; no IOCs or enterprise detection surface are available yet, but analysts should track how this technique migrates toward corporate credential theft campaigns.
- Leader — Skip
- Engineer — Plan: AiTM and device-code phishing bypass standard MFA; audit your M365 conditional access policies to restrict or block device code flow, and prioritize phishing-resistant MFA (FIDO2 or certificate-based) for privileged accounts this quarter.
- SOC/IR — Plan: Build or tune detections for suspicious device-code OAuth grant flows and anomalous session token reuse in Entra ID / M365 audit logs — the AiTM component means valid MFA completion is not a reliable innocence signal.
- Leader — Learn: Confirms that commodity phishing platforms are now routing around standard MFA at scale; useful background when justifying a phishing-resistant MFA upgrade on the roadmap or fielding customer security questionnaires about M365 identity controls.
- Engineer — Plan: Device code flow abuse bypasses MFA by design; audit your identity provider (Entra ID, Okta) and restrict or disable the OAuth Device Authorization Grant for users/apps that don’t require it — block or conditional-policy-gate this flow this quarter.
- SOC/IR — Plan: No IOCs provided, but Greatness PhaaS commoditizing device code phishing signals growing campaign volume; build detections in Entra/Okta logs for unexpected device code authorization requests, particularly outside normal device-enrollment windows.
- Leader — Learn: MFA bypass techniques are now packaged in commercial crimeware toolkits, eroding the assurance value of standard MFA — useful context for risk register updates and for evaluating phishing-resistant auth (FIDO2/passkeys) as a strategic control.
- Engineer — Skip
- SOC/IR — Learn: The Kratos PhaaS takedown removes active infrastructure but no IOCs or TTPs are published in this item, so there is no immediate detection or hunt to run; useful background on the phishing-as-a-service ecosystem.
- Leader — Learn: A major PhaaS platform serving global customers has been dismantled — useful context for threat landscape briefings, but no immediate vendor exposure or regulatory action is required.