T1567: Exfiltration Over Web Service
Adversaries may use an existing, legitimate external Web service to exfiltrate data rather than their primary command and control channel. Popular Web services acting as an exfiltration mechanism may give a significant amount of cover due to the likelihood that hosts within a network are already communicating with them prior to compromise. Firewall rules may also already exist to permit traffic to these services.
Web service providers also commonly use SSL/TLS encryption, giving adversaries an added level of protection.
Analyst context for executives and security teams
Exfiltration over a web service matters because it blends data theft into traffic many organizations already allow: SaaS, office platforms, code repositories, cloud storage, text storage sites, and other legitimate external web services. The business issue is not only malware traffic; it is whether the organization can distinguish approved use of trusted services from unauthorized movement of sensitive data over HTTPS.
Executive priority
Prioritize this technique where sensitive data, SaaS usage, developer tooling, or cloud storage are material to operations. Leaders should ask whether web egress, DLP, and SaaS audit evidence can prove what data left, which account or host sent it, and whether the destination service was authorized. This is especially relevant for incident response readiness, compliance evidence around data handling, and control decisions about web filtering and DLP scope.
Technical view
T1567 is an enterprise exfiltration technique across ESXi, Linux, macOS, Office Suite, SaaS, and Windows. ATT&CK provides no official detection text, but a related detection strategy, DET0548, exists and should be reviewed for coverage design. SOC and detection teams should validate monitoring for outbound transfers to legitimate web services, with special attention to the sub-technique context: code repositories, cloud storage, and text storage sites. Because SSL/TLS is common, detections should not depend solely on payload inspection; they should correlate destination reputation/category, user or host identity, volume, timing, process or application context, and DLP findings where available.
Likely telemetry
- Web proxy and secure web gateway logs, including URL/category, destination domain, method, bytes sent, user, and device context
- Firewall and network egress logs showing outbound connections to external web services
- DNS logs and TLS metadata such as SNI/certificate context where collected
- Endpoint network connection telemetry from Windows, Linux, macOS, and ESXi where supported
- SaaS and Office Suite audit logs for file access, sharing, exports, uploads, and unusual account activity
Detection direction
- Baseline approved web service usage by business unit, user role, host type, and workload so anomalous uploads are not lost in normal SaaS traffic.
- Tune for large or unusual outbound transfers to legitimate services, especially when the host, user, time, destination category, or application context is atypical.
- Correlate web egress with identity and SaaS audit events; web traffic alone may show the destination but not the business legitimacy of the transfer.
- Account for HTTPS blind spots. If payload inspection is unavailable or inappropriate, rely more heavily on metadata, DLP classification, destination governance, and behavioral baselines.
- Separate sanctioned from unsanctioned use of code repositories, cloud storage, and text storage sites to reduce false positives while preserving visibility into risky channels.
Mitigation priorities
- Start by defining which external web services are authorized for business use and which users, devices, and workloads may access them.
- Apply M1021 Restrict Web-Based Content through web filtering, category controls, download/upload governance, script or extension controls where appropriate, and policy enforcement for unauthorized services.
- Apply M1057 Data Loss Prevention to identify, classify, monitor, and control movement of sensitive data across endpoint, network, SaaS, and cloud paths.
- Ensure SaaS, Office Suite, code repository, and cloud storage audit logging is enabled and retained long enough to support incident response and compliance evidence.
- Review exception handling: broad allow rules for popular web services can become exfiltration blind spots if not paired with logging, identity context, and DLP or behavioral monitoring.
Analyst notes and limits
The supplied ATT&CK relationships show this technique is used by multiple campaigns, groups, and software entries, and it has sub-techniques for code repositories, cloud storage, and text storage sites. Those relationships support prioritizing coverage across legitimate web services, but local risk depends on the organization’s sanctioned services, data sensitivity, egress architecture, and logging maturity.
MITRE provides no official detection text for this object in the supplied fields. The related DET0548 detection strategy is named but not described here, so specific analytic logic should be validated from that source and local telemetry. This take does not assert active exploitation, local exposure, attribution, or guaranteed detection coverage.
Exfiltration Over Web Service
Adversaries may use an existing, legitimate external Web service to exfiltrate data rather than their primary command and control channel. Popular Web services acting as an exfiltration mechanism may give a significant amount of cover due to the likelihood that hosts within a network are already communicating with them prior to compromise. Firewall rules may also already exist to permit traffic to these services.
Web service providers also commonly use SSL/TLS encryption, giving adversaries an added level of protection.
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.
Related techniques
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.
| Domain | ID | Name | Relationship / procedure |
|---|---|---|---|
| Enterprise | T1567.001 | Exfiltration to Code Repository Sub-technique | Exfiltration to Code Repository subtechnique of this object. |
| Enterprise | T1567.003 | Exfiltration to Text Storage Sites Sub-technique | Exfiltration to Text Storage Sites subtechnique of this object. |
| Enterprise | T1567.002 | Exfiltration to Cloud Storage Sub-technique | Exfiltration to Cloud Storage subtechnique of this object. |
| Enterprise | T1567.004 | Exfiltration Over Webhook Sub-technique | Exfiltration Over Webhook subtechnique of this object. |
Groups, software, and campaigns
G0059: Magic Hound
Magic Hound is an Iranian-sponsored threat group that conducts long term, resource-intensive cyber espionage operations, likely on behalf of the Islamic Revolutionary Guard Corps. They have targeted European, U.S., and Middle Eastern government and military personnel, academics, journalists, and organizations such as the World Health Organization (WHO), via complex social engineering campaigns since at least 2014.[1][2][3][4][5]
G1052: Contagious Interview
Contagious Interview is a North Korea–aligned threat group active since 2023. The group conducts both cyberespionage and financially motivated operations, including the theft of cryptocurrency and user credentials. Contagious Interview targets Windows, Linux, and macOS systems, with a particular focus on individuals engaged in software development and cryptocurrency-related activities. [1][2][3][4][5][6][7][8]
G0007: APT28
APT28 is a threat group that has been attributed to Russia's General Staff Main Intelligence Directorate (GRU) 85th Main Special Service Center (GTsSS) military unit 26165.[1][2] This group has been active since at least 2004.[3][4][5][6][7][8][9][10][11][12][13]
APT28 reportedly compromised the Hillary Clinton campaign, the Democratic National Committee, and the Democratic Congressional Campaign Committee in 2016 in an attempt to interfere with the U.S. presidential election.[5] In 2018, the US indicted five GRU Unit 26165 officers associated with APT28 for cyber operations (including close-access operations) conducted between 2014 and 2018 against the World Anti-Doping Agency (WADA), the US Anti-Doping Agency, a US nuclear facility, the Organization for the Prohibition of Chemical Weapons (OPCW), the Spiez Swiss Chemicals Laboratory, and other organizations.[14] Some of these were conducted with the assistance of GRU Unit 74455, which is also referred to as Sandworm Team.
G1043: BlackByte
BlackByte is a ransomware threat actor operating since at least 2021. BlackByte is associated with several versions of ransomware also labeled BlackByte Ransomware. BlackByte ransomware operations initially used a common encryption key allowing for the development of a universal decryptor, but subsequent versions such as BlackByte 2.0 Ransomware use more robust encryption mechanisms. BlackByte is notable for operations targeting critical infrastructure entities among other targets across North America.[1][2][3][4][5]
S1171: OilCheck
S0547: DropBook
S0622: AppleSeed
S0508: ngrok
S1168: SampleCheck5000
SampleCheck5000 is a downloader with multiple variants that was used by OilRig including during the Outer Space campaign to download and execute additional payloads. [1][2]
S1179: Exbyte
S1245: InvisibleFerret
InvisibleFerret is a modular python malware that is leveraged for data exfiltration and remote access capabilities.[1][2][3] InvisibleFerret consists of four modules: main, payload, browser, and AnyDesk.[1] InvisibleFerret malware has been leveraged by North Korea-affiliated threat actors identified as DeceptiveDevelopment or Contagious Interview since 2023.[4][2][3][5] InvisibleFerret has historically been introduced to the victim environment through the use of the BeaverTail malware.[6][1][2][3][5]
C0051: APT28 Nearest Neighbor Campaign
APT28 Nearest Neighbor Campaign was conducted by APT28 from early February 2022 to November 2024 against organizations and individuals with expertise on Ukraine. APT28 primarily leveraged living-off-the-land techniques, while leveraging the zero-day exploitation of CVE-2022-38028. Notably, APT28 leveraged Wi-Fi networks in close proximity to the intended target to gain initial access to the victim environment. By daisy-chaining multiple compromised organizations nearby the intended target, APT28 discovered dual-homed systems (with both a wired and wireless network connection) to enable Wi-Fi and use compromised credentials to connect to the victim network.[1]
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]
C0062: Anthropic AI-orchestrated Campaign
The Anthropic AI-orchestrated Campaign was conducted in September 2025 by a likely China nexus espionage actor identified as GTG-1002. The Anthropic AI-orchestrated Campaign was a highly coordinated operation that manipulated Claude Code to perform reconnaissance, vulnerability discovery, exploitation, lateral movement, credential harvesting, data analysis, and exfiltration operations at approximately 30 entities in the technology, financial, chemical, and government sectors. During the Anthropic AI-orchestrated Campaign, human operators used Claude Code agents and Model Context Protocol (MCP) tools to automate cyber operations. Operators broke attacks into discrete tasks, used crafted prompts, and established personas to bypass AI guardrails, enabling the agents to execute the operations with minimal human involvement.[1][2]
C0017: C0017
C0017 was an APT41 campaign conducted between May 2021 and February 2022 that successfully compromised at least six U.S. state government networks through the exploitation of vulnerable Internet facing web applications. During C0017, APT41 was quick to adapt and use publicly-disclosed as well as zero-day vulnerabilities for initial access, and in at least two cases re-compromised victims following remediation efforts. The goals of C0017 are unknown, however APT41 was observed exfiltrating Personal Identifiable Information (PII).[1]
All related ATT&CK context
Mitigation direction
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 .
Imported snapshots across ATT&CK releases (1)
| Release | Bundle imported | Object version | Modified | Status | Raw hash |
|---|---|---|---|---|---|
| 19.1 | 1.5 | Current bundle | 0f09e6e28004… |
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.
External references and citations
MITRE external references are preserved separately from Glexia analysis so citations remain traceable to their original source records.
-
[1]
mitre-attack T1567Open source URL
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.