Ransomware family
BlackFile Ransomware Decryption & Data Recovery
- Active
- High
- No public decryptor
BlackFile is a vishing extortion crew Google tracks as UNC6671, active since early 2026: it calls employees' personal phones posing as the IT helpdesk, captures passwords and MFA through adversary-in-the-middle pages, then bulk-exports data from Microsoft 365 and Okta. After announcing a shutdown "under this name" in May it moved to REDACT and spread across brands such as Pink, Helix and Falcon. Google assesses it is independent of ShinyHunters, despite once borrowing that name.
- First seen
- 2026-01
- File extensions
- No public information
- Ransom notes
- No public information
- Affected platforms
- Windows
Family profile
- File extensions
- No public information
- Ransom notes
- No public information
- Contact patterns
- Tox at first; Session messenger only from February 2026
- From March 2026, extortion sent from hijacked internal corporate email and Microsoft Teams accounts
- Spam floods from dozens of Gmail accounts, threatening voicemails to executives and, in severe cases, swatting of staff
- A standard 72-hour deadline
- Aliases / versions
- UNC6671(Google 威胁情报追踪编号)、REDACT(2026 年 5 月起的主品牌)、Pink、Helix、Falcon、Cinder / Vortex(Arete 认为同属该体系)
- First seen
- 2026-01
- Status
- Active
- Operational status
- Actively operating
- Threat level
- High
- Affected platforms
- Windows
- Tags
- Extortion-only
- Active
- Rebranded
- Phishing
BlackFile and its successor brands run data-theft extortion. Neither of Google Threat Intelligence's two reports records an encryptor, so there is nothing to decrypt. The core of an incident is bulk export from cloud platforms such as Microsoft 365 and Okta; response centres on reclaiming accounts, scoping the exfiltration and meeting notification duties.
Latest activity
Google says UNC6671 now runs REDACT as its main brand alongside Pink, Helix and Falcon; 18 BlackFile wallets took 141.65 BTC from January to May 2026, with payments continuing after the shutdown notice.
SourcesThe Hacker News on UNC6671 vishing: helpdesk calls to personal phones, AitM theft of passwords and MFA, bulk export from Microsoft 365 and Okta. Tradecraft resembles SLH, but Google rates it a separate crew.
SourcesGTIG's BlackFile report: leak site launched 6 February, "shutting down under this name" notice on 11 May; GTIG assesses the operation is independent of ShinyHunters despite once borrowing its name.
Sources
Overview
Google Threat Intelligence Group (GTIG) has watched UNC6671's vishing operations since early January 2026. The group launched its leak site on 6 February and adopted the BlackFile name that month. By May GTIG counted dozens of targeted organisations across North America, Australia and the UK. Early victims were in manufacturing, healthcare and insurance; by July the focus had moved to private equity, law firms and rating agencies, with financial services a priority.
Rebrand. The leak site went offline in late April, returned briefly on 11 May with a notice that "BlackFile is shutting down… under this name", and GTIG read that as a transition rather than an end. GTIG later assessed with moderate confidence that the same core intrusion group moved to REDACT as its main brand and spread across further extortion brands including FALCON, HELIX and PINK, tied together by shared infrastructure - one lookalike domain, passkeyhelpdesk[.]com, targeted a Falcon victim and a Helix victim at the same time. Incident-response firm Arete's September report also places Cinder and possibly Vortex in this ecosystem, assessing that they remain interconnected despite claims of independence.
Earnings. Between January and May 2026, 18 BlackFile wallets received 141.65 BTC (about $10.69 million), and payments continued after the shutdown notice. Opening demands typically ran from $1 million to over $3 million, negotiations often cut them by 50-75%, and in more than half of tracked cases final payments averaged about $750,000.
Relationship to ShinyHunters. GTIG's May report states plainly that the operations are independent. UNC6671 borrowed the ShinyHunters brand at least once to make its threats more credible, but it uses separate Tox channels, distinct domain-registration patterns and its own leak site. As early as January, GTIG noted that although UNC6671's tradecraft closely matches UNC6661 (part of the ShinyHunters-branded activity), its extortion email was unbranded and used a different Tox ID, suggesting "separate individuals may be involved".
How to identify it
BlackFile does not encrypt files, so there is no extension and no ransom note file. Look for these signs instead:
Intrusion.
- Employees receive calls on personal phones from "IT" or "the helpdesk" about a mandatory passkey migration or MFA update; more recently the caller ID spoofs the real helpdesk number.
- They are steered to a subdomain carrying the company's name on root domains such as enrollms[.]com, passkeyms[.]com or setupsso[.]com, typically registered through Tucows.
- Right after the employee enters a password and approves MFA, an unknown MFA device appears in the account's security settings.
Data export.
- Access through the Microsoft 365 or Okta SSO dashboard into SharePoint, OneDrive, Zendesk, Salesforce and other apps, with searches for terms such as "confidential" and "SSN".
- Unified audit logs show python-requests or WindowsPowerShell user agents while the ClientAppId is spoofed as Microsoft Office.
- Because files are fetched directly, downloads are often recorded as FileAccessed rather than FileDownloaded, so counting download events badly understates the loss; GTIG recorded one case with more than a million files taken.
Extortion. The demand may arrive from your own hijacked internal email or Teams accounts, with Session as the contact channel and a 72-hour deadline.
Infection vectors
Entry is pure social engineering. No exploit and no malware on disk are needed. The operators call employees on personal phones, bypassing corporate security tooling and normal support channels, and use a passkey migration or MFA update as the pretext to send them to a company-branded fake login page.
Real-time MFA capture. The page is an adversary-in-the-middle phishing kit that relays the password to the real SSO provider; once the employee approves the MFA prompt, the operator immediately registers an attacker-controlled MFA device in the security settings for persistence.
Movement and export. With a Microsoft 365 or Okta account in hand, the operator logs into the SSO dashboard and reaches every cloud app tied to it. Export uses Python and PowerShell scripts, the Microsoft Graph API and reused session cookies such as FedAuth, over commercial VPN and hosting infrastructure.
Arete also records the Helix brand using ClickFix lures to trigger PowerShell payloads, so entry methods vary between brands in this ecosystem.
Encryption behavior
Neither GTIG's reports nor later coverage record BlackFile or its successor brands deploying an encryptor; this is a pure data-theft extortion operation. Its leak site usually posts only limited samples and directory listings, and GTIG has not seen it publish a victim's data in full.
No encryption does not mean less harm: the operators hold cloud-stored business files, contracts and personal data, and they add pressure by harassing staff, flooding mailboxes and threatening executives.
Assess before you act
Recoverability assessment
Nothing is encrypted in a BlackFile incident; the goal is to reclaim accounts, establish what left and stop the pressure campaign. We do not pay ransoms and do not negotiate.
1) Reclaim identities. Remove any unknown MFA devices, reset affected passwords, revoke every session and token (including session cookies such as FedAuth), and check for new app consents and mailbox forwarding rules.
2) Scope the exfiltration. Do not count only FileDownloaded events: include FileAccessed and requests from scripted user agents, and review each app's accessed sites, files and time windows to see whether customer, partner or personal data is involved.
3) Handle the pressure. Reclaim hijacked internal email and Teams accounts quickly, warn executives and staff that threatening calls may follow, and involve law enforcement in severe cases.
4) Notify. Complete regulatory, contractual and customer notification.
Our response plan
Hit by BlackFile ransomware? What to do
Reclaim accounts and preserve evidence
Immediately remove unknown MFA devices, reset passwords and revoke sessions and tokens; at the same time export Microsoft 365 unified audit logs, Okta system logs and each SaaS app's access logs before retention limits erase them.
Exfiltration scoping
Use audit logs to reconstruct which apps the operator entered, which sites and files were accessed and when activity began and ended, counting FileAccessed events and scripted user-agent requests alongside downloads, to produce a fact base for notification.
Hardening and staff warning
Move to phishing-resistant MFA such as FIDO2 security keys and require secondary verification for new MFA device registration; enable conditional access and impossible-travel alerts on SSO and Microsoft 365; tell staff plainly that IT will never call a personal phone to demand a passkey migration or MFA update.
Notification and monitoring
Complete external notification, prepare messaging for the harassment and pressure campaign, keep watching the REDACT, Pink, Helix and Falcon leak sites and lookalike domain registrations, and close with an incident report.
Risk warning
What not to do
- Do not downgrade the incident because nothing is encrypted - the data has left your cloud tenant and notification clocks are running.
- Do not reset passwords without also removing MFA devices and revoking sessions; the operator's device and session cookies stay valid otherwise.
- Do not judge the loss by counting download events alone; directly fetched files are logged as access.
- Do not reply to extortion messages arriving from internal email or Teams, and do not pay.
- Do not treat it as a ShinyHunters incident and borrow that group's public profile; Google assesses they are different crews.
Emergency response
Data already encrypted? Stop and let an engineer look first
We do not pay ransoms and we do not negotiate with attackers. Engineers run a free assessment first, then propose a recovery plan and a firm quote.
Related industries
Financial Services Ransomware Response and Recovery
Financial and quasi-financial institutions face far stricter requirements on data integrity, transaction continuity and regulatory reporting than most sectors, so one ransomware event hits availability, customer trust and compliance simultaneously. This page covers the threat profile, a recovery approach centred on transactional consistency, and hardening priorities.
Healthcare Ransomware Response and Recovery
When a hospital is hit, registration, consultation, orders, billing, laboratory and imaging fail at the same moment and care falls back to paper. This page covers the healthcare threat picture, a recovery priority built around clinical continuity, and the handling of patient data and compliance obligations.
Manufacturing Ransomware Response and Recovery
Ransomware in manufacturing hits information systems and production cadence at the same time: with ERP down there are no orders, with MES down there is no schedule, and an encrypted drawing library takes the process documentation for an entire product line with it. This page covers the asset profile, recovery priorities and targeted defences.
Similar families
- No public decryptor
Scattered LAPSUS$ Hunters
Scattered LAPSUS$ Hunters (SLSH) is a data-theft extortion alliance that formed on Telegram in August 2025 from ShinyHunters, Scattered Spider and LAPSUS$ members. It breaches Salesforce, Okta and Snowflake tenants at scale through vishing, insider recruitment and OAuth token abuse. Its own encryptor, ShinySp1d3r, was announced in November 2025 and samples have been analysed, but no deployment at scale has been confirmed as of September 2026.
- No public decryptor
ShinyHunters
ShinyHunters (ShinyCorp, UNC6240, Bling Libra; MITRE ATT&CK G1057) has run data-theft extortion since 2019 without ever encrypting a file. Operators use voice phishing and stolen SaaS OAuth tokens to pull data out of Salesforce, Snowflake and Databricks, then press with a Tor leak site and a 72-hour bitcoin deadline. Victim postings continued through 2026.
- No public decryptor
Silent Ransom Group
Silent Ransom Group (Luna Moth, Chatty Spider, UNC3753) is a Conti-lineage crew that extorts without encrypting anything. Operators impersonate an internal IT helpdesk by phone, walk staff into a remote-access session, take documents out, then press with a clearnet leak site and calls to employees. The FBI flagged in-person intrusions with USB storage in both May 2025 and May 2026.
FAQ
BlackFile Frequently asked questions
Are BlackFile, REDACT, Pink, Helix and Falcon the same group?
Google Threat Intelligence assesses with moderate confidence that one core intrusion group, UNC6671, is behind them: after announcing in May that BlackFile was shutting down "under this name", it moved to REDACT and spread across FALCON, HELIX, PINK and other brands, linked by shared lookalike domains. Arete also counts Cinder and possibly Vortex. For a victim the name changes nothing about the response: vishing takes over cloud accounts, data is bulk-exported, then extortion follows.
Is BlackFile part of ShinyHunters?
Google assesses it is not. The tradecraft is very similar - helpdesk impersonation calls, stolen passwords and MFA, bulk export from cloud platforms - and UNC6671 has borrowed the ShinyHunters name at least once. But Google's May report notes separate Tox channels, distinct domain-registration patterns and a dedicated leak site, and concludes the operations are independent.
An employee got a call from "IT" asking them to update MFA - how do we tell if it is real?
The simplest rule: hang up and call the helpdesk back through the company directory or intranet, and never open a link the caller sends. BlackFile calls usually go to personal phones with a passkey-migration or MFA-update pretext, and recently spoof the real helpdesk number, so caller ID cannot be trusted. If the employee has already entered a password or approved MFA, alert security at once to remove the device, reset the password and revoke sessions.
Sources
- Welcome to BlackFile: Inside a Vishing Extortion Operation — Google Threat Intelligence Group (2026-05-16)
- UNC6671 Rebrands: Multi-Brand Vishing Extortion Targets Financial Services and Enterprise Cloud Environments — Google Threat Intelligence Group
- Tracking the Expansion of ShinyHunters-Branded SaaS Data Theft (UNC6671 described as a separate cluster) — Google Threat Intelligence Group (2026-01-31)
- Hedge fund cyberattacks tied to BlackFile-linked UNC6671 extortion group — BleepingComputer
- UNC6671 Vishing Extortion Rebrands Across 5 Brands — SecurityOnline (2026-08-12)
- Ransomware Trends & Data Insights: September 2026 (BlackFile ecosystem, Helix ClickFix) — Arete
External links are provided for reference only. The content is published by third parties and does not represent our position.
Updated