T1683.002: Audio-Visual Content
Adversaries may create or manipulate audio, image, and video content to support targeting and malicious operations. Adversaries may also use synthetic voice recordings, real-time altered audio or video during live interactions, fabricated profile photos and identity documents, or video content depicting fabricated or impersonated individuals.[1]
Content may be produced manually through editing tools, generated using AI-assisted tools, or produced using third-party synthetic services.[2][3] AI-assisted tools have enabled adversaries to produce synthetic media at scale and generate content that is more difficult to identify as inauthentic.
Audio-visual content produced through these methods may be used in support of other techniques, such as Phishing, Spearphishing via Service, Phishing for Information, Internal Spearphishing, Social Engineering, Financial Theft, or Establish Accounts.
Analyst context for executives and security teams
Audio-Visual Content is a pre-compromise resource-development behavior: adversaries may create or manipulate images, audio, video, profile photos, identity documents, or live audio/video to make later targeting, phishing, social engineering, fraud, or account-establishment efforts more believable. For leaders, the risk is not the media file itself; it is that trust-based business processes can be pressured by realistic synthetic or edited content before malware or a conventional intrusion is visible.
Executive priority
Treat this as a readiness issue for high-trust workflows: executive approvals, finance requests, recruiting, help desk identity verification, account creation, and external communications. Because ATT&CK provides no official detection text for this sub-technique, priority should be on proving that teams have verification procedures, escalation paths, and evidence collection for suspicious audio, image, and video-enabled interactions. This supports incident decision-making, fraud prevention, social-engineering resilience, and audit evidence around pre-compromise controls.
Technical view
This sub-technique is in the PRE platform and Resource Development tactic, so SOC coverage will often depend on process telemetry and human-reported signals rather than endpoint alerts. Detection engineering should validate what can be observed around media-backed interactions that lead into related ATT&CK behaviors such as Phishing, Spearphishing via Service, Phishing for Information, Internal Spearphishing, Social Engineering, Financial Theft, and Establish Accounts. The relationship to DET0918 indicates a detection strategy exists, but the supplied object includes no detection details; teams should therefore document local analytic assumptions and avoid claiming automated coverage without testing.
Likely telemetry
- User reports of suspicious calls, video meetings, images, documents, profiles, or identity claims
- Email, messaging, collaboration, and meeting metadata associated with media-based requests
- Help desk, HR, recruiting, finance, and account-registration case records tied to identity verification or approval decisions
- Attachments, URLs, file metadata, and message content where audio, image, or video artifacts are submitted or linked
- Logs or records for new account creation, profile changes, and verification attempts when media artifacts are part of the workflow
Detection direction
- Inventory where audio, image, or video content can influence approvals, identity proofing, payment, hiring, or access decisions.
- Create triage paths for suspicious media-supported requests, especially when they involve urgency, identity claims, credential requests, financial action, or account creation.
- Tune detections and case routing around the downstream behaviors named by ATT&CK, including phishing, social engineering, financial theft, and establishing accounts.
- Account for false positives: legitimate edited media, accessibility tools, marketing content, remote interviews, and normal video conferencing artifacts can resemble suspicious content without malicious context.
- Because the object has no official detection text, require validation through tabletop exercises, red-team/social-engineering simulations where appropriate, and review of actual reporting and escalation records.
Mitigation priorities
- Prioritize pre-compromise controls consistent with M1056: reduce exposed information that enables impersonation and make adversarial preparation harder.
- Require out-of-band verification for high-risk requests involving money movement, credential disclosure, account creation, sensitive data, or executive approval.
- Harden help desk, finance, HR, recruiting, and account-registration procedures so audio-visual content alone is not sufficient proof of identity or authority.
- Train users and frontline teams to report suspicious synthetic or manipulated media without needing to prove it is fake.
- Preserve evidence and escalation records so incident response can connect media-backed pre-compromise activity to later phishing, social engineering, or fraud attempts.
Analyst notes and limits
ATT&CK lists this as a sub-technique of Generate Content and relates it to APT-C-36 and Contagious Interview use. Those relationships should be treated as ATT&CK context, not as evidence that those groups are active in a specific environment. The most useful local question is whether business processes can resist convincing media-backed impersonation before technical compromise occurs.
The supplied ATT&CK object provides no official detection guidance and lists the platform as PRE, which limits direct host, network, or cloud telemetry assumptions. Any claims of coverage require local evidence from communications platforms, workflow systems, reporting channels, and incident records.
Audio-Visual Content
Adversaries may create or manipulate audio, image, and video content to support targeting and malicious operations. Adversaries may also use synthetic voice recordings, real-time altered audio or video during live interactions, fabricated profile photos and identity documents, or video content depicting fabricated or impersonated individuals.[1]
Content may be produced manually through editing tools, generated using AI-assisted tools, or produced using third-party synthetic services.[2][3] AI-assisted tools have enabled adversaries to produce synthetic media at scale and generate content that is more difficult to identify as inauthentic.
Audio-visual content produced through these methods may be used in support of other techniques, such as Phishing, Spearphishing via Service, Phishing for Information, Internal Spearphishing, Social Engineering, Financial Theft, or Establish Accounts.
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 | T1683 | Generate Content | This object subtechnique of Generate Content. |
Groups, software, and campaigns
G0099: APT-C-36
APT-C-36 is a suspected South American threat group that has engaged in espionage and financially motivated operations since at least 2018. APT-C-36 has targeted government institutions and entities in the financial, energy, and professional manufacturing sectors across Colombia and other Latin American countries.[1][2][3][4]
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]
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.0 | Current bundle | 909a2f285f3e… |
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]
Nov AI Threat Tracker
Google Threat Intelligence Group. (2025, November 5). GTIG AI Threat Tracker: Advances in Threat Actor Usage of AI Tools. Retrieved March 31, 2026.
Open source URL -
[2]
FBI 2025 AI Generate Content
Internet Crime Complaint Center, FBI. (2025). Federal Bureau of Investigation Internet Crime Report, 2025. Retrieved April 17, 2026.
Open source URL -
[3]
Europol Deepfakes
Europol. (2022). FACING REALITY? LAW ENFORCEMENT AND THE CHALLENGE OF DEEPFAKES. Retrieved April 17, 2026.
Open source URL -
[4]
mitre-attack T1683.002Open 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.