Phishing Redirector

SIGMA detection rule by NTT Security - Patrik Olson, Ramine Etow · NOASSERTION

URL pattern seen in multiple successful phishing attacks in the last few days. This phishing redirector has been observed to be deployed on compromised websites. If the user passes the antibot checks, they are redirected to a MITM phishing proxy (EvilProxy). If the phish is successful, you should see authentication attempts from the phishing proxy IP address in Azure AD / Entra ID logs.

title: Phishing Redirector
id: 3dc81d88-6d9c-4c86-bc5d-ff743d50dbee
description: >-
  URL pattern seen in multiple successful phishing attacks in the last few days.
  This phishing redirector has been observed to be deployed on compromised websites. If the
  user passes the antibot checks, they are redirected to a MITM phishing proxy (EvilProxy).
  If the phish is successful, you should see authentication attempts from the phishing proxy
  IP address in Azure AD / Entra ID logs.
status: test
author: NTT Security - Patrik Olson, Ramine Etow
date: '2024-08-13'
modified: '2024-08-13'
logsource:
  category: proxy
detection:
  selection:
    c-uri-query|startswith: 'classic='
    c-uri-query|re: '^classic=[A-Za-z0-9]{10,}'
  condition: selection
falsepositives:
  - User may have opened phishing lure without entering any credentials. Look for suspicious authentication attempts
level: high
tags:
  - attack.defense-evasion

[[ currentRule.title && currentRule.title.length > 60 ? currentRule.title.slice(0, 60) + '…' : currentRule.title ]]

d743242d-8f9e-4ac9-8f6c-74193ee6798d

Propose edits, view related rules, and engage with the community through comments.

Executable code, not a declarative rule

This submission is arbitrary [[ currentRule.format ? currentRule.format.toUpperCase() : '' ]] code, not a declarative detection rule — review it as you would any script before running it, and note that it cannot be safely aggregated or auto-executed alongside YARA/Sigma/Suricata/CRS rules.

Rejected pattern present

[[ reason ]]

What does this mean?

Format & documentation suggestions

Not a security issue — this rule is valid and was accepted as-is. These are optional fields/conventions its own format recommends, mainly affecting its quality score and how well it documents itself for other reviewers.

[[ reason ]]

What do these messages mean?

[[ currentRule.title && currentRule.title.length > 60 ? currentRule.title.slice(0, 60) + '…' : currentRule.title ]]

[[ currentRule.title ]]

Community Discussion