- Date
- September 27, 2024
- Location
- Italy
- Industry
- Manufacturing
- Access vector
- Unknown
- OT targeting
- Indirect: abundance of caution
- Primary peril
- None
- Impact duration
- Unknown
Smeg appliance production halt after network anomaly, 2024

The incident path, stage by stage
Each stage of the attack, from intent to financial loss, with this incident’s path highlighted. Solid cells are confirmed, dashed cells are reported by a source but not confirmed, dotted cells are implied by the facts, and Unknown marks what is not publicly known. Click a stage title or a highlighted cell to read that part of the analysis.
Scroll sideways to see every stage.
On this page
Highlights
What happened. On September 27, 2024, Smeg, the Italian home-appliance maker based in Guastalla, found what it called “an anomaly in network processes” and, as a precaution, suspended its activities until its systems returned to full functionality[1][2]. The local press reported a suspected hacker attack, production stopped and hundreds of employees sent home[1].
Why it matters. Production stopped although every system any source names belongs to business IT, not to the production lines[1][3]. The company acknowledged the event, but almost nothing about its cause or cost has been made public.
About this analysis. This analysis sets out what is known, stage by stage. It rests on Smeg’s short statement, local press reporting and the attackers’ own claims, and the evidence is thin. This account reflects the best available information as of October 22, 2026; new information could confirm, change or discredit parts of it.
Highlights
- Smeg said the anomaly “temporarily compromised the normal operation of the company’s systems,” and that a temporary suspension of activities was ordered as a precaution[1].
- Il Resto del Carlino reported that the affected software manages production, logistics, HR and accounting, and that hundreds of employees could not continue working and went home[1].
- The Interlock ransomware group claimed responsibility and 820 GB of data. Smeg has confirmed neither, and Smeg never called the event an attack[4][3].
- No source gives a duration, an access route or any loss in money[2][3].
Attack flow
- Updated: 2026-10-22
- Intent: Malicious [reported | Press reports; Smeg never said attack]
- Threat actors: Cyber Criminals [reported | Interlock’s own claim]
- Access vector: Not disclosed [unknown | No source says how]
- IT impact: System Outage [confirmed | Per Smeg’s statement]; Data Exfiltration [reported | T1114, Interlock’s claim]
- OT targeting: Indirect: Abundance of Caution [confirmed]
- OT sophistication: Not applicable [not in path | No OT technique documented]
- OT impact: None [not in path | Only IT and ERP systems named]
- Perils: No Perils [confirmed | No physical event]
- Financial losses: Business Interruption [confirmed | No amount]; Cyber Incident Response [confirmed | No amount]; Assets & Equipment [implied]
What happened
Smeg’s statement, published by Il Resto del Carlino on September 28, 2024, says that on the previous day the company found “an anomaly in network processes” that “temporarily compromised the normal operation of the company’s systems.” “As a precaution,” it says, “a temporary suspension of activities was ordered until full functionality returns.” It adds that “the situation is under control,” that all measures needed to protect the integrity of information were promptly put in place, and that technicians were working to resolve the situation as quickly as possible[1]. CyberInsider carried the statement in English and said Smeg had not answered its request for comment[2].
Il Resto del Carlino reported a suspected hacker attack. It said the affected software manages production, logistics, HR and accounting, that production stopped, and that hundreds of employees went home[1]. ICS-STRIVE, an aggregator, names the SAP system and says the Guastalla headquarters and other branches in Italy were affected[3]. Smeg says it has five production plants in Italy[5]; no source says how many stopped.
Kaspersky ICS-CERT reported in February 2025 that the Interlock group claimed responsibility and “allegedly exfiltrated 820 GB of data”[4]. Interlock’s leak site listed Smeg on October 24, 2024, offering corporate documents and “a dump of mailboxes of all employees,” according to the tracker ransomware.live[6]. ICS-STRIVE records “No threat source identified” and “No Malware identified,” and gives the date as September 12, 2024, which conflicts with Smeg’s own statement[3]. September 12 is the date an earlier attack on Smeg UK began, in 2018[7].
Intent: reported as malicious
Smeg never called the event an attack. It described an anomaly in network processes and a precautionary suspension[1]. The press reported a suspected hacker attack, and Kaspersky ICS-CERT reports that a ransomware group claimed it[1][4]. That is consistent with a deliberate act rather than a technical failure, but it rests on press reporting and the attackers’ word, not on any statement by the victim or an authority. Intent is shown as malicious, reported.
Threat actors: an unverified ransomware claim
The only named actor is Interlock, and only on its own claim. Kaspersky ICS-CERT, which had no first-hand access, reports that the group claimed responsibility[4], and leak-site trackers show Smeg listed on October 24, 2024, with a claimed leak size of 820 GB[6][8]. Smeg named no attacker, and ICS-STRIVE identifies no threat source[3].
A US joint advisory on Interlock, published in July 2025, says the group was first observed in late September 2024 and uses a leak site for double extortion. It does not mention Smeg[9]. Cyber Criminals is shown as reported, and attribution is classed as suspected.
Access vector: not disclosed
No source says how anyone got in. Smeg’s statement describes only an anomaly in network processes, and both Il Resto del Carlino and CyberInsider said investigations were under way to find out how it happened[1][2]. The US advisory on Interlock describes the group’s usual entry routes, but it does not mention Smeg and says nothing about this case[9]. The stage is marked unknown.
IT impact: business systems down, data claimed
Smeg itself confirms that the normal operation of its systems was compromised[1], which is shown as System Outage. The systems named are business IT: software for production management, logistics, HR and accounting, according to the newspaper, and SAP, according to ICS-STRIVE[1][3].
Data theft is the attackers’ claim. Interlock’s listing offered corporate documents and employee mailboxes, and the group claimed 820 GB[6][4]. Smeg has not confirmed any data theft, and no authority has described the contents. Whether any data was encrypted is not known; ICS-STRIVE records no malware identified[3].
OT targeting: a precautionary stop
This is an indirect case driven by caution. Smeg’s own words are that the suspension was ordered “as a precaution”[1]. Production stopped and hundreds of employees went home, but every system any source names sits in the IT and ERP layer[1][3]. No source says that production-line control systems were touched.
The stop is the consequence. Whether production could have run without the business systems, and for how long, is not described.
OT sophistication: not applicable
No OT technique is documented. The systems named are business software, and no source describes any action on production equipment, line controllers or operator panels[1][3]. With no compromise of operational technology on record, there is nothing to grade, and the stage is marked not in path.
OT impact: none established
No source reports an effect on the production lines themselves. Production stopped because activities were suspended, not because a control system was reported to have failed or been manipulated[1]. No source confirms or denies involvement of production-line control systems. No PLC, line controller or operator panel is described as corrupted or replaced, and the stage is marked not in path.
Perils: none
There was no physical event. Smeg’s statement and the press describe a suspension of business systems and activities, and no source reports fire, overheating, equipment damage, injury or a release[1][2]. The map shows No Perils.
A factory whose lines were never touched can still stop when the business systems behind production are suspended.
Financial losses: none disclosed
No money figure exists for this incident: not a ransom, not a business interruption cost and not a recovery cost. Smeg’s own statement confirms the suspension of activities and the response work, and the newspaper reports production stopped[1]. No restoration date or duration is disclosed, so even an estimate based on downtime is out of reach. Employees were sent home rather than running manual or degraded operations[1].
Loss evidence
- Confirmed: Suspension of activities and lost production; Network event response and recovery
- Implied: Startup and return-to-service validation
- Not supported: Manual operations and workarounds (employees were sent home instead); Proprietary data response and recovery; Sensitive personal data response; Ransom extortion; Market valuation (Smeg is privately held); Server, computer, network and embedded device replacement; Industry regulation liability
No source reports a ransom demand, a negotiation or a payment. If the Interlock claim is right, the leak-site listing is consistent with no payment having been made[6].
What this incident shows
Smeg is a case that is real, acknowledged by the victim and financially opaque. The company confirmed a suspension of activities and response work in its own words, and the press confirmed that production stopped[1]. Beyond that there is almost no independently verifiable technical or financial detail.
It also shows how a precautionary decision becomes the loss. Every system any source names belongs to business IT, yet hundreds of workers went home[1][3]. And it shows why attackers’ claims need care: the actor, the data volume and even the date in some accounts come from sources other than the victim, and one aggregator’s date matches an older, separate incident[3][7].
References
- Lecci, Antonio. “Attacco hacker alla multinazionale Smeg: sistemi in avaria, produzione ferma” [Hacker attack on the multinational Smeg: systems down, production stopped]. Il Resto del Carlino, 28 Sept. 2024. ilrestodelcarlino.it/reggio-emilia/cronaca/guastalla-attacco-hacker-alla-ditta-smeg-ae6c5ef3
- Lekander, Alex. “High-End Appliances Maker Smeg Halts Production After Cyberattack.” CyberInsider, 30 Sept. 2024. cyberinsider.com/high-end-appliances-maker-smeg-halts-production-after-cyberattack/
- “Production at Standstill at Italian High-end Home Appliances Manufacturer.” ICS-STRIVE, 20 Nov. 2024. icsstrive.com/incident/production-at-standstill-at-italian-high-end-home-appliances-manufacturer/
- Kaspersky ICS-CERT. “Q3 2024 -- A Brief Overview of the Main Incidents in Industrial Cybersecurity.” Kaspersky ICS-CERT, 19 Feb. 2025. ics-cert.kaspersky.com/publications/reports/2025/02/19/q3-2024-a-brief-overview-of-the-main-incidents-in-industrial-cybersecurity/
- Smeg S.p.A. “About us.” Smeg. smeg.com/company/about-us
- “Smeg.” Interlock leak-site listing as tracked by ransomware.live, discovered 24 Oct. 2024. ransomware.live/id/U21lZ0BpbnRlcmxvY2s
- The Register, article on the 2018 Smeg UK cyberattack, 18 Sept. 2018. theregister.com/2018/09/18/smeg_cyber_attack/
- “Smeg Data Breach.” Breachsense, Oct. 2024 listing. breachsense.com/breaches/smeg-data-breach/
- FBI, CISA, HHS and MS-ISAC. “#StopRansomware: Interlock.” Cybersecurity Advisory AA25-203A, CISA, 22 July 2025. cisa.gov/news-events/cybersecurity-advisories/aa25-203a


