Explore our new Cybersecurity Terms Glossary, explained by our experts.
Cybersecurity Terms Glossary
In March 2023 a signed 3CX softphone update carried a North Korean backdoor. The attackers had reached the vendor through a second poisoned installer, making it the first documented cascading supply chain compromise.

What Was the 3CX Supply Chain Attack?
On 29 March 2023 several security vendors warned that the 3CX DesktopApp, a softphone shipped by a company that claims more than 600,000 business customers, was beaconing to attacker-controlled infrastructure. The installer was genuine: signed with 3CX’s own certificate and served from 3CX’s own update servers. Malicious code had been inserted inside the vendor’s build pipeline, so every customer who accepted the update installed the backdoor themselves.
Investigators attributed the operation to a North Korean cluster, tracked by Mandiant as UNC4736 and overlapping with the activity usually called Labyrinth Chollima. What makes the case worth studying is not the payload but how the attackers reached 3CX in the first place: through a different poisoned installer. It remains the clearest public example of a cascading software supply chain compromise.
The affected Windows builds were 18.12.407 and 18.12.416; the macOS client was tampered with separately. Two libraries bundled with the Electron application, ffmpeg.dll and d3dcompiler_47.dll, had been modified. The first contained shellcode that located an encrypted blob appended to the second, decrypted it, and ran it in memory. This is textbook DLL side-loading, with the signature of a trusted application doing the work of a signature on the malware.
The loader then retrieved icon files from a GitHub repository. Appended to each .ico file was a Base64 string holding the address of the next command-and-control server, a quiet way to publish infrastructure that survives individual takedowns. A small, selected subset of victims then received a final-stage information stealer that harvested browsing history and stored credentials from Chrome, Edge, Brave, and Firefox.
Mandiant’s investigation, published in April 2023, traced the intrusion back to one employee workstation. The employee had downloaded X_TRADER, a trading application from Trading Technologies that had itself been trojanised and signed with a valid certificate. The product had been discontinued in 2020, but the installer was still downloadable, and nothing on the 3CX network stopped a developer from running it. Credentials harvested from that machine gave the attackers a path into the build environments for both the Windows and the macOS clients.
A compromise of one software vendor was therefore used to compromise another, whose product then shipped to hundreds of thousands of organisations. That pattern is why third-party assurance questionnaires alone are a weak control: 3CX could have answered every question honestly and still shipped the backdoor.
The trojanised updates were in circulation for around a week before public confirmation. Customers had already reported that their endpoint detection products were flagging the 3CX client, and those reports were initially treated as false positives — a reaction worth rehearsing against, because it is the natural one. A signed binary from a named vendor sits in almost every application allow list, and the outbound traffic was ordinary HTTPS to GitHub and commodity hosting.
Operators of essential services under the NIS Regulations 2018 are assessed against the NCSC Cyber Assessment Framework, whose principle A4 covers supply chain risk explicitly, and UK financial entities now face comparable third-party duties. The NCSC’s supply chain security guidance is written for exactly this case: knowing which suppliers can reach your network, and what happens when one of them is the attack.
If you need to establish whether a compromised product touched your estate, our investigation and incident response services can scope and run that hunt.
The trojanised Windows builds of the 3CX DesktopApp were 18.12.407 and 18.12.416, distributed as an Electron application. A separate macOS build released in the same period was also tampered with. 3CX published updated versions and a list of indicators, and recommended that customers move to the web client until clean installers were confirmed. Check your deployment records rather than only the currently installed version.
It is a compromise of one software supplier used as the route into another supplier, whose product then reaches the eventual victims. In the 3CX case, a trojanised X_TRADER installer compromised a 3CX employee, and the credentials taken from that machine opened the 3CX build pipeline. The defining feature is that the final victims are two vendors removed from the original intrusion.
No. A software bill of materials lists components, and the malicious DLLs carried the names of components that genuinely belonged in the product. An SBOM still helps after disclosure, because it answers which systems contain the named files and versions. Prevention depends on build pipeline integrity at the vendor, reproducible builds, and behavioural monitoring on your own endpoints.
Focus on behaviour rather than provenance. Watch for business applications that start resolving unfamiliar domains, fetch files from code-hosting services, read browser credential stores, or spawn unexpected child processes. Retain endpoint and DNS telemetry long enough to look backwards when an advisory appears, and treat detections against signed commercial software as findings to investigate, not noise to suppress.
You May Be Interested In These
We use a few cookies that are needed to make this website work, and they are always on. We would also like to set analytics cookies, to see which pages are useful; functional cookies, so that our live chat works; and advertising cookies, to measure our campaigns. We will not set any of those until you say yes, and you can change your mind at any time from the Cookie Settings link in the footer.
Choose the cookies you are happy for us to use. Strictly necessary cookies are always on; everything else is off until you turn it on.
These cookies keep the website working: they hold your security checks, your form submissions and the choice you make here. The site cannot run without them, so they are always on.
These let our live chat open and remember your conversation, and let the newsletter sign-up work. Switch them off and the chat window will not appear.
These tell us which pages are read and how people find us, so that we can improve the site. The reports are about groups of visitors, never about you personally.
These let us measure our advertising and show you our adverts on other websites, such as LinkedIn, Google and Meta. Switch them off and you will still see adverts, but they will be less relevant.