LiveActive security incident?Get immediate response
MITRE ATT&CK® Campaign

C0059: Salesforce Data Exfiltration

The Salesforce Data Exfiltration campaign began in October 2024 with financially-motivated threat actor UNC6040 using Spearphishing Voice (vishing) to compromise corporate Salesforce instances for large-scale data theft and extortion. Following the initial data theft, victim organizations received extortion demands from a separate threat actor, UNC6240, who claimed to be the “ShinyHunters” group. The observed infrastructure and TTPs used during the Salesforce Data Exfiltration campaign overlap with those used by threat groups with suspected ties to the broader collective known as "The Com.” These overlaps could plausibly be the result of associated actors operating within the same communities and are not necessarily an indication of a direct operational relationship.[1][2]

EnterpriseC0059CampaignObject v1.0Modified
Glexia's Take · Automated analysis

Security context for executives and security teams

Automation confidenceMedium

This campaign matters because it frames CRM data theft as a business-continuity and extortion risk, not just a phishing problem. The supplied ATT&CK description says actors used voice spearphishing to compromise corporate Salesforce instances, steal data at scale, and support extortion demands. For leaders, the key decision is whether Salesforce and related SaaS access, integrations, and export activity are governed and monitored with the same rigor as core identity and financial systems.

Executive priority

Prioritize validation of identity controls, SaaS administration, CRM data governance, and incident response playbooks for data-theft extortion scenarios. Executives should ask: who can approve or install Salesforce/OAuth integrations, who can export customer data, how quickly can anomalous CRM access be investigated, and what evidence would support breach assessment, customer notification, and regulator-facing reporting. This object is especially relevant to cloud security, IAM, SOC readiness, IR retainers, compliance evidence, and customer-data risk management.

Technical view

ATT&CK provides no campaign-specific detection text, so defenders should build coverage from the described behavior and related techniques: voice spearphishing for information, impersonation, abuse of domain accounts, CRM data collection, SaaS/OAuth application integration persistence, automated exfiltration, exfiltration over web services, proxy and multi-hop proxy use including Tor, and possible Python/tooling activity. SOC teams should validate Salesforce audit logging, identity-provider logs, OAuth consent/application events, CRM export/API activity, anomalous session origin changes, and network egress indicators associated with proxies or Tor where applicable.

Likely telemetry

  • Salesforce login, session, API, report/export, bulk data access, administrative, and integration audit events
  • Identity provider authentication logs, MFA events, conditional access decisions, domain account activity, and password/reset or recovery events
  • OAuth consent, connected-app creation, permission grant, token issuance, and token reuse events for SaaS environments
  • Help desk, call center, and security awareness reporting for voice phishing and impersonation attempts
  • Network egress logs, proxy logs, DNS logs, TLS metadata, and firewall events showing access to external web services, proxies, multi-hop infrastructure, or Tor-related traffic

Detection direction

  • Confirm that Salesforce and other CRM audit logs are enabled, retained long enough for investigations, and correlated with identity-provider authentication events.
  • Baseline normal CRM export, API, reporting, and integration behavior by user role so large-scale or unusual data access can be triaged without relying only on static indicators.
  • Tune detections for impossible travel, new device or location access, MFA fatigue or recovery anomalies, new OAuth/connected applications, high-volume object queries, and unusual use of privileged or domain accounts.
  • Treat voice phishing reports as security telemetry: correlate help desk calls, user reports, and identity events around the same time window.
  • Add context for proxies, multi-hop proxy behavior, and Tor, but avoid assuming all anonymized traffic is malicious; focus on correlation with CRM access, new sessions, or export behavior.

Mitigation priorities

  • Harden identity first: enforce phishing-resistant MFA where feasible, conditional access, least privilege, and rapid credential/session revocation for Salesforce and domain accounts.
  • Govern SaaS integrations: require approval for OAuth/connected apps, restrict high-risk scopes, review existing integrations, and monitor token activity.
  • Limit CRM data exposure through role-based access, export restrictions, segmentation of sensitive customer fields, and periodic entitlement reviews.
  • Prepare IR procedures for SaaS data theft: preserve Salesforce and IdP logs, identify affected objects/records, revoke tokens, disable suspicious integrations, and coordinate legal/compliance notification workflows.
  • Train help desk and business users on voice phishing and impersonation scenarios, including verification procedures for requests involving credentials, MFA, links, or SaaS access.
