Has gathered audio during a Zoom session.1
Audio Capture T1123
- Tactic
- Collection
- Platforms
- Linux, macOS, Windows
- Version
- 1.0
- Created
- 31 May 2017
- Last modified
- 12 May 2026
An adversary can leverage a computer's peripheral devices (e.g., microphones and webcams) or applications (e.g., voice and video call services) to capture audio recordings for the purpose of listening into sensitive conversations to gather information.[1]
Audio Capture MITRE reference T1123
2 groups have been recorded using this technique. Newest first; each entry carries MITRE’s procedure text and a link to the group’s full record. Click a name to filter the rules below.
Has used an audio capturing utility known as SOUNDWAVE that captures microphone input.1
All 2 groups for this technique
30 software entries are documented implementing this technique. MITRE files each as a tool or as malware; newest first, then by how many groups carry them.
Uses Apple's built-in AVFoundation Framework library to capture and manage audio recordings then transform them to JSON blobs for exfiltration.1
Can capture input and output audio streams from infected devices.12
Can load a module to leverage the LAME encoder and mciSendStringW to control and capture audio.1
Has the ability to record audio.1
Has the ability to capture VoiceIP application audio on an infected host.1
Has the ability to record audio from the compromised host.1
All 30 software entries for this technique · 6 newest in this preview
Offense vs defense T1123
Is defensive coverage keeping up with adversary use? Eight counts, each ranked against all 697 ATT&CK techniques. Attack sits left, defense right, so a shape leaning left means adversaries are better documented here than defenders are equipped. Hover any spoke for its percentile and the share of techniques that have more. The timeline below shows when each side arrived.
How it got here
Adversary activity (campaign spans) over cumulative rule output. Each source is plotted independently from zero, so neither line includes the other. Campaign dates are year-granularity.
Audio Capture detection strategy DET0221
MITRE names one behaviour worth catching for this technique and breaks it into 3 analytics, one per platform. Each carries the log sources it needs and the fields you tune per environment.
Behavioral Detection Strategy for T1123 Audio Capture Across Windows, Linux, macOS
AN0619 · Windows
Unusual or unauthorized processes accessing microphone APIs (e.g., winmm.dll, avrt.dll) followed by audio file writes to user-accessible or temp directories.
Log sources
The data this analytic draws on. You do not need every component — each one you already collect covers part of it. Each links to its ATT&CK record.
| Data component | Name | Channel |
|---|---|---|
| Process CreationDC0032 | WinEventLog:Security | EventCode=4688 |
| Process AccessDC0035 | WinEventLog:Sysmon | EventCode=10 |
| File CreationDC0039 | WinEventLog:Sysmon | EventCode=11 |
Tunable fields
MITRE calls these the analytic’s mutable elements: the thresholds and filters you set for your own environment.
| Field | What you tune |
|---|---|
| TimeWindow | Time span in which the process accesses audio APIs and writes files, to reduce false positives. |
| TargetProcess | Set of approved processes known to legitimately use microphone (e.g., Zoom, Teams). |
| WriteDirectory | Allowlist of paths where legitimate apps store audio (e.g., user media folders). |
AN0620 · Linux
Processes accessing ALSA/PulseAudio devices or executing audio capture binaries like 'arecord', followed by file creation or suspicious child process spawning.
Log sources
The data this analytic draws on. You do not need every component — each one you already collect covers part of it. Each links to its ATT&CK record.
| Data component | Name | Channel |
|---|---|---|
| Process CreationDC0032 | linux:Sysmon | EventCode=1 |
| File CreationDC0039 | auditd:SYSCALL | write |
| File AccessDC0055 | auditd:SYSCALL | open |
Tunable fields
MITRE calls these the analytic’s mutable elements: the thresholds and filters you set for your own environment.
| Field | What you tune |
|---|---|
| ExecutableName | Capture binaries like arecord, parecord, or ffmpeg. |
| DevicePath | Log attempts to access /dev/snd/*, /dev/dsp, /proc/asound/*. |
| UserContext | Whether the user has audio access rights or is running under elevated privileges. |
AN0621 · macOS
Processes invoking AVFoundation or CoreAudio frameworks, accessing input devices via TCC logs or Unified Logs, followed by writing AIFF/WAV/MP3 files to disk.
Log sources
The data this analytic draws on. You do not need every component — each one you already collect covers part of it. Each links to its ATT&CK record.
| Data component | Name | Channel |
|---|---|---|
| OS API ExecutionDC0021 | macos:unifiedlog | audio APIs |
| Process AccessDC0035 | Apple TCC Logs | Microphone Access Events |
| File CreationDC0039 | fs:fsusage | File IO |
Tunable fields
MITRE calls these the analytic’s mutable elements: the thresholds and filters you set for your own environment.
| Field | What you tune |
|---|---|
| FrameworkCall | CoreAudio vs. AVFoundation vs. lower-level device access APIs. |
| TargetDirectory | Suspicious file drops (e.g., ~/Library/Caches/, /tmp/, nonstandard user folders). |
| AnomalousParent | Unexpected parent-child relationship between non-media apps and AV capture. |
| # | Test | Platform | Executor | Elevation | Prereqs | Cleanup | Ref | |||||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| 01 | using device audio capture commandlet | windows | PowerShell | — | 1 | — | ||||||||||||||||||
Uses AudioDeviceCmdlets to set the default recording device and simulate audio capture. Module repo: AudioDeviceCmdlets Attack command $mic = Get-AudioDevice -Recording Set-AudioDevice -ID $mic.ID Start-Sleep -Seconds 5 Prerequisite AudioDeviceCmdlets module must be installed Check if (Get-Module -ListAvailable -Name AudioDeviceCmdlets) { exit 0 } else { exit 1 }
Satisfy Install with: Install-Module -Name AudioDeviceCmdlets -Force" GUID53dcbff4-901f-40e7-a1c6-9f533c1ee2f0 | ||||||||||||||||||||||||
| 02 | Registry artefact when application use microphone | windows | cmd | — | — | Yes | ||||||||||||||||||
can-you-track-processes-accessing-the-camera-and-microphone Attack command reg add HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\CapabilityAccessManager\ConsentStore\microphone\NonPackaged\C:#Windows#Temp#atomic.exe /v LastUsedTimeStart /t REG_BINARY /d a273b6f07104d601 /f reg add HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\CapabilityAccessManager\ConsentStore\microphone\NonPackaged\C:#Windows#Temp#atomic.exe /v LastUsedTimeStop /t REG_BINARY /d 96ef514b7204d601 /f Cleanup command reg DELETE HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\CapabilityAccessManager\ConsentStore\microphone\NonPackaged\C:#Windows#Temp#atomic.exe /f GUID2c6a175f-26f3-4d8b-9e18-3b8a2d08d23c | ||||||||||||||||||||||||
| 03 | using Quicktime Player | macos | sh | — | — | Yes | ||||||||||||||||||
Use AppleScript to get Quicktime Player to record an audio file from the default microphone. Should create a non-empty m4a file with sound from the microphone. - requires Automation permissions but no additional microphone permissions - saves file in /tmp by default. Other locations likely to require more permissions. Input arguments
Attack command sh #{filename} #{audiofile} #{duration}
Cleanup command if test -w #{audiofile}; then
rm #{audiofile}
fi
GUID1cf9a241-3136-4358-859f-94a7b174207b | ||||||||||||||||||||||||
Tests from Atomic Red Team (MIT licence) · technique definition