Executive SummaryRisk level: High
What happened

The Starkiller Phishing Suite, developed by the Jinkusu group, uses Adversary/Account-in-the-Middle (AitM) proxy techniques to bypass MFA by relaying credentials and session interactions through counterfeit login pages in real time.

Who is affected

Organizations relying on traditional MFA, whose users can be lured to proxied login pages.

Why it matters

AitM defeats many MFA implementations by intercepting authentication live, turning user trust into account compromise.

Immediate recommended actions

  • Adopt phishing-resistant MFA (FIDO2/WebAuthn) resistant to AitM.
  • Deploy advanced email filtering and user awareness training.
  • Use adaptive MFA factoring device/location context.
  • Monitor sign-in logs for new-device/impossible-travel anomalies.
How to read this report. Items are labelled by confidence: Confirmed stated as fact in the source, Reported described by the source, Potential analyst inference, and Requires Validation to be confirmed in your environment. Where the source lacks detail this is stated as “Not specified in the source material”.

Key Technical Findings

Vulnerability / Campaign Type

AitM phishing suite (Starkiller / Jinkusu) for MFA bypass.

Affected Systems

User accounts on services protected by interceptable MFA.

Initial Access Vector

Phishing emails linking to proxied counterfeit login pages (T1566).

Execution Method

Real-time interception of credentials/sessions; client exploitation referenced (T1203).

Persistence

Not specified in the source material.

Privilege Escalation

Not specified in the source material.

Defense Evasion

Proxying legitimate login flows to appear authentic.

Credential Access

Capture of credentials and live authentication interactions.

Lateral Movement

Not specified in the source material.

Data Exfiltration

C2 over web protocols (T1071.001).

Impact Level

High – MFA bypass and account takeover.

Technical Background

Starkiller positions an attacker-controlled proxy between the user and the legitimate service. A phishing email directs the victim to a proxied login page; entered credentials and authentication interactions are relayed in real time, allowing the attacker to authenticate even when MFA is present.

This defeats time-based and push MFA but not phishing-resistant authenticators bound to the legitimate origin. Defenses center on FIDO2/WebAuthn, adaptive MFA, email filtering, and sign-in anomaly detection.

Attack Chain Analysis

  1. Initial Access

    ActivitySend phishing linking to a proxied login page (T1566).

    EvidenceLinks to look-alike domains.

    TelemetryEmail gateway, proxy logs.

    Detection opportunityFlag mail linking to newly seen look-alike domains.

  2. Credential Access

    ActivityRelay/capture credentials and session via AitM proxy.

    EvidenceLogins from proxy infrastructure; new devices.

    TelemetryIdP/SaaS sign-in logs.

    Detection opportunityAlert on impossible travel and unfamiliar ASNs.

  3. Command and Control

    ActivityCommunicate over web protocols (T1071.001).

    EvidenceOutbound web traffic to attacker infrastructure.

    TelemetryProxy/DNS.

    Detection opportunityMonitor for unusual outbound web traffic.

Deep Technical Behavior Analysis

The defining behavior is live session relay: because the proxy forwards the real authentication, MFA prompts succeed and the attacker captures a valid session. The strongest signals are sign-ins originating from proxy/hosting ASNs and impossible-travel anomalies; the durable fix is origin-bound, phishing-resistant MFA.

Specific Starkiller infrastructure and indicators are not specified in the source material and require validation.

Indicators of Compromise

No indicators of compromise were provided in the source material.

Indicators of Behavior

Behavioral indicators to hunt for even when atomic IoCs are limited (Potential — validate against your baseline).

Behavioral Indicator Description Data Source Confidence
Beaconing to rare destinations Periodic outbound connections to newly-seen domains/IPs or direct-IP C2. Proxy, firewall, DNS logs Potential
Unusual DNS queries High-entropy or rare domains; possible tunneling. DNS resolver logs Potential
Authentication anomalies Spraying/stuffing, impossible travel, or MFA fatigue patterns. IdP/VPN logs, Azure AD/Okta sign-ins Potential

Detection Engineering Guidance

Defensive detection logic (Potential — tune to your environment). No exploit code is included; logic is for hunting and alerting only.

T1071.001 — Application Layer Protocol: Web Protocols
  • ObjectiveDetect C2 over web protocols
  • Suspicious patternBeaconing to rare destinations
  • Data sourceProxy, firewall, DNS
  • False positivesAdmin tooling/automation; baseline before alerting.
  • ResponseTriage host, validate scope, preserve evidence, contain if confirmed.
