Attack Mob T1616 Call Control

MITRE ATT&CK T1616: Call Control

When to use this skill

Use this skill when the task involves T1616, Call Control, mobile ATT&CK, TTP mapping, detection engineering, hunting, incident-response enrichment, control validation, or authorized adversary-emulation planning. Treat it as a defensive analysis aid: keep outputs focused on understanding, detecting, mitigating, and safely validating this ATT&CK technique.

Technique context

• ATT&CK domain: mobile
• ATT&CK ID: T1616
• Technique name: Call Control
• Type: technique
• ATT&CK URL: https://attack.mitre.org/techniques/T1616
• Tactics: collection, command-and-control, impact
• Platforms: Android
• Required permissions: Not specified
• Effective permissions: Not specified
• Defenses bypassed: Not specified

ATT&CK description

Adversaries may make, forward, or block phone calls without user authorization. This could be used for adversary goals such as audio surveillance, blocking or forwarding calls from the device owner, or C2 communication.

Several permissions may be used to programmatically control phone calls, including:

• ANSWER_PHONE_CALLS - Allows the application to answer incoming phone calls(Citation: Android Permissions)
• CALL_PHONE - Allows the application to initiate a phone call without going through the Dialer interface(Citation: Android Permissions)
• PROCESS_OUTGOING_CALLS - Allows the application to see the number being dialed during an outgoing call with the option to redirect the call to a different number or abort the call altogether(Citation: Android Permissions)
• MANAGE_OWN_CALLS - Allows a calling application which manages its own calls through the self-managed ConnectionService APIs(Citation: Android Permissions)
• BIND_TELECOM_CONNECTION_SERVICE - Required permission when using a ConnectionService(Citation: Android Permissions)
• WRITE_CALL_LOG - Allows an application to write to the device call log, potentially to hide malicious phone calls(Citation: Android Permissions)

When granted some of these permissions, an application can make a phone call without opening the dialer first. However, if an application desires to simply redirect the user to the dialer with a phone number filled in, it can launch an Intent using Intent.ACTION_DIAL, which requires no specific permissions. This then requires the user to explicitly initiate the call or use some form of Input Injection to programmatically initiate it.

Agent workflow

1. Clarify scope: identify the system, asset class, log sources, cloud or endpoint platform, and whether the user wants triage, detection, coverage assessment, or safe emulation planning.
2. Load bundled resources as needed: use references/technique-profile.json for structured metadata, references/detection-and-mitigation.md for triage and telemetry guidance, references/known-threat-context.md for ATT&CK relationship context, and templates/ for repeatable outputs.
3. Map observations to ATT&CK: compare the user's evidence to the ATT&CK description, tactics, platforms, and known procedure patterns before asserting a match.
4. Produce defensive outputs: prioritize hypotheses, telemetry requirements, detection logic ideas, validation steps, containment guidance, and mitigations.
5. Preserve uncertainty: distinguish confirmed evidence, plausible indicators, assumptions, and gaps. Recommend what to collect next.
6. Stay safe: do not provide malware, credential theft, persistence, evasion, destructive automation, or unauthorized exploitation instructions. For adversary emulation, keep steps bounded to approved lab or control-validation contexts and omit operational abuse details.

Bundled resources

• references/technique-profile.json: machine-readable ATT&CK metadata for this technique.
• references/detection-and-mitigation.md: detection notes, telemetry checklist, triage questions, mitigation candidates, and false-positive considerations.
• references/known-threat-context.md: ATT&CK relationship context with attribution cautions.
• templates/detection-brief.md: detection engineering brief template.
• templates/hunt-plan.md: threat hunt plan template.
• templates/incident-response-note.md: incident response note template.
• templates/coverage-assessment.md: ATT&CK coverage assessment template.
• scripts/render_brief.py: local helper that renders a Markdown defensive brief from technique-profile.json.
• assets/output-schema.json: JSON schema for structured technique analysis outputs.

To generate a quick brief, run python scripts/render_brief.py --output brief.md from inside this skill directory, or adapt the templates directly.

Detection guidance

No ATT&CK detection guidance was present in the source STIX object.

Useful telemetry and data sources

• Not specified in the STIX object.

Mitigations to consider

• User Guidance

Known threat context

Use these examples only as contextual leads, not as proof that an observed event is this technique:

• AndroRAT (malware)
• Android/SpyAgent (malware)
• Anubis (malware)
• BRATA (malware)
• BusyGasper (malware)
• CarbonSteal (malware)
• Chameleon (malware)
• Crocodilus (malware)
• DocSwap (malware)
• Drinik (malware)
• Escobar (malware)
• Fakecalls (malware)
• GodFather (malware)
• Monokle (malware)
• SpyC23 (malware)
• TangleBot (malware)
• VajraSpy (malware)

Recommended output pattern

When responding with this skill, structure the answer as:

• Assessment: whether the evidence supports this ATT&CK mapping and why.
• Evidence: specific indicators, logs, behaviors, and assumptions.
• Detection: telemetry sources, analytic logic, and tuning considerations.
• Response: containment, eradication, recovery, and validation actions.
• Coverage gaps: missing logs, sensors, controls, or environmental details.
• References: include the ATT&CK URL and any user-provided evidence references.

ATT&CK contributors

• Gaetan van Diemen, ThreatFabric