AI Vishing Campaign Targets Wall Street Firms

Wall Street Giants Targeted in Coordinated AI Vishing Campaign

HIGH
August 8, 2026
6m read
PhishingThreat ActorCyberattack

Related Entities

Threat Actors

UNC6671BlackFileRedact

Organizations

Products & Tech

Other

BlackstoneKKRApolloCME GroupPoint72CitadelMillenniumTwo Sigma

Full Report

Executive Summary

A large-scale and sophisticated voice-phishing (vishing) campaign is actively targeting employees at some of the world's largest financial institutions. The targets include private-equity giants Blackstone and KKR, hedge funds like Citadel and Point72, and the exchange operator CME Group. The financially motivated threat actor, tracked as UNC6671 (also known as BlackFile and now rebranding as Redact), is using AI-powered voice cloning technology to impersonate corporate IT helpdesk personnel. The attackers socially engineer employees, directing them to adversary-in-the-middle (AitM) phishing sites designed to steal Microsoft 365 and Okta credentials, including real-time MFA tokens. The campaign's success in targeting high-value financial firms underscores the increasing effectiveness of AI-enhanced social engineering attacks.


Threat Overview

This campaign represents a significant evolution in phishing, combining AI technology with proven AitM techniques to bypass modern authentication controls.

  • Threat Actor: UNC6671 / BlackFile / Redact, a financially motivated group.
  • Targets: High-value employees at major financial firms, including hedge funds, private equity firms, and exchange operators.
  • Attack Vector: Voice-phishing (vishing). Attackers call employees on their personal mobile phones.
  • Tactic: The attackers use AI voice cloning to mimic the voices of IT support staff, creating a sense of legitimacy and urgency (e.g., "We need you to approve this security update.").
  • Phishing Infrastructure: Victims are directed to highly convincing, lookalike login portals for Microsoft 365 and Okta. These are AitM proxies that sit between the user and the real service.
  • Goal: To steal credentials (username, password) and intercept multi-factor authentication (MFA) tokens or session cookies in real-time, thereby gaining full access to the victim's account.
  • Post-Compromise: Once access is gained, the group uses automated tools to exfiltrate sensitive data from cloud and SaaS applications.

Firms like Two Sigma and Point72 have confirmed being targeted but stated they thwarted the attempts before significant data loss occurred.


Technical Analysis

The attack's technical sophistication lies in its seamless integration of social engineering and real-time credential capture.

  • AI Voice Cloning: The use of AI to mimic voices overcomes a traditional vishing hurdle: the caller's voice not sounding familiar or professional. This makes the social engineering aspect far more convincing.
  • Adversary-in-the-Middle (AitM): This is the key technical component for bypassing MFA. The phishing site is not a static page; it's a reverse proxy. When the victim enters their credentials, the AitM kit forwards them to the real login service (e.g., Microsoft). When the real service prompts for an MFA code, the prompt is passed back to the victim. The victim enters their MFA code into the phishing site, which is then captured and used by the attacker to complete the login and steal the resulting session cookie.

MITRE ATT&CK Mapping


Impact Assessment

A successful attack against an employee at a major financial firm can have devastating consequences.

  • Financial Data Theft: Attackers can gain access to non-public market information, M&A details, trading strategies, and client financial data.
  • Fraud: Compromised accounts can be used to authorize fraudulent wire transfers or manipulate financial records.
  • Market Manipulation: Access to pre-release earnings reports or other sensitive information could be used for insider trading or market manipulation.
  • Widespread Compromise: A single compromised account, especially a privileged one, can be used as a beachhead to move laterally within the firm's network.

IOCs — Directly from Articles

No specific domains, IPs, or other IOCs were provided in the source articles.


Cyber Observables — Hunting Hints

Detecting AitM activity requires looking for subtle anomalies in the authentication process.

Type
log_source
Value
IdP Logs (Okta, Entra ID)
Description
Look for successful logins from unfamiliar IP addresses, ASNs, or geolocations, especially if they occur shortly after a known vishing attempt.
Context
SIEM, Identity Provider logs
Confidence
high
Type
user_agent
Value
Unusual User-Agent strings
Description
AitM phishing kits may use non-standard or unusual User-Agent strings that differ from legitimate browser traffic.
Context
Web proxy logs, IdP logs
Confidence
low
Type
network_traffic_pattern
Value
Mismatched IP geolocation
Description
A user's login IP is in one country, but their VPN or corporate IP is in another.
Context
IdP logs, VPN logs, Firewall logs
Confidence
medium
Type
event_id
Value
Suspicious MFA device registration
Description
Attackers may attempt to register their own device for MFA after compromising an account. Monitor for new MFA device enrollments.
Context
IdP logs
Confidence
high

Detection & Response

Detection

  • User Reporting: The most effective detection is a well-trained workforce that can recognize and report suspicious calls to the security team.
  • Identity Provider (IdP) Analytics: Modern IdPs like Okta and Microsoft Entra ID have built-in risk engines that can detect impossible travel, anomalous device fingerprints, and other signs of session hijacking.
  • Monitor for AitM Phishing Kits: Security teams can proactively hunt for newly registered domains that impersonate their own brand and use tools that detect the signatures of known AitM phishing kits.

Response

  • Immediate Session Revocation: If a compromise is suspected, the first step is to revoke all active sessions for the user's account and force a password reset. This is a key D3FEND technique: User-initiated Compromise Remediation.
  • Account Lockout: Temporarily lock the account to prevent further unauthorized access while the investigation is underway.
  • Forensic Analysis: Analyze logs from the IdP, endpoints, and SaaS applications to determine the scope of the compromise and what data was accessed or exfiltrated.

