{
	"id": "e5ca5f50-ef3a-4bbf-83ca-72cd1af51db3",
	"created_at": "2026-04-06T00:21:44.018752Z",
	"updated_at": "2026-04-10T03:20:49.757964Z",
	"deleted_at": null,
	"sha1_hash": "c138d3026c1be19148dd23ccd02cf9cc3a4a34ce",
	"title": "Steelcase furniture giant hit by Ryuk ransomware attack",
	"llm_title": "",
	"authors": "",
	"file_creation_date": "0001-01-01T00:00:00Z",
	"file_modification_date": "0001-01-01T00:00:00Z",
	"file_size": 2240999,
	"plain_text": "Steelcase furniture giant hit by Ryuk ransomware attack\r\nBy Lawrence Abrams\r\nPublished: 2020-10-27 · Archived: 2026-04-05 16:04:09 UTC\r\nOffice furniture giant Steelcase has suffered a ransomware attack that forced them to shut down their network to contain the\r\nattack's spread.\r\nSteelcase is the largest office furniture manufacturer globally, with 13,000 employees and $3.7 billion in 2020.\r\nSteelcase suffers a Ryuk ransomware attack\r\nIn an 8-K form filed with the Securities and Exchange Commission (SEC), Steelcase has disclosed that they were the victim\r\nof a cyberattack on October 22nd, 2020.\r\nhttps://www.bleepingcomputer.com/news/security/steelcase-furniture-giant-hit-by-ryuk-ransomware-attack/\r\nPage 1 of 4\n\n0:00\r\nhttps://www.bleepingcomputer.com/news/security/steelcase-furniture-giant-hit-by-ryuk-ransomware-attack/\r\nPage 2 of 4\n\nVisit Advertiser websiteGO TO PAGE\r\nOn October 22, 2020, Steelcase Inc. (the “Company”) detected a cyberattack on its information technology systems. The\r\nCompany promptly implemented a series of containment measures to address this situation including temporarily shutting\r\ndown the affected systems and related operations.\r\nThe Company is actively engaged in restoring the affected systems and returning to normal levels of operations. At this time,\r\nthe Company is not aware of any data loss from its systems or any other loss of assets as a result of this attack. Although\r\ncyberattacks can be unpredictable, the Company does not currently expect this incident will have a material impact on its\r\nbusiness operations or its financial results.\r\nBleepingComputer has been actively tracking this attack after a source in the cybersecurity industry told us last week that\r\nSteelcase suffered a Ryuk ransomware attack.\r\nWe were told that Steelcase's devices were encrypted by Ryuk after first being targeted by the same group behind the recent\r\nattack on Sopra Steria and Universal Health Services.\r\nIf you have first-hand information about this or other unreported cyberattacks, you can confidentially contact us on Signal\r\nat +16469613731 or on Wire at @lawrenceabrams-bc.\r\nThose attacks utilized either the BazarLoader or TrickBot infections, which ultimately provide remote access to the Ryuk\r\nRansomware threat actors, who then compromise the rest of the network and deploy Ryuk.\r\nIt is unknown how many devices were encrypted or if business operations were impacted other than the shutting down of the\r\nnetwork.\r\nBleepingComputer has contacted Steelcase with further questions but has not heard back.\r\nAutomated Pentesting Covers Only 1 of 6 Surfaces.\r\nAutomated pentesting proves the path exists. BAS proves whether your controls stop it. Most teams run one without the\r\nother.\r\nhttps://www.bleepingcomputer.com/news/security/steelcase-furniture-giant-hit-by-ryuk-ransomware-attack/\r\nPage 3 of 4\n\nThis whitepaper maps six validation surfaces, shows where coverage ends, and provides practitioners with three diagnostic\r\nquestions for any tool evaluation.\r\nSource: https://www.bleepingcomputer.com/news/security/steelcase-furniture-giant-hit-by-ryuk-ransomware-attack/\r\nhttps://www.bleepingcomputer.com/news/security/steelcase-furniture-giant-hit-by-ryuk-ransomware-attack/\r\nPage 4 of 4",
	"extraction_quality": 1,
	"language": "EN",
	"sources": [
		"Malpedia",
		"ETDA"
	],
	"references": [
		"https://www.bleepingcomputer.com/news/security/steelcase-furniture-giant-hit-by-ryuk-ransomware-attack/"
	],
	"report_names": [
		"steelcase-furniture-giant-hit-by-ryuk-ransomware-attack"
	],
	"threat_actors": [],
	"ts_created_at": 1775434904,
	"ts_updated_at": 1775791249,
	"ts_creation_date": 0,
	"ts_modification_date": 0,
	"files": {
		"pdf": "https://archive.orkl.eu/c138d3026c1be19148dd23ccd02cf9cc3a4a34ce.pdf",
		"text": "https://archive.orkl.eu/c138d3026c1be19148dd23ccd02cf9cc3a4a34ce.txt",
		"img": "https://archive.orkl.eu/c138d3026c1be19148dd23ccd02cf9cc3a4a34ce.jpg"
	}
}