3CX: Difference between revisions
mNo edit summary |
Lowspeedguy (talk | contribs) m Added the sixth reference link to the first Supply Chain Incident Response paragraph, as it is further proof of it and now it is more lixely for people to click on it if they want more proof for the paragraph's claim. |
||
| Line 20: | Line 20: | ||
====Supply Chain Incident Response==== | ====Supply Chain Incident Response==== | ||
In March 2023, 3CX was the victim of a high-profile supply chain hack, thought to be the result of a cascade failure starting with the software X_Trader. This attack was linked to an earlier incident perpetrated by North Korean hackers, targeting software company [https://www.marketswiki.com/wiki/Trading_Technologies_International Trading Technologies]. A 3CX employee's PC containing the Trading Technologies App was used by the hackers to compromise their software and distribute malware to consumers. <ref>{{Cite news |last=Greenberg |first=Andy |date=Apr 20, 2023 |title=The Huge 3CX Breach Was Actually 2 Linked Supply Chain Attacks |url=https://www.wired.com/story/3cx-supply-chain-attack-times-two/ |archive-url=https://web.archive.org/web/20250726115243/https://www.wired.com/story/3cx-supply-chain-attack-times-two/ |archive-date=July 26, 2025 |work=Wired |pages=2025-08-12}}</ref> | In March 2023, 3CX was the victim of a high-profile supply chain hack, thought to be the result of a cascade failure starting with the software X_Trader. This attack was linked to an earlier incident perpetrated by North Korean hackers, targeting software company [https://www.marketswiki.com/wiki/Trading_Technologies_International Trading Technologies]. A 3CX employee's PC containing the Trading Technologies App was used by the hackers to compromise their software and distribute malware to consumers. <ref>{{Cite news |last=Greenberg |first=Andy |date=Apr 20, 2023 |title=The Huge 3CX Breach Was Actually 2 Linked Supply Chain Attacks |url=https://www.wired.com/story/3cx-supply-chain-attack-times-two/ |archive-url=https://web.archive.org/web/20250726115243/https://www.wired.com/story/3cx-supply-chain-attack-times-two/ |archive-date=July 26, 2025 |work=Wired |pages=2025-08-12}}</ref><ref name=":1" /> | ||
3CX also faced backlash for requiring users to pay a fee when opening support tickets during the breach, which led to further public criticism from system administrators and IT professionals.<ref>{{Cite web |last=CrowdStrike |date=2023-03-29 |title=// 2023-03-29 // SITUATIONAL AWARENESS // CrowdStrike Tracking Active Intrusion Campaign Targeting 3CX Customers // |url=https://www.reddit.com/r/crowdstrike/comments/125r3uu/20230329_situational_awareness_crowdstrike/ |website=reddit}}</ref><blockquote>"I have been in contact with 3CX and their suggestion is to open a support ticket at £75 per incident. Ludicrous." -wars_t (reddit.com) </blockquote> | 3CX also faced backlash for requiring users to pay a fee when opening support tickets during the breach, which led to further public criticism from system administrators and IT professionals.<ref name=":1">{{Cite web |last=CrowdStrike |date=2023-03-29 |title=// 2023-03-29 // SITUATIONAL AWARENESS // CrowdStrike Tracking Active Intrusion Campaign Targeting 3CX Customers // |url=https://www.reddit.com/r/crowdstrike/comments/125r3uu/20230329_situational_awareness_crowdstrike/ |website=reddit}}</ref><blockquote>"I have been in contact with 3CX and their suggestion is to open a support ticket at £75 per incident. Ludicrous." -wars_t (reddit.com) </blockquote> | ||
==References:== | ==References:== | ||
<references /> | <references /> | ||
[[Category:3CX]] | [[Category:3CX]] | ||