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.
This campaign represents a significant evolution in phishing, combining AI technology with proven AitM techniques to bypass modern authentication controls.
Firms like Two Sigma and Point72 have confirmed being targeted but stated they thwarted the attempts before significant data loss occurred.
The attack's technical sophistication lies in its seamless integration of social engineering and real-time credential capture.
T1566.004 - Spearphishing Voice: The core of the attack is vishing, using voice calls to manipulate victims.T1648 - AI-Generated Content: The use of AI voice cloning falls under this new ATT&CK technique for creating deceptive content.T1598.003 - Spearphishing Link: The vishing call directs the user to a malicious link.T1110.004 - Credential Stuffing: The attackers use an AitM setup to steal credentials in real-time, effectively bypassing MFA.T1539 - Steal Web Session Cookie: The ultimate goal of the AitM attack is to steal the authenticated session cookie, which allows the attacker to take over the session without needing the password or MFA again.T1114 - Email Collection: Post-compromise, the attackers exfiltrate sensitive data from the user's email account.A successful attack against an employee at a major financial firm can have devastating consequences.
No specific domains, IPs, or other IOCs were provided in the source articles.
Detecting AitM activity requires looking for subtle anomalies in the authentication process.
User-initiated Compromise Remediation.Hardware-based Process Isolation (D3-HBPI) at the authentication level.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.
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.

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.
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.
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.
Observables and indicators of compromise (IOCs) have been extracted and cataloged. Risk has been assessed and correlated with known threat actors and historical campaigns.
Detection rules, incident response steps, and D3FEND-aligned mitigation strategies are included so your team can act on this intelligence immediately.
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 detection rules are derived from the threat techniques in this article and can be converted for deployment across any major SIEM or EDR platform.