Mitigation

  1. User Training: This is the most critical mitigation. Employees must be trained to be suspicious of any unsolicited call, especially those creating urgency and asking for credentials or for them to visit a website. They should be instructed to hang up and call the IT helpdesk back on a known, official number.
  2. Phishing-Resistant MFA: The ultimate technical control against AitM attacks is to use phishing-resistant MFA, such as FIDO2 security keys (e.g., YubiKey). These methods tie the authentication to the specific domain, and the browser will not allow the credential to be used on a phishing site, breaking the AitM chain. This is an application of D3FEND's Hardware-based Process Isolation (D3-HBPI) at the authentication level.
  3. Conditional Access Policies: Implement strict conditional access policies that block logins from non-compliant devices, untrusted locations, or IP addresses associated with anonymous proxies.
  4. Limit Personal Device Use: Enforce policies that restrict employees from logging into corporate resources from personal, unmanaged devices, which are harder to monitor and secure.

Timeline of Events

1
August 8, 2026
This article was published

MITRE ATT&CK Mitigations

The primary defense is training employees to recognize and report unsolicited vishing calls, and to independently verify requests via official channels.

Deploy phishing-resistant MFA, such as FIDO2 security keys, to technically prevent credential theft via AitM phishing sites.

Use IdP risk engines and UEBA to detect anomalous login behavior like impossible travel or unusual device fingerprints.

Use web filtering to block access to known phishing sites and newly registered domains.

D3FEND Defensive Countermeasures

To defeat the core technical component of this vishing campaign, organizations must upgrade from standard MFA (like SMS or push notifications) to phishing-resistant MFA. This specifically means deploying FIDO2-compliant authenticators, such as YubiKeys or Windows Hello for Business with hardware-backed keys. When a user attempts to log in, the FIDO2 protocol cryptographically binds the authentication ceremony to the domain name of the site they are on. If a user is lured to an AitM phishing site (e.g., login-okta.phish.com), the browser will prevent the security key from responding because the domain does not match the legitimate one (company.okta.com). This breaks the attack chain at a technical level, regardless of how convincing the AI-cloned voice is. This is the single most effective technical control against AitM phishing.

Since user training is paramount, it must be continuous and data-driven. Implement a robust User Behavior Analysis (D3-UBA) program that includes simulated vishing attacks. Use a variety of scenarios, including ones that mimic the UNC6671 tactics (e.g., urgent call from IT). Track metrics on which employees report the calls versus which ones fall for them. Use this data to provide targeted, non-punitive follow-up training to employees who are more susceptible. The goal is to build a 'human firewall' where the default employee reaction to an unsolicited, urgent call from 'IT' is to hang up and call the service desk back on a trusted, internally published number. This cultural and behavioral shift is a critical non-technical countermeasure.

To detect a successful compromise in near real-time, security teams should implement Authentication Event Thresholding (D3-ANET) within their SIEM. This involves creating detection rules that correlate multiple authentication signals. For example, a high-fidelity alert should be generated if the following sequence occurs for a single user account: [1] A successful MFA login from a new or non-corporate IP address/ASN, followed by [2] An attempt to enroll a new MFA device, and then [3] A high volume of data access or email exfiltration via APIs like Microsoft Graph. This pattern is highly indicative of an account takeover. By setting thresholds and chaining these events together, the security team can move beyond simple 'impossible travel' alerts to detecting the entire TTP of the UNC6671 group post-compromise.

Article Author

Jason Gomes

Jason Gomes

• Cybersecurity Practitioner

Cybersecurity professional with over 10 years of specialized experience in security operations, threat intelligence, incident response, and security automation. Expertise spans SOAR/XSOAR orchestration, threat intelligence platforms, SIEM/UEBA analytics, and building cyber fusion centers. Background includes technical enablement, solution architecture for enterprise and government clients, and implementing security automation workflows across IR, TIP, and SOC use cases.

Threat Intelligence & AnalysisSecurity Orchestration (SOAR/XSOAR)Incident Response & Digital ForensicsSecurity Operations Center (SOC)SIEM & Security AnalyticsCyber Fusion & Threat SharingSecurity Automation & IntegrationManaged Detection & Response (MDR)

Editorial Standards & Analyst Review

CyberNetSec.io uses automation to assist source monitoring, deduplication, observable extraction, and structured intelligence generation. Published analysis follows human-defined editorial standards and adds defensive context including MITRE ATT&CK, D3FEND, STIX, and Sigma where applicable. Read our editorial policy.

Tags

VishingPhishingAIVoice CloningUNC6671BlackFileWall StreetFinanceAitM

📢 Share This Article

Help others stay informed about cybersecurity threats

🎯 MITRE ATT&CK Mapped

Every tactic, technique, and sub-technique used in this threat has been identified and mapped to the MITRE ATT&CK framework for consistent, actionable threat language.

🧠 Enriched & Analyzed

Observables and indicators of compromise (IOCs) have been extracted and cataloged. Risk has been assessed and correlated with known threat actors and historical campaigns.

🛡️ Actionable Guidance

Detection rules, incident response steps, and D3FEND-aligned mitigation strategies are included so your team can act on this intelligence immediately.

🔗 STIX Visualizer

Structured threat data is packaged as a STIX 2.1 bundle and can be visualized as an interactive graph — relationships between actors, malware, techniques, and indicators.

Sigma Generator

Sigma detection rules are derived from the threat techniques in this article and can be converted for deployment across any major SIEM or EDR platform.