IPCRIME Underground Atlas | Threat Actor Profile | Reviewed November 21, 2026. Cinder, known in Unit 42’s tracking system as CL-CRI-1274, is one of several activity clusters identified in a November report about Com-affiliated cyber extortion. Researchers say they first observed the cluster in September 2026. The available information is strongest on tactics and cloud-service behavior; it does not establish who its members are.
The difference between a cluster and a group
Unit 42 distinguishes Cinder from Vortex, Helix and other clusters based on observed campaigns and related infrastructure. Similarities do not mean that all attacks were managed by one operator, or that an individual accused elsewhere is necessarily a participant. Tracking labels are analytical tools and can be revised as evidence improves.
Initial access and session persistence
The published research says initial access commonly began with voice phishing. In observed Cinder cases, attackers reused a persistent authenticated session, sometimes described by a ‘keep me signed in’ preference, to avoid generating another Duo multifactor prompt. The legitimate identity system was used with session material that an unauthorized operator had obtained.
This distinction matters operationally: a user can change a password while an existing session remains usable under some configurations. The defensive response depends on the provider’s token revocation and session-management controls, not just changing a secret and assuming access has ended.
Data access and pressure on victims
Unit 42 observed scripted use of cloud collaboration APIs and Microsoft Graph tooling to collect material from SharePoint and OneDrive. The reports also describe extortion messages being sent via internal email and Microsoft Teams after data collection. A message claiming data theft is a pressure tactic; the amount taken must still be established separately through evidence.
Indicators and investigative questions
- Examine sign-in and session-token activity during and after reports of suspicious calls.
- Review cloud application grants and whether persistent sessions were invalidated.
- Look for unusual SharePoint, OneDrive and Microsoft Graph export patterns, including high-volume reads.
- Preserve internal extortion messages and determine which account sent them.
- Track evidence-backed confidence when connecting a case to Cinder rather than inferring identity from slogans or reused infrastructure.
Scope and limitations
The primary report does not give a reliable count of Cinder victims or a comprehensive list of all industries affected. Its strongest evidence concerns recurring behavior in incident response and telemetry. Neither its description of browser extensions attributed to another cluster nor the reported actor landscape should be copied wholesale into Cinder’s profile.
Sources
Unit 42 — Com-affiliated vishing and extortion research, November 20; IPCRIME independent overview.
Research-grounded dossier; no firsthand identity attribution, private-data redistribution or law-enforcement partnership.