pseudo: periodic outbound (low jitter) to newly-seen domain/IP
  with small uniform payloads => alert(level=medium)
Platform Log Source What to Look For Priority
Endpoint EDR / Defender telemetry Process tree, persistence, tamper attempts High
Identity IdP / VPN logs Impossible travel, spraying, MFA fatigue High
Network DNS resolver logs Rare/high-entropy domains, tunneling Medium
Network Proxy / firewall logs Beaconing, direct-IP C2, exfil volume High

MITRE ATT&CK Mapping

Tactic Technique ID Technique Name Relevance Detection Opportunity Confidence
Initial Access T1566 Phishing Phishing emails lure victims to malicious sites. Monitor for anomalous email patterns and sender addresses. Reported
Command and Control T1071.001 Application Layer Protocol: Web Protocols Use of web protocols for C2 communications. Monitor unusual outbound web traffic patterns. Reported
Execution T1203 Exploitation for Client Execution Exploitation of vulnerabilities in client applications. Track application crashes and exploit attempts via logs. Reported

Incident Response Guidance

  • Validate exposure and confirm whether the issue applies to your environment.
  • Preserve evidence (memory, disk, relevant logs) before remediation.
  • Isolate affected hosts/accounts if compromise is suspected.
  • Collect volatile data and review the log sources listed above.
  • Hunt for the indicators of behavior and any related atomic indicators.
  • Rotate potentially exposed credentials, keys, and session tokens.
  • Remove persistence (tasks, services, keys, web shells, cron, OAuth grants).
  • Patch affected systems; reimage where integrity cannot be assured.
  • Run post-remediation validation and a BAS/security-validation retest.

Remediation and Hardening

  • Patch affected systems and reduce internet-exposed services.
  • Enforce MFA and least-privilege for privileged and remote access.
  • Improve endpoint telemetry (Sysmon/EDR) and PowerShell logging.
  • Restrict script execution and constrain LOLBins where feasible.
  • Monitor persistence locations and disable unnecessary services.
  • Segment critical assets and review privileged accounts.
  • Rotate secrets and remove credentials from configuration files.
  • Tune SIEM/EDR detections, then validate controls after changes.

Business Risk

  • Service disruption: degraded or unavailable systems during compromise or recovery.
  • Data exposure: risk to sensitive, regulated, or customer data depending on scope.
  • Regulatory exposure: potential breach-notification and compliance obligations.
  • Financial impact: incident response, downtime, and potential extortion costs.
  • Brand and trust impact: reputational damage with customers and partners.
  • Identity blast radius: compromised accounts can expand access across cloud and SaaS.

Executive Takeaway

What leadership needs to know: AitM defeats many MFA implementations by intercepting authentication live, turning user trust into account compromise. Current assessed risk: High.

Prioritise: patching/exposure reduction, identity hardening (MFA, least privilege), and detection coverage for the techniques above.

Validate after remediation: re-test controls with breach & attack simulation to confirm the relevant techniques are now prevented or detected.

Validating Your Defenses with Valitrix

The Valitrix Breach and Attack Simulation (BAS) platform provides a continuous validation framework for security controls against real-world adversary techniques, including those employed by the Starkiller Phishing Suite. By emulating these specific MITRE ATT&CK techniques within a controlled environment, organizations can assess their detection capabilities and response readiness without exposing themselves to actual attacks.

This proactive approach enables SOC teams to refine their incident response procedures and enhance their overall security posture. Valitrix’s automated simulations ensure that detection mechanisms are not only in place but are effective against sophisticated phishing tactics like AitM, thus enabling organizations to stay one step ahead of evolving threats.

Key Takeaways

  • The Starkiller Phishing Suite employs advanced AitM techniques to bypass MFA protections.
  • User education is crucial in mitigating phishing threats effectively.
  • Robust detection mechanisms using EDR and email filtering are essential.
  • Valitrix BAS helps validate defenses against real-world attack simulations.

Frequently Asked Questions

What is the Starkiller Phishing Suite?

The Starkiller Phishing Suite is an advanced phishing toolkit designed to bypass multi-factor authentication using AitM techniques, targeting organizational credentials.

How can organizations detect Starkiller attacks?

Organizations should utilize EDR systems, proxy logs, and advanced email filtering to detect unusual access patterns and phishing attempts effectively.

What role does user education play in preventing phishing?

User education is vital; it empowers employees to recognize and report phishing attempts, significantly reducing the risk of credential theft.