{
	"id": "dff87189-2f4e-4db6-bb8b-b7d3fa39e9a2",
	"created_at": "2026-04-06T00:10:40.620743Z",
	"updated_at": "2026-04-10T03:20:37.878814Z",
	"deleted_at": null,
	"sha1_hash": "e2e30a15ec87f8b6c5dbacc8182d65ac79278809",
	"title": "HildaCrypt Ransomware Developer Releases Decryption Keys",
	"llm_title": "",
	"authors": "",
	"file_creation_date": "0001-01-01T00:00:00Z",
	"file_modification_date": "0001-01-01T00:00:00Z",
	"file_size": 1586138,
	"plain_text": "HildaCrypt Ransomware Developer Releases Decryption Keys\r\nBy Lawrence Abrams\r\nPublished: 2019-10-05 · Archived: 2026-04-05 23:03:46 UTC\r\nThe developer behind the HildaCrypt Ransomware has decided to release the ransomware's private decryption keys. With\r\nthese keys a decryptor can be made that would allow any potential victims to recover their files for free.\r\nWhen a new ransomware or a variant is discovered, it is very common for researchers to post about them on Twitter.  This\r\nweek, researcher GrujaRS discovered a new ransomware variant and identified it as a STOP variant.\r\nhttps://www.bleepingcomputer.com/news/security/hildacrypt-ransomware-developer-releases-decryption-keys/\r\nPage 1 of 4\n\n0:00\r\nhttps://www.bleepingcomputer.com/news/security/hildacrypt-ransomware-developer-releases-decryption-keys/\r\nPage 2 of 4\n\nVisit Advertiser websiteGO TO PAGE\r\nLast night, the developer contacted the researcher to tell him that it was an incorrect identification and that it was actually a\r\nvariant of the HildaCrypt Ransomware.\r\nAs part of this communication, the developer decided to also release the master private decryption keys for the ransomware.\r\nWith these keys a decryptor can be made that allows a victim to get their files back for free.\r\nHildaCrypt Ransomware Decryption Keys\r\nAfter giving the keys to Michael Gillespie, he confirmed they were legitimate released a decryptor using them.\r\nFor those who wish to view the keys or create a decryptor based on them, they can be accessed here.\r\nHildaCrypt was created for fun\r\nBleepingComputer had a conversation with the ransomware developer last night and was told that HildaCrypt was only\r\nmade for fun and \"it was mainly an educational thing really\".\r\nThey further told us \"hildacrypt never was used on anyone\" and that they released the keys in case \"some kid gets a hold of\r\nthese binaries I hope the keys would be of some use\".\r\nAfter further discussion, the developer intimated that they were probably going to stop development of the ransomware and\r\ninstead focus on getting involved in more legitimate efforts of the cybersecurity community.\r\nhttps://www.bleepingcomputer.com/news/security/hildacrypt-ransomware-developer-releases-decryption-keys/\r\nPage 3 of 4\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/hildacrypt-ransomware-developer-releases-decryption-keys/\r\nhttps://www.bleepingcomputer.com/news/security/hildacrypt-ransomware-developer-releases-decryption-keys/\r\nPage 4 of 4",
	"extraction_quality": 1,
	"language": "EN",
	"sources": [
		"Malpedia"
	],
	"references": [
		"https://www.bleepingcomputer.com/news/security/hildacrypt-ransomware-developer-releases-decryption-keys/"
	],
	"report_names": [
		"hildacrypt-ransomware-developer-releases-decryption-keys"
	],
	"threat_actors": [],
	"ts_created_at": 1775434240,
	"ts_updated_at": 1775791237,
	"ts_creation_date": 0,
	"ts_modification_date": 0,
	"files": {
		"pdf": "https://archive.orkl.eu/e2e30a15ec87f8b6c5dbacc8182d65ac79278809.pdf",
		"text": "https://archive.orkl.eu/e2e30a15ec87f8b6c5dbacc8182d65ac79278809.txt",
		"img": "https://archive.orkl.eu/e2e30a15ec87f8b6c5dbacc8182d65ac79278809.jpg"
	}
}