Additional notes and limits

The official description identifies a financially motivated campaign involving Salesforce compromise, data theft, and extortion demands, with reported use of vishing and overlaps with communities associated with “The Com.” The relationship set materially broadens defensive planning across reconnaissance, resource development, identity abuse, SaaS persistence, CRM collection, proxy use, and exfiltration. The most important local validation question is whether the organization can reconstruct who accessed and exported CRM data, through which identity path and integration, and over what time period.

ATT&CK does not provide official detection guidance for this campaign, and the campaign object itself lists no platforms or tactics. Platform references in this take are limited to the official description’s Salesforce/CRM context and related ATT&CK techniques such as SaaS, Office Suite, Windows, Linux, macOS, ESXi, Network Devices, and PRE where applicable. Local telemetry, Salesforce configuration, identity architecture, and integration inventory are required to determine actual exposure or coverage.

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Official MITRE ATT&CK definition

Salesforce Data Exfiltration

The Salesforce Data Exfiltration campaign began in October 2024 with financially-motivated threat actor UNC6040 using Spearphishing Voice (vishing) to compromise corporate Salesforce instances for large-scale data theft and extortion. Following the initial data theft, victim organizations received extortion demands from a separate threat actor, UNC6240, who claimed to be the “ShinyHunters” group. The observed infrastructure and TTPs used during the Salesforce Data Exfiltration campaign overlap with those used by threat groups with suspected ties to the broader collective known as "The Com.” These overlaps could plausibly be the result of associated actors operating within the same communities and are not necessarily an indication of a direct operational relationship.[1][2]

View the same entry on attack.mitre.org (MITRE-hosted reference; in-page links above use the Glexia ATT&CK library.)

Glexia analysis

How security teams should use this page

Treat this object as behavior context, not an attribution claim. Validate the related groups, software, data sources, and mitigations against official ATT&CK relationships and your own telemetry before making control-coverage decisions.

ATT&CK relationship table

Techniques used

This mirrors the MITRE pattern of making group, software, campaign, and technique relationships scannable. Relationship notes come from mirrored ATT&CK relationship text when available.

18 rows
DomainIDNameRelationship / procedure
EnterpriseT1684.001ImpersonationSub-technique

During Salesforce Data Exfiltration, threat actors impersonated IT support personnel in voice calls with victims at times claiming to be addressing enterprise-wide connectivity issues.[2][1]

EnterpriseT1608.005Link TargetSub-technique

During Salesforce Data Exfiltration, threat actors established an Okta phishing panel which victims were tricked into accessing from mobile phones or work computers during social engineering calls.[1][2]

EnterpriseT1059.006PythonSub-technique

During Salesforce Data Exfiltration, threat actors used custom applications developed in python.[2]

EnterpriseT1213.004Customer Relationship Management SoftwareSub-technique

During Salesforce Data Exfiltration, threat actors accessed and exfiltrated sensitive information from compromised Salesforce instances.[2]

EnterpriseT1671Cloud Application Integration

During Salesforce Data Exfiltration, threat actors deceived victims into authorizing malicious connected apps to their organization's Salesforce portal.[1][2]

EnterpriseT1078.002Domain AccountsSub-technique

During Salesforce Data Exfiltration, threat actors used compromised credentials for lateral movement.[1][2]

EnterpriseT1567Exfiltration Over Web Service

During Salesforce Data Exfiltration, threat actors exfiltrated data via legitimate Salesforce API communication channels including the Salesforce Data Loader application.[2][1]

EnterpriseT1036Masquerading

During Salesforce Data Exfiltration, threat actors used voice calls to socially engineer victims into authorizing a modified version of the Salesforce Data Loader app.[2]

EnterpriseT1090Proxy

During Salesforce Data Exfiltration, threat actors used Mullvad VPN IPs to proxy voice phishing calls.[2]

EnterpriseT1585.002Email AccountsSub-technique

During Salesforce Data Exfiltration, threat actors registered emails shinycorp@tuta[.]com and shinygroup@tuta[.]com to send victims extortion demands.[2]

EnterpriseT1083File and Directory Discovery

During Salesforce Data Exfiltration, threat actors queried customers' Salesforce environments to identify sensitive information for exfiltration.[1]

EnterpriseT1090.003Multi-hop ProxySub-technique

