Skip to main content
MuonPartners
Services
Architecture

Solution design and technology roadmapping

Solution AssessmentTechnology RoadmapsIntegration DesignSolution ArchitectureTechnical Design
Cyber Security

Security assessments, IAM, and compliance

AssessmentsIAMComplianceSecurity BaselineCyber Innovation
Network and Platform

Network architecture and cloud platforms

Network DesignCloud StrategyModernisation
Enterprise Architecture

Business-technology alignment

Business AlignmentPortfolio AnalysisGovernance
View all services
ProjectsCase StudiesInsightsToolsAbout
Contact Us

Services

Architecture
Solution AssessmentTechnology RoadmapsIntegration DesignSolution ArchitectureTechnical Design
Cyber Security
AssessmentsIAMComplianceSecurity BaselineCyber Innovation
Network and Platform
Network DesignCloud StrategyModernisation
Enterprise Architecture
Business AlignmentPortfolio AnalysisGovernance
ProjectsCase StudiesInsightsToolsAboutContact
Get in Touch
MuonPartners

Strategic technology consulting for Australian organisations navigating complexity.

Services

  • Architecture
  • Cyber Security
  • Network and Platform
  • Enterprise Architecture

Company

  • About
  • Products
  • Frameworks
  • Cross-Framework Mapping
  • Projects
  • Case Studies
  • Insights
  • Contact

Contact

  • [email protected]
  • Australia
  • LinkedIn

© 2026 Muon Partners. All rights reserved.

ABN 50 669 022 315 · A Muon Group company.

Privacy PolicyTerms of Service
  1. Frameworks
  2. >ATTACK
  3. >Execution
  4. >ATTACK-T1559.003
ATTACK-T1559.003Active

XPC Services

Statement

Adversaries can provide malicious content to an XPC service daemon for local code execution. macOS uses XPC services for basic inter-process communication between various processes, such as between the XPC Service daemon and third-party application privileged helper tools. Applications can send messages to the XPC Service daemon, which runs as root, using the low-level XPC Service <code>C API</code> or the high level <code>NSXPCConnection API</code> in order to handle tasks that require elevated privileges (such as network connections). Applications are responsible for providing the protocol definition which serves as a blueprint of the XPC services. Developers typically use XPC Services to provide applications stability and privilege separation between the application client and the daemon.(Citation: creatingXPCservices)(Citation: Designing Daemons Apple Dev)

Adversaries can abuse XPC services to execute malicious content. Requests for malicious execution can be passed through the application's XPC Services handler.(Citation: CVMServer Vuln)(Citation: Learn XPC Exploitation) This may also include identifying and abusing improper XPC client validation and/or poor sanitization of input parameters to conduct Exploitation for Privilege Escalation.

Location

Tactic
Execution

Technique Details

Identifier
ATTACK-T1559.003
Parent Technique
ATTACK-T1559
ATT&CK Page
View on MITRE

Tactics

Execution

Platforms

macOS

Detection

Detect Abuse of XPC Services (T1559.003)

Mitigations

Application Developer Guidance: Application Developer Guidance focuses on providing developers with the knowledge, tools, and best practices needed to write secure code, reduce vulnerabilities, and implement secure design principles. By integrating security throughout the software development lifecycle (SDLC), this mitigation aims to prevent the introduction of exploitable weaknesses in applications, systems, and APIs. This mitigation can be implemented through the following measures:

Preventing SQL Injection (Secure Coding Practice):

  • Implementation: Train developers to use parameterized queries or prepared statements instead of directly embedding user input into SQL queries.
  • Use Case: A web application accepts user input to search a database. By sanitizing and validating user inputs, developers can prevent attackers from injecting malicious SQL commands.

Cross-Site Scripting (XSS) Mitigation:

  • Implementation: Require developers to implement output encoding for all user-generated content displayed on a web page.
  • Use Case: An e-commerce site allows users to leave product reviews. Properly encoding and escaping user inputs prevents malicious scripts from being executed in other users’ browsers.

Secure API Design:

  • Implementation: Train developers to authenticate all API endpoints and avoid exposing sensitive information in API responses.
  • Use Case: A mobile banking application uses APIs for account management. By enforcing token-based authentication for every API call, developers reduce the risk of unauthorized access.

Static Code Analysis in the Build Pipeline:

  • Implementation: Incorporate tools into CI/CD pipelines to automatically scan for vulnerabilities during the build process.
  • Use Case: A fintech company integrates static analysis tools to detect hardcoded credentials in their source code before deployment.

Threat Modeling in the Design Phase:

  • Implementation: Use frameworks like STRIDE (Spoofing, Tampering, Repudiation, Information Disclosure, Denial of Service, Elevation of Privilege) to assess threats during application design.
  • Use Case: Before launching a customer portal, a SaaS company identifies potential abuse cases, such as session hijacking, and designs mitigations like secure session management.

Tools for Implementation:

  • Static Code Analysis Tools: Use tools that can scan for known vulnerabilities in source code.
  • Dynamic Application Security Testing (DAST): Use tools like Burp Suite or OWASP ZAP to simulate runtime attacks and identify vulnerabilities.
  • Secure Frameworks: Recommend secure-by-default frameworks (e.g., Django for Python, Spring Security for Java) that enforce security best practices.
SP 800-53
SP800-53-CM-5relatedvia ctid-attack-to-sp800-53
SP800-53-CM-6relatedvia ctid-attack-to-sp800-53
SP800-53-CM-7relatedvia ctid-attack-to-sp800-53
SP800-53-SA-10relatedvia ctid-attack-to-sp800-53
SP800-53-SA-11relatedvia ctid-attack-to-sp800-53
View in graphReport an issue
← Back to Execution
Execution45 controls
ATTACK-T1047Windows Management InstrumentationATTACK-T1053Scheduled Task/JobATTACK-T1053.002AtATTACK-T1053.003CronATTACK-T1053.005Scheduled TaskATTACK-T1053.006Systemd TimersATTACK-T1053.007Container Orchestration JobATTACK-T1059Command and Scripting InterpreterATTACK-T1059.001PowerShellATTACK-T1059.002AppleScriptATTACK-T1059.003Windows Command ShellATTACK-T1059.004Unix ShellATTACK-T1059.005Visual BasicATTACK-T1059.006PythonATTACK-T1059.007JavaScriptATTACK-T1059.008Network Device CLIATTACK-T1059.009Cloud APIATTACK-T1059.010AutoHotKey & AutoITATTACK-T1059.011LuaATTACK-T1059.012Hypervisor CLIATTACK-T1059.013Container CLI/APIATTACK-T1072Software Deployment ToolsATTACK-T1106Native APIATTACK-T1129Shared ModulesATTACK-T1203Exploitation for Client ExecutionATTACK-T1204User ExecutionATTACK-T1204.001Malicious LinkATTACK-T1204.002Malicious FileATTACK-T1204.003Malicious ImageATTACK-T1204.004Malicious Copy and PasteATTACK-T1204.005Malicious LibraryATTACK-T1559Inter-Process CommunicationATTACK-T1559.001Component Object ModelATTACK-T1559.002Dynamic Data ExchangeATTACK-T1559.003XPC ServicesATTACK-T1569System ServicesATTACK-T1569.001LaunchctlATTACK-T1569.002Service ExecutionATTACK-T1569.003SystemctlATTACK-T1609Container Administration CommandATTACK-T1648Serverless ExecutionATTACK-T1651Cloud Administration CommandATTACK-T1674Input InjectionATTACK-T1675ESXi Administration CommandATTACK-T1677Poisoned Pipeline Execution