Back to the archive

The encyclopedia · Engineering & Operations · Technical decision · 2026

A cyberattack stopped ZEGO's machines for six weeks — then came the insolvency

Aschaffenburg textile finisher, ~60 staff. Attack on 29 March 2026 halted production for six weeks; by July the company had filed for insolvency.

ZEGO Textilveredelungszentrum · 2026-07-09

What happened

ZEGO Textilveredelungszentrum GmbH is an Aschaffenburg textile finisher: embroidery, sewing and printing on work, business and team clothing, plus storage and logistics for its customers. Around 60 people worked there — a single-site operation whose entire order book runs through its own IT.

On 29 March 2026 a cyberattack brought that IT down, and production stood still for almost six weeks. The type of attack was never disclosed — extortion was discussed in reporting, unconfirmed; what is documented is the outage itself: orders could not be processed, machines could not be fed. For a finisher that lives on delivery dates, six weeks is not a delay — it is a breach of contract.

In July 2026 the company filed for insolvency at the Aschaffenburg district court, which appointed Maximilian Maierhofer of the Ohly Zöller firm as preliminary insolvency administrator. Managing director Johannes Zenglein said the attack 'hurts a lot', insisted that insolvency is not necessarily the end of a company, and set the goals: restructure, stabilise economically, preserve jobs. Production is meant to continue through the proceedings.

The shape of the case: no strategic blunder, no failed collection — an external shock that a 60-person shop had no cushion for. Six weeks of downtime converted one IT incident into an insolvency filing.

Why it happened

  • The attack of 29 March 2026 halted production for almost six weeks — orders unprocessed, machines idle — and the lost revenue could not be recovered afterwards
  • A single-site finisher of around 60 employees had no cushion: no redundant IT, no alternate production, no way to keep delivery dates while its systems were down
  • By July the only instrument left was insolvency at the Aschaffenburg district court, with a preliminary administrator appointed to steer the restructuring
  • Management's own framing — restructure, stabilise, preserve jobs — concedes that the attack turned a running business into a case for the court
What it costinsolvency after a six-week standstillcostly

The lesson

For a small single-site producer, an IT attack is not an IT incident — it is six weeks of revenue gone. ZEGO's machines stood still in March; by July the company was in insolvency.

Aftermath

Under preliminary administrator Maximilian Maierhofer, ZEGO kept producing through the proceedings, its stated aim to restructure and preserve the roughly 60 jobs. Whether the procedure ends in a plan, a buyer or shrinkage was still open as the case entered the court's hands — the attacker behind it all has never been named.

Sources

spotted an error? The club wants to know.

Comments · 0

    Sign in to join the comments.

    More like this

    Somewhere, someone solved the problem this company failed at. 2nd Opinion →