{
	"id": "0bef9b4c-aa04-426c-9bcb-ed6993d9bb38",
	"created_at": "2026-04-11T02:23:53.636293Z",
	"updated_at": "2026-04-11T02:24:15.513454Z",
	"deleted_at": null,
	"sha1_hash": "d58bd89ca2f329a743f46d9f8731d93ba7298d87",
	"title": "B\u0026G Foods attacked by Daixin Team; files leaked - DataBreaches.Net",
	"llm_title": "",
	"authors": "",
	"file_creation_date": "0001-01-01T00:00:00Z",
	"file_modification_date": "0001-01-01T00:00:00Z",
	"file_size": 433442,
	"plain_text": "B\u0026G Foods attacked by Daixin Team; files leaked -\r\nDataBreaches.Net\r\nPublished: 2023-02-12 · Archived: 2026-04-11 02:00:19 UTC\r\nB\u0026G Foods describes itself as a “multibillion dollar company with more than 50 brands and one purpose:\r\nDelicious food from our family to yours.” Some of the California firm’s brands are Crisco, Green Giant,\r\nCinnamon Toast Crunch, Cream of Wheat, and Vermont Maid Syrup. But a recent cyberattack by Daixin Team has\r\nallegedly resulted in the encryption of an estimated 1,000 hosts and the exfiltration of files that have now been\r\nleaked on Daixin’s dark web leak site.\r\nDaixin’s leak site listing claims internal documents and databases exfiltrated from B\u0026G.\r\nA spokesperson for Daixin informs DataBreaches that B\u0026G was locked on February 4. On inquiry, Daixin’s\r\nspokesperson wasn’t sure whether they had encrypted all backups and stated that the firm could have recovered. \r\nWhen asked how they had contacted B\u0026G and whether B\u0026G ever responded, Daixin told DataBreaches that they\r\nhad left notes on the local network and sent several communications, but B\u0026G did not appear in the chat to\r\nrespond or try to negotiate.\r\n“Maybe they don’t care about the leak, and like to restore systems the hard way,” the spokesperson added.\r\nInspecting the leaked files confirmed one of Daixin’s statements to DataBreaches that this wasn’t one of their\r\nmore significant attacks. The leaked data does include internal company documents. However, the entire dump\r\ndoes not appear to have more serious or confidential corporate files, personnel files, or contractor files.\r\nSome personnel-related files concern employee benefits, while others reveal employees’ birthdays (month and\r\nday, but not year) and cellphone numbers. Other files concerned employee benefits.\r\nSome files, however, included sensitive employee data, as the two files below illustrate. The first is a portion of a\r\nletter sent to two healthcare professionals asking for their assessment as to whether a named employee was fit for\r\nhttps://www.databreaches.net/b-files-leaked/\r\nPage 1 of 3\n\nwork in light of their job duties, medical condition (severe sleep apnea), and prescribed medication.\r\nRequest for a fitness-to-work evaluation for a named employee. The letter indicated his medical\r\nissues and prescribed medication. Redacted by DataBreaches.net\r\nThe second image (below) is the top portion of the first page of a confidential investigation after an incident in\r\nwhich a named contractor was found unconscious on a job site from what appears to have been drug abuse or\r\noverdose.\r\nhttps://www.databreaches.net/b-files-leaked/\r\nPage 2 of 3\n\nThe top portion of a confidential and privileged report on a contractor found unresponsive on a job\r\nsite. Redacted by DataBreaches.net. B\u0026G purchased Smuckers in 2020. \r\nAs a multibillion-dollar company, B\u0026G could afford to pay a ransom, and their incident response is likely more\r\nattributable to a refusal to be extorted than an inability to pay. But how will they compensate employees whose\r\npersonal and sensitive details have now been leaked for everyone to read?\r\nDataBreaches sent an email inquiry to B\u0026G yesterday asking whether the encryption had interfered with any of\r\nB\u0026G’s functions and whether B\u0026G could decrypt any locked files without Daixin’s decryptor or if they were able\r\nto restore from a backup. They did not reply.\r\nThis post will be updated if more information is received.\r\nSource: https://www.databreaches.net/b-files-leaked/\r\nhttps://www.databreaches.net/b-files-leaked/\r\nPage 3 of 3",
	"extraction_quality": 1,
	"language": "EN",
	"sources": [
		"MISPGALAXY"
	],
	"origins": [
		"web"
	],
	"references": [
		"https://www.databreaches.net/b-files-leaked/"
	],
	"report_names": [
		"b-files-leaked"
	],
	"threat_actors": [],
	"ts_created_at": 1775874233,
	"ts_updated_at": 1775874255,
	"ts_creation_date": 0,
	"ts_modification_date": 0,
	"files": {
		"pdf": "https://archive.orkl.eu/d58bd89ca2f329a743f46d9f8731d93ba7298d87.pdf",
		"text": "https://archive.orkl.eu/d58bd89ca2f329a743f46d9f8731d93ba7298d87.txt",
		"img": "https://archive.orkl.eu/d58bd89ca2f329a743f46d9f8731d93ba7298d87.jpg"
	}
}