{
	"id": "558579db-2aa8-4d19-9f1c-3e8ffd1a26c3",
	"created_at": "2026-09-13T02:02:33.576979Z",
	"updated_at": "2026-11-22T02:22:26.595069Z",
	"deleted_at": null,
	"sha1_hash": "e9a205a3ed7f2f1f13a6f6deadafb91233f24ae7",
	"title": "[SHADOWBYT3$] - Ransomware Victim: UMSA - RedPacket Security",
	"llm_title": "[SHADOWBYT3$] - Ransomware Victim: UMSA - RedPacket Security",
	"authors": "RedPacket Security",
	"file_creation_date": "0001-01-01T00:00:00Z",
	"file_modification_date": "0001-01-01T00:00:00Z",
	"file_size": 41100,
	"plain_text": "https://www.redpacketsecurity.com/shadowbyt3-ransomware-victim-umsa/\n\n[SHADOWBYT3$] - Ransomware Victim: UMSA - RedPacket\n\nSecurity\n\nBy September 10, 2026\n\nPublished: 2026-02-25 · Archived: 2026-09-13 02:00:20 UTC\n\nRead with OpenAI\n\nimage\n\nNOTE: No files or stolen information are exfiltrated, downloaded, taken, hosted, seen, reposted, or disclosed by\n\nRedPacket Security. Any legal issues relating to the content should be directed at the attackers, not RedPacket\n\nSecurity. This blog is an editorial notice informing that a company has fallen victim to a ransomware attack.\n\nRedPacket Security is not affiliated with any ransomware threat actors or groups and will not host infringing\n\ncontent. The information on this page is automated and redacted whilst being scraped directly from the\n\nSHADOWBYT3$ Onion Dark Web Tor Blog page.\n\nRansomware group:\n\nSHADOWBYT3$\n\nVictim name:\n\nUMSA\n\nAI Generated Summary of the Ransomware Leak Page\n\nThe leak page associated with the victim UMSA, attributed to the threat group ShadowByt3$, appears as a data-\n\nexfiltration post published on 2026-02-17 at 17:00:00. The available metadata indicates a reference to a file\n\nlabeled “UMSA_LEAK.7z,” suggesting that the attackers claim to have exfiltrated data from the organization and\n\nare presenting a compressed archive as part of the leak. The post does not provide a clear statement of the\n\nindustry, operational impact, or a specified ransom demand within the available fields. The absence of an explicit\n\ncompromise date beyond the post date means the published timestamp serves as the primary temporal marker for\n\nthis event in the leak listing.\n\nRegarding the content and presentation of the page, there is no evidence of included screenshots or other images\n\nwithin the provided data (the record shows zero images and zero downloads). The post references an archive file\n\nname but does not disclose additional visible artifacts or graphics in the metadata. In keeping with standard\n\nransomware reporting, the incident is described here as a data-leak event rather than a confirmed encryption-only\n\nincident, though the exact scope and nature of affected data remain unspecified in the available details. PII or\n\ncontact information is not present in the summary, and the victim name “UMSA” is preserved as issued. The\n\nabsence of visible images or links means there are no additional visual proofs to reference in this summary.\n\nPage 1 of 2\n\nhttps://www.redpacketsecurity.com/shadowbyt3-ransomware-victim-umsa/\n\nSupport Our Work\n\nA considerable amount of time and effort goes into maintaining this website, creating backend automation and\n\ncreating new features and content for you to make actionable intelligence decisions. Everyone that supports the\n\nsite helps enable new functionality.\n\nIf you like the site, please support us on Patreon or Buy Me A Coffee using the buttons below.\n\nAI APIs OSINT driven New features\n\nBuy Me A Coffee Patreon\n\nPost navigation\n\nSource: https://www.redpacketsecurity.com/shadowbyt3-ransomware-victim-umsa/\n\nPage 2 of 2",
	"extraction_quality": 1,
	"language": "EN",
	"sources": [
		"MISPGALAXY",
		"Malpedia"
	],
	"origins": [
		"web"
	],
	"references": [
		"https://www.redpacketsecurity.com/shadowbyt3-ransomware-victim-umsa/"
	],
	"report_names": [
		"shadowbyt3-ransomware-victim-umsa"
	],
	"threat_actors": [
		{
			"id": "fc60e135-9e19-40d8-b882-f65934b8a43e",
			"created_at": "2026-09-13T02:00:05.998986Z",
			"updated_at": "2026-11-22T02:00:30.437977Z",
			"deleted_at": null,
			"main_name": "ShadowByt3$",
			"aliases": [],
			"source_name": "MISPGALAXY:ShadowByt3$",
			"tools": [],
			"source_id": "MISPGALAXY",
			"reports": null
		}
	],
	"ts_created_at": 1789264953,
	"ts_updated_at": 1795314146,
	"ts_creation_date": 0,
	"ts_modification_date": 0,
	"files": {
		"pdf": "https://archive.orkl.eu/e9a205a3ed7f2f1f13a6f6deadafb91233f24ae7.pdf",
		"text": "https://archive.orkl.eu/e9a205a3ed7f2f1f13a6f6deadafb91233f24ae7.txt",
		"img": "https://archive.orkl.eu/e9a205a3ed7f2f1f13a6f6deadafb91233f24ae7.jpg"
	},
	"iocs": [
		{
			"type": "domain",
			"value": "www.redpacketsecurity.com",
			"count": 3,
			"flags": [
				"in_url_host"
			],
			"some_flags": [
				"in_url_host"
			]
		},
		{
			"type": "url",
			"value": "https://www.redpacketsecurity.com/shadowbyt3-ransomware-victim-umsa/",
			"count": 3,
			"flags": [],
			"some_flags": []
		}
	]
}