During Salesforce Data Exfiltration, threat actors used Tor IPs for voice calls and for the collection of stolen data.[2]

EnterpriseT1585Establish Accounts

During Salesforce Data Exfiltration, threat actors created Salesforce trial accounts to register their malicious applications.[2]

EnterpriseT1587.001MalwareSub-technique

During Salesforce Data Exfiltration, threat actors created malicious applications within Salesforce trial accounts, typically Python scripts with similar function to the Salesforce Data Loader.[1][2]

EnterpriseT1588.002ToolSub-technique

During Salesforce Data Exfiltration, threat actors initially relied on the legitimate Salesforce Data Loader app for data exfiltration.[2][1]

EnterpriseT1020Automated Exfiltration

During Salesforce Data Exfiltration, threat actors used API queries to automatically exfiltrate large volumes of data.[1]

EnterpriseT1586.002Email AccountsSub-technique

During Salesforce Data Exfiltration, threat actors used compromised emails to create Salesforce trial accounts.[2]

EnterpriseT1598.004Spearphishing VoiceSub-technique

During Salesforce Data Exfiltration, threat actors initiated voice calls with victims to socially engineer them into authorizing malicious applications or divulging sensitive credentials.[1][2]

Associated objects

Groups, software, and campaigns

ToolEnterprise

S0183: Tor

Tor is a software suite and network that provides increased anonymity on the Internet. It creates a multi-hop proxy network and utilizes multilayer encryption to protect both the message and routing information. Tor utilizes "Onion Routing," in which messages are encrypted with multiple layers of encryption; at each step in the proxy network, the topmost layer is decrypted and the contents forwarded on to the next node until it reaches its destination. [1]

LinuxWindowsmacOS
Relationship explorer

All related ATT&CK context

Change history

Object version and sync metadata

The fields below describe the current mirrored snapshot. When Glexia retains multiple ATT&CK source imports, you can open the table to compare the same object across releases (hashes and MITRE timestamps). For MITRE’s own release notes and roadmap, see ATT&CK resources — Updates.

ATT&CK release
19.1
Object version
1.0
Created
Modified
Raw hash
ee83c93e765e94ec...
Imported snapshots across ATT&CK releases(1)
ReleaseBundle importedObject versionModifiedStatusRaw hash
19.11.0Current bundleee83c93e765e…
Raw source

Mirrored ATT&CK source object

The raw object is retained through the mirrored ATT&CK source bundle and object hash. The raw endpoint returns the exact object from the mirrored bundle when available.

Source references

External references and citations

