---
title: "3CX supply-chain compromise"
description: "What the retained public evidence establishes about the 3CX incident, its attack path, impact, and response."
incident_type: "Cybersecurity incident"
status: "active"
last_modified: "2026-09-19"
canonical_url: "https://www.ally.security/incidents/3cx-supply-chain-compromise-2023"
markdown_url: "https://www.ally.security/incidents/3cx-supply-chain-compromise-2023.md"
stix_url: "https://www.ally.security/incidents/3cx-supply-chain-compromise-2023/stix.json"
---

# 3CX supply-chain compromise

North Korean-linked (Lazarus/UNC4736); trojanized desktop app. Notable "double supply chain" attack — 3CX itself was compromised via an earlier trojanized trading app.

Last modified Sep 19, 2026 · 1 source

## Summary

- **Environment:** VoIP software supply chain
- **Operational impact:** Notable "double supply chain" attack — 3CX itself was compromised via an earlier trojanized trading app
- **Financial impact:** No financial figure is established by the reviewed source evidence

## What happened

In 2023, 3CX experienced an incident in its voip software supply chain environment. The retained source describes the attack path as follows: North Korean-linked (Lazarus/UNC4736); trojanized desktop app. [1](#source-1)

The documented consequence was: Notable "double supply chain" attack — 3CX itself was compromised via an earlier trojanized trading app. [1](#source-1)

## Impact

- Documented impact: Notable "double supply chain" attack — 3CX itself was compromised via an earlier trojanized trading app. [1](#source-1)
- No financial loss, ransom amount, recovery cost, or regulatory penalty is established by the reviewed source evidence.

## Timeline

### April 20, 2023 — Documented public update

The [3CX software supply chain compromise](https://cloud.google.com/blog/topics/threat-intelligence/3cx-software-supply-chain-compromise) records the incident facts used in this briefing. [1](#source-1)

### September 19, 2026 — Briefing updated

This briefing was last reviewed and updated on September 19, 2026.

## Threat Group & Attack Vector

The retained source describes the attack path as follows: North Korean-linked (Lazarus/UNC4736); trojanized desktop app. The canonical record does not add intrusion steps beyond those supported by the source. [1](#source-1)

### Actors

- **Lazarus/UNC4736** — identified in the supported attack description. [1](#source-1)

### TTPs

- No specific MITRE ATT\&CK technique is currently mapped for this case.

## Response

The reviewed source does not describe containment, notification, or restoration steps in enough detail to summarize them responsibly.

This account is bounded to [3CX software supply chain compromise](https://cloud.google.com/blog/topics/threat-intelligence/3cx-software-supply-chain-compromise). Details absent from that evidence are left unresolved rather than inferred. [1](#source-1)

## Assets

[Download the case-scoped STIX 2.1 bundle](<https://www.ally.security/incidents/3cx-supply-chain-compromise-2023/stix.json>)

## Sources

Primary source records used to research this incident.

<a id="source-1"></a>

### 3CX software supply chain compromise

research · Google Cloud Mandiant

<https://cloud.google.com/blog/topics/threat-intelligence/3cx-software-supply-chain-compromise>

<details>
<summary>Evidence ledger</summary>

Review the supporting structured claims.

1. **Occurred At · 100% confidence · current**  
   Documented public update: 2023-04-20
2. **Resulted In · 88% confidence · current**  
   3CX supply-chain compromise: North Korean-linked (Lazarus/UNC4736); trojanized desktop app.
3. **Resulted In · 87% confidence · current**  
   3CX supply-chain compromise: Notable "double supply chain" attack — 3CX itself was compromised via an earlier trojanized trading app.
4. **Affected Organization · 100% confidence · current**  
   3CX supply-chain compromise: 3CX
5. **Resulted In · 100% confidence · current**  
   3CX supply-chain compromise: The reviewed source documents the 3cx supply-chain compromise involving 3CX.

</details>