2024 · Canada · C - Manufacturing · Compromised customer support portal replying with phishing
Analysed 2026-11-06 by Hermes
Open this case in the tool →Compromised customer support portal replying with phishing
Expertise to Execution
Evidence coverage: 3/6 stages, weight 15/60
Decisive stage: detection (clearest evidence) · Alternative: Strategy to Leadership
(1) Mercku, a Canadian router maker whose equipment is distributed to customers by Canadian and European ISPs (Start.ca, FibreStream, Innsys, RealNett, Orion Telekom, Kelcom), runs a Zendesk-hosted helpdesk portal as its official, inherently trusted customer support channel; the standing expectation is that automated customer communications from that channel are protected against covert modification, that changes to the ticket-reply process are verified, and that anomalies in outbound customer traffic are noticed. (2) Unknown threat actors altered the portal so that every newly filed support ticket was auto-answered with a fake 'Metamask: Mandatory Metamask Account Update Required' phishing email using a userinfo-obfuscated link; the abuse kept running for new tickets until BleepingComputer verified it by submitting test tickets and notified Mercku's support and press teams (first report 01-07-2024), and the company subsequently made no statement on the cause or the rectification. (3) The classification rests on the detection stage: the unacted-on knowledge is material - integrity monitoring of outbound replies on one's own customer-facing channel and verification of ticket-process changes are standard technical remedies, not a strategic controversy - and the chain broke in execution, because these known controls were not realised in operations and the incident reached the victim only via an external tester's notification. The entry vector is undisclosed and is not load-bearing. A secondary Strategy to Leadership pattern appears in the response stage (media-only disclosure while the abuse was live), but it rests on the absence of reporting rather than a documented decision and is recorded as contributing only. RM34 (Expertise to Execution lens): available monitoring for the victim's own customer-facing channel was not configured, tuned or maintained to detect that its ticket acknowledgements had been replaced by phishing, so the compromise stayed invisible until BleepingComputer's test submissions exposed it (causal role: Obscuring). RM45 (Expertise to Execution lens): verification of changes to the support-ticket acknowledgement process is a known technical control, but it was not built into the process, so the attacker's altered auto-reply was sent without independent check to every new ticket requester (causal role: Enabling).
RM34 — Monitoring / detection / alert-handling gapRM45 — Business-process verification gapEntry vector never disclosed: no source (and no Mercku or Zendesk statement) explains how the helpdesk portal was compromised; the entry- and detection-stage origin/break answers therefore rest on coder inference, which caps confidence at 3. The EuRepoC row gives start_date 01.06.2024 and 'disclosed by media', while the first public report (BleepingComputer) is dated 01-07-2024 and later reporting places the verification end of June 2024; the June date is not corroborated in open reporting, Year 2024 holds either way. EuRepoC fields record no data breach, no system interference and no economic impact, consistent with the press record; no victim notification to customers was found. Follow-up coverage on how the ticket pipeline was subverted (e.g. compromised agent credentials) does not exist in open sources as of this analysis. The case-file description matches the stated victim (no data-quality mismatch). No step required consent beyond normal public-source research.