{
	"id": "f63d9da7-1001-4b3f-b05d-5c3833071741",
	"created_at": "2026-04-06T00:18:36.78585Z",
	"updated_at": "2026-04-10T13:11:36.393225Z",
	"deleted_at": null,
	"sha1_hash": "3235360d6e0079571fce57b5792774d2fa253ab2",
	"title": "Bridgestone Americas confirms ransomware attack, LockBit leaks data",
	"llm_title": "",
	"authors": "",
	"file_creation_date": "0001-01-01T00:00:00Z",
	"file_modification_date": "0001-01-01T00:00:00Z",
	"file_size": 3156381,
	"plain_text": "Bridgestone Americas confirms ransomware attack, LockBit leaks data\r\nBy Ionut Ilascu\r\nPublished: 2022-03-11 · Archived: 2026-04-05 16:56:20 UTC\r\nA cyberattack on Bridgestone Americas, one of the largest manufacturers of tires in the world, has been claimed by the\r\nLockBit ransomware gang.\r\nThe threat actor announced that they will leak all data stolen from the company and launched a countdown timer, which is\r\ncurrently at less than three hours.\r\nTimer activated\r\nBridgestone has tens of production units across the world and over 130,000 employees (regular and contractual), as per the\r\ncompany’s data at the end of 2020.\r\nhttps://www.bleepingcomputer.com/news/security/lockbit-ransomware-gang-claims-attack-on-bridgestone-americas/\r\nPage 1 of 5\n\n0:00\r\nhttps://www.bleepingcomputer.com/news/security/lockbit-ransomware-gang-claims-attack-on-bridgestone-americas/\r\nPage 2 of 5\n\nVisit Advertiser websiteGO TO PAGE\r\nOn February 27, Bridgestone started to investigate “a potential information security incident” detected in the morning hours\r\nof the same day.\r\n\"Out of an abundance of caution, we disconnected many of our manufacturing and retreading facilities in Latin America and\r\nNorth America from our network to contain and prevent any potential impact,” Bridgestone said in a statement to media.\r\nNo details about the incident emerged until today when the LockBit ransomware gang claimed the attack by adding\r\nBridgestone Americas to the list of their victims.\r\nLockBit is one of the most active ransomware gangs today, targeting large corporations, sometimes asking for ransoms of\r\ntens of millions of U.S. dollars, as was the case with Accenture.\r\nIt is unclear what data LockBit stole from Bridgestone or how detrimental leaking it would be to the company. At the time of\r\nwriting, the countdown from the actor for publishing the files expires in about three hours and a half.\r\nIn a report last month, industrial cybersecurity company Dragos notes that LockBit was the most active ransomware actor\r\ntargeting the industrial sector last year, with 103 attacks, followed by the Conti gang with 63.\r\nThe FBI in early February shared technical details and defense tips for LockBit ransomware attacks, noting that a bug in the\r\nmalware allows showing a hidden debug window to view in real-time the state of data destruction.\r\nhttps://www.bleepingcomputer.com/news/security/lockbit-ransomware-gang-claims-attack-on-bridgestone-americas/\r\nPage 3 of 5\n\nBleepingComputer has reached out to Bridgestone Americas for a statement on the recent incident but did not hear back by\r\npublishing time.\r\nUpdate [March 11, 16:36 EST]: Bridgestone Americas replied to BleepingComputer's request for comments saying that it\r\nis working with Accenture Security \"to investigate and understand the full scope and nature of the incident\" and that they are\r\nanalyzing to determine what data was stolen.\r\nThe full statement below:\r\nOn February 27, 2022, Bridgestone Americas detected an IT security incident. Since then, we have proactively notified\r\nfederal law enforcement and are staying in communication with them.  We are also working around the clock with external\r\nsecurity advisors, Accenture Security, to investigate and understand the full scope and nature of the incident. We have\r\ndetermined this incident to be the result of a ransomware attack. We have no evidence this was a targeted attack.\r\nUnfortunately, ransomware attacks similar to this one are increasing in sophistication and affecting thousands of\r\norganizations of all sizes.\r\nAs part of our investigation, we have learned that the threat actor has followed a pattern of behavior common to attacks of\r\nthis type by removing information from a limited number of Bridgestone systems and threatening to make this information\r\npublic. \r\nWe are committed to conducting a swift and decisive investigation to determine as quickly as possible what specific data was\r\ntaken from our environment. Bridgestone treats the security of our teammates, customers, and partners’ information with the\r\nutmost importance. We will continue to communicate with them often, working together to mitigate potential harm from\r\nthese types of incidents and to further enhance our cybersecurity measures as recommended by our internal and external\r\nsecurity advisors.\r\nhttps://www.bleepingcomputer.com/news/security/lockbit-ransomware-gang-claims-attack-on-bridgestone-americas/\r\nPage 4 of 5\n\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\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/lockbit-ransomware-gang-claims-attack-on-bridgestone-americas/\r\nhttps://www.bleepingcomputer.com/news/security/lockbit-ransomware-gang-claims-attack-on-bridgestone-americas/\r\nPage 5 of 5",
	"extraction_quality": 1,
	"language": "EN",
	"sources": [
		"Malpedia"
	],
	"origins": [
		"web"
	],
	"references": [
		"https://www.bleepingcomputer.com/news/security/lockbit-ransomware-gang-claims-attack-on-bridgestone-americas/"
	],
	"report_names": [
		"lockbit-ransomware-gang-claims-attack-on-bridgestone-americas"
	],
	"threat_actors": [],
	"ts_created_at": 1775434716,
	"ts_updated_at": 1775826696,
	"ts_creation_date": 0,
	"ts_modification_date": 0,
	"files": {
		"pdf": "https://archive.orkl.eu/3235360d6e0079571fce57b5792774d2fa253ab2.pdf",
		"text": "https://archive.orkl.eu/3235360d6e0079571fce57b5792774d2fa253ab2.txt",
		"img": "https://archive.orkl.eu/3235360d6e0079571fce57b5792774d2fa253ab2.jpg"
	}
}