MITRE external references are preserved separately from Glexia analysis so citations remain traceable to their original source records.

  1. [1]
    FBI Salesforce Data Theft SEP 2025

    FBI Cyber Division. (2025, September 12). Cyber Criminal Groups UNC6040 and UNC6395 Compromising Salesforce Instances for Data Theft and Extortion. Retrieved October 22, 2025.

    Open source URL
  2. [2]
    Google Salesforce JUN 2025

    Google Threat Intelligence Group. (2025, June 4). The Cost of a Call: From Voice Phishing to Data Extortion. Retrieved October 22, 2025.

    Open source URL
  3. [3]
    FBI Salesforce Data Theft SEP 2025

    FBI Cyber Division. (2025, September 12). Cyber Criminal Groups UNC6040 and UNC6395 Compromising Salesforce Instances for Data Theft and Extortion. Retrieved October 22, 2025.

    Open source URL
  4. [4]
    FBI Salesforce Data Theft SEP 2025

    FBI Cyber Division. (2025, September 12). Cyber Criminal Groups UNC6040 and UNC6395 Compromising Salesforce Instances for Data Theft and Extortion. Retrieved October 22, 2025.

    Open source URL
  5. [5]
    Google Salesforce JUN 2025

    Google Threat Intelligence Group. (2025, June 4). The Cost of a Call: From Voice Phishing to Data Extortion. Retrieved October 22, 2025.

    Open source URL
  6. [6]
    Google Salesforce JUN 2025

    Google Threat Intelligence Group. (2025, June 4). The Cost of a Call: From Voice Phishing to Data Extortion. Retrieved October 22, 2025.

    Open source URL
  7. [7]
    mitre-attackC0059
    Open source URL
  8. [8]
    mitre-attackC0059
    Open source URL
  9. [9]
    mitre-attackC0059
    Open source URL
  10. [10]
    FBI Salesforce Data Theft SEP 2025

    FBI Cyber Division. (2025, September 12). Cyber Criminal Groups UNC6040 and UNC6395 Compromising Salesforce Instances for Data Theft and Extortion. Retrieved October 22, 2025.

    Open source URL
  11. [11]
    FBI Salesforce Data Theft SEP 2025

    FBI Cyber Division. (2025, September 12). Cyber Criminal Groups UNC6040 and UNC6395 Compromising Salesforce Instances for Data Theft and Extortion. Retrieved October 22, 2025.

    Open source URL
  12. [12]
    Google Salesforce JUN 2025

    Google Threat Intelligence Group. (2025, June 4). The Cost of a Call: From Voice Phishing to Data Extortion. Retrieved October 22, 2025.

    Open source URL
  13. [13]
    Google Salesforce JUN 2025

    Google Threat Intelligence Group. (2025, June 4). The Cost of a Call: From Voice Phishing to Data Extortion. Retrieved October 22, 2025.

    Open source URL
  14. [14]
    FBI Salesforce Data Theft SEP 2025

    FBI Cyber Division. (2025, September 12). Cyber Criminal Groups UNC6040 and UNC6395 Compromising Salesforce Instances for Data Theft and Extortion. Retrieved October 22, 2025.

    Open source URL
  15. [15]
    FBI Salesforce Data Theft SEP 2025

    FBI Cyber Division. (2025, September 12). Cyber Criminal Groups UNC6040 and UNC6395 Compromising Salesforce Instances for Data Theft and Extortion. Retrieved October 22, 2025.

    Open source URL
  16. [16]
    Google Salesforce JUN 2025

    Google Threat Intelligence Group. (2025, June 4). The Cost of a Call: From Voice Phishing to Data Extortion. Retrieved October 22, 2025.

    Open source URL
  17. [17]
    Google Salesforce JUN 2025

    Google Threat Intelligence Group. (2025, June 4). The Cost of a Call: From Voice Phishing to Data Extortion. Retrieved October 22, 2025.

    Open source URL
  18. [18]
    Google Salesforce JUN 2025

    Google Threat Intelligence Group. (2025, June 4). The Cost of a Call: From Voice Phishing to Data Extortion. Retrieved October 22, 2025.

    Open source URL
  19. [19]
    Google Salesforce JUN 2025

    Google Threat Intelligence Group. (2025, June 4). The Cost of a Call: From Voice Phishing to Data Extortion. Retrieved October 22, 2025.

    Open source URL
  20. [20]
    Google Salesforce JUN 2025

    Google Threat Intelligence Group. (2025, June 4). The Cost of a Call: From Voice Phishing to Data Extortion. Retrieved October 22, 2025.

    Open source URL
  21. [21]
    Google Salesforce JUN 2025

    Google Threat Intelligence Group. (2025, June 4). The Cost of a Call: From Voice Phishing to Data Extortion. Retrieved October 22, 2025.

    Open source URL
  22. [22]
    FBI Salesforce Data Theft SEP 2025

    FBI Cyber Division. (2025, September 12). Cyber Criminal Groups UNC6040 and UNC6395 Compromising Salesforce Instances for Data Theft and Extortion. Retrieved October 22, 2025.

    Open source URL
  23. [23]
    FBI Salesforce Data Theft SEP 2025

    FBI Cyber Division. (2025, September 12). Cyber Criminal Groups UNC6040 and UNC6395 Compromising Salesforce Instances for Data Theft and Extortion. Retrieved October 22, 2025.

    Open source URL
  24. [24]
    Google Salesforce JUN 2025

    Google Threat Intelligence Group. (2025, June 4). The Cost of a Call: From Voice Phishing to Data Extortion. Retrieved October 22, 2025.

    Open source URL
  25. [25]
    Google Salesforce JUN 2025

    Google Threat Intelligence Group. (2025, June 4). The Cost of a Call: From Voice Phishing to Data Extortion. Retrieved October 22, 2025.

    Open source URL
  26. [26]
    FBI Salesforce Data Theft SEP 2025

    FBI Cyber Division. (2025, September 12). Cyber Criminal Groups UNC6040 and UNC6395 Compromising Salesforce Instances for Data Theft and Extortion. Retrieved October 22, 2025.

    Open source URL
  27. [27]
    FBI Salesforce Data Theft SEP 2025

    FBI Cyber Division. (2025, September 12). Cyber Criminal Groups UNC6040 and UNC6395 Compromising Salesforce Instances for Data Theft and Extortion. Retrieved October 22, 2025.

    Open source URL
  28. [28]
    Google Salesforce JUN 2025

    Google Threat Intelligence Group. (2025, June 4). The Cost of a Call: From Voice Phishing to Data Extortion. Retrieved October 22, 2025.

    Open source URL
  29. [29]
    Google Salesforce JUN 2025

    Google Threat Intelligence Group. (2025, June 4). The Cost of a Call: From Voice Phishing to Data Extortion. Retrieved October 22, 2025.

    Open source URL
  30. [30]
    FBI Salesforce Data Theft SEP 2025

    FBI Cyber Division. (2025, September 12). Cyber Criminal Groups UNC6040 and UNC6395 Compromising Salesforce Instances for Data Theft and Extortion. Retrieved October 22, 2025.

    Open source URL
  31. [31]
    FBI Salesforce Data Theft SEP 2025

    FBI Cyber Division. (2025, September 12). Cyber Criminal Groups UNC6040 and UNC6395 Compromising Salesforce Instances for Data Theft and Extortion. Retrieved October 22, 2025.

    Open source URL
  32. [32]
    Google Salesforce JUN 2025

    Google Threat Intelligence Group. (2025, June 4). The Cost of a Call: From Voice Phishing to Data Extortion. Retrieved October 22, 2025.

    Open source URL
  33. [33]
    Google Salesforce JUN 2025

    Google Threat Intelligence Group. (2025, June 4). The Cost of a Call: From Voice Phishing to Data Extortion. Retrieved October 22, 2025.

    Open source URL
  34. [34]
    Google Salesforce JUN 2025

    Google Threat Intelligence Group. (2025, June 4). The Cost of a Call: From Voice Phishing to Data Extortion. Retrieved October 22, 2025.

    Open source URL
  35. [35]
    Google Salesforce JUN 2025

    Google Threat Intelligence Group. (2025, June 4). The Cost of a Call: From Voice Phishing to Data Extortion. Retrieved October 22, 2025.

    Open source URL
  36. [36]
    Google Salesforce JUN 2025

    Google Threat Intelligence Group. (2025, June 4). The Cost of a Call: From Voice Phishing to Data Extortion. Retrieved October 22, 2025.

    Open source URL
  37. [37]
    Google Salesforce JUN 2025

    Google Threat Intelligence Group. (2025, June 4). The Cost of a Call: From Voice Phishing to Data Extortion. Retrieved October 22, 2025.

    Open source URL
  38. [38]
    Google Salesforce JUN 2025

    Google Threat Intelligence Group. (2025, June 4). The Cost of a Call: From Voice Phishing to Data Extortion. Retrieved October 22, 2025.

    Open source URL
  39. [39]
    Google Salesforce JUN 2025

    Google Threat Intelligence Group. (2025, June 4). The Cost of a Call: From Voice Phishing to Data Extortion. Retrieved October 22, 2025.

    Open source URL
  40. [40]
    FBI Salesforce Data Theft SEP 2025

    FBI Cyber Division. (2025, September 12). Cyber Criminal Groups UNC6040 and UNC6395 Compromising Salesforce Instances for Data Theft and Extortion. Retrieved October 22, 2025.

    Open source URL
  41. [41]
    FBI Salesforce Data Theft SEP 2025

    FBI Cyber Division. (2025, September 12). Cyber Criminal Groups UNC6040 and UNC6395 Compromising Salesforce Instances for Data Theft and Extortion. Retrieved October 22, 2025.

    Open source URL
  42. [42]
    Google Salesforce JUN 2025

    Google Threat Intelligence Group. (2025, June 4). The Cost of a Call: From Voice Phishing to Data Extortion. Retrieved October 22, 2025.

    Open source URL
  43. [43]
    Google Salesforce JUN 2025

    Google Threat Intelligence Group. (2025, June 4). The Cost of a Call: From Voice Phishing to Data Extortion. Retrieved October 22, 2025.

    Open source URL
  44. [44]
    Google Salesforce JUN 2025

    Google Threat Intelligence Group. (2025, June 4). The Cost of a Call: From Voice Phishing to Data Extortion. Retrieved October 22, 2025.

    Open source URL
  45. [45]
    Google Salesforce JUN 2025

    Google Threat Intelligence Group. (2025, June 4). The Cost of a Call: From Voice Phishing to Data Extortion. Retrieved October 22, 2025.

    Open source URL
  46. [46]
    FBI Salesforce Data Theft SEP 2025

    FBI Cyber Division. (2025, September 12). Cyber Criminal Groups UNC6040 and UNC6395 Compromising Salesforce Instances for Data Theft and Extortion. Retrieved October 22, 2025.

    Open source URL
  47. [47]
    FBI Salesforce Data Theft SEP 2025

    FBI Cyber Division. (2025, September 12). Cyber Criminal Groups UNC6040 and UNC6395 Compromising Salesforce Instances for Data Theft and Extortion. Retrieved October 22, 2025.

    Open source URL
  48. [48]
    Google Salesforce JUN 2025

    Google Threat Intelligence Group. (2025, June 4). The Cost of a Call: From Voice Phishing to Data Extortion. Retrieved October 22, 2025.

    Open source URL
  49. [49]
    Google Salesforce JUN 2025

    Google Threat Intelligence Group. (2025, June 4). The Cost of a Call: From Voice Phishing to Data Extortion. Retrieved October 22, 2025.

    Open source URL
  50. [50]
    FBI Salesforce Data Theft SEP 2025

    FBI Cyber Division. (2025, September 12). Cyber Criminal Groups UNC6040 and UNC6395 Compromising Salesforce Instances for Data Theft and Extortion. Retrieved October 22, 2025.

    Open source URL
  51. [51]
    FBI Salesforce Data Theft SEP 2025

    FBI Cyber Division. (2025, September 12). Cyber Criminal Groups UNC6040 and UNC6395 Compromising Salesforce Instances for Data Theft and Extortion. Retrieved October 22, 2025.

    Open source URL
  52. [52]
    Google Salesforce JUN 2025

    Google Threat Intelligence Group. (2025, June 4). The Cost of a Call: From Voice Phishing to Data Extortion. Retrieved October 22, 2025.

    Open source URL
  53. [53]
    Google Salesforce JUN 2025

    Google Threat Intelligence Group. (2025, June 4). The Cost of a Call: From Voice Phishing to Data Extortion. Retrieved October 22, 2025.

    Open source URL
  54. [54]
    FBI Salesforce Data Theft SEP 2025

    FBI Cyber Division. (2025, September 12). Cyber Criminal Groups UNC6040 and UNC6395 Compromising Salesforce Instances for Data Theft and Extortion. Retrieved October 22, 2025.

    Open source URL
  55. [55]
    FBI Salesforce Data Theft SEP 2025

    FBI Cyber Division. (2025, September 12). Cyber Criminal Groups UNC6040 and UNC6395 Compromising Salesforce Instances for Data Theft and Extortion. Retrieved October 22, 2025.

    Open source URL
  56. [56]
    Google Salesforce JUN 2025

    Google Threat Intelligence Group. (2025, June 4). The Cost of a Call: From Voice Phishing to Data Extortion. Retrieved October 22, 2025.

    Open source URL
  57. [57]
    Google Salesforce JUN 2025

    Google Threat Intelligence Group. (2025, June 4). The Cost of a Call: From Voice Phishing to Data Extortion. Retrieved October 22, 2025.

    Open source URL
  58. [58]
    FBI Salesforce Data Theft SEP 2025

    FBI Cyber Division. (2025, September 12). Cyber Criminal Groups UNC6040 and UNC6395 Compromising Salesforce Instances for Data Theft and Extortion. Retrieved October 22, 2025.

    Open source URL
  59. [59]
    Google Salesforce JUN 2025

    Google Threat Intelligence Group. (2025, June 4). The Cost of a Call: From Voice Phishing to Data Extortion. Retrieved October 22, 2025.

    Open source URL
  60. [60]
    Google Salesforce JUN 2025

    Google Threat Intelligence Group. (2025, June 4). The Cost of a Call: From Voice Phishing to Data Extortion. Retrieved October 22, 2025.

    Open source URL
Source and licensing

Source: MITRE ATT&CK®. © 2026 The MITRE Corporation. This work is reproduced and distributed with the permission of The MITRE Corporation. MITRE ATT&CK and ATT&CK are registered trademarks of The MITRE Corporation. Glexia is not affiliated with or endorsed by MITRE.