{
	"id": "cdd066a6-873b-416f-8028-671d3df457a6",
	"created_at": "2026-04-06T00:13:16.045761Z",
	"updated_at": "2026-04-10T13:13:00.249114Z",
	"deleted_at": null,
	"sha1_hash": "9d6f57a5a077306759512ecefc45185260e2fa4c",
	"title": "Security Concerns in Android mHealth Apps",
	"llm_title": "",
	"authors": "",
	"file_creation_date": "0001-01-01T00:00:00Z",
	"file_modification_date": "0001-01-01T00:00:00Z",
	"file_size": 38808,
	"plain_text": "Security Concerns in Android mHealth Apps\r\nArchived: 2026-04-05 13:19:41 UTC\r\nMobile Health (mHealth) applications lie outside of regulatory protection such as HIPAA, which requires a\r\nbaseline of privacy and security protections appropriate to sensitive medical data. However, mHealth apps,\r\nparticularly those in the app stores for iOS and Android, are increasingly handling sensitive data for both\r\nprofessionals and patients. This paper presents a series of three studies of the mHealth apps in Google Play that\r\nshow that mHealth apps make widespread use of unsecured Internet communications and third party servers. Both\r\nof these practices would be considered problematic under HIPAA, suggesting that increased use of mHealth apps\r\ncould lead to less secure treatment of health data unless mHealth vendors make improvements in the way they\r\ncommunicate and store data.\r\nGeneral Medicine\r\nAPA\r\nStandard\r\nHarvard\r\nVancouver\r\nAuthor\r\nBIBTEX\r\nRIS\r\nHe, D., Naveed, M., Gunter, C. A., \u0026 Nahrstedt, K. (2014). Security Concerns in Android mHealth Apps. AMIA ...\r\nAnnual Symposium proceedings / AMIA Symposium. AMIA Symposium, 2014, 645-654.\r\nSource: https://experts.illinois.edu/en/publications/security-concerns-in-android-mhealth-apps\r\nhttps://experts.illinois.edu/en/publications/security-concerns-in-android-mhealth-apps\r\nPage 1 of 1",
	"extraction_quality": 1,
	"language": "EN",
	"sources": [
		"MITRE"
	],
	"origins": [
		"web"
	],
	"references": [
		"https://experts.illinois.edu/en/publications/security-concerns-in-android-mhealth-apps"
	],
	"report_names": [
		"security-concerns-in-android-mhealth-apps"
	],
	"threat_actors": [
		{
			"id": "d90307b6-14a9-4d0b-9156-89e453d6eb13",
			"created_at": "2022-10-25T16:07:23.773944Z",
			"updated_at": "2026-04-10T02:00:04.746188Z",
			"deleted_at": null,
			"main_name": "Lead",
			"aliases": [
				"Casper",
				"TG-3279"
			],
			"source_name": "ETDA:Lead",
			"tools": [
				"Agentemis",
				"BleDoor",
				"Cobalt Strike",
				"CobaltStrike",
				"RbDoor",
				"RibDoor",
				"Winnti",
				"cobeacon"
			],
			"source_id": "ETDA",
			"reports": null
		},
		{
			"id": "75108fc1-7f6a-450e-b024-10284f3f62bb",
			"created_at": "2024-11-01T02:00:52.756877Z",
			"updated_at": "2026-04-10T02:00:05.273746Z",
			"deleted_at": null,
			"main_name": "Play",
			"aliases": null,
			"source_name": "MITRE:Play",
			"tools": [
				"Nltest",
				"AdFind",
				"PsExec",
				"Wevtutil",
				"Cobalt Strike",
				"Playcrypt",
				"Mimikatz"
			],
			"source_id": "MITRE",
			"reports": null
		}
	],
	"ts_created_at": 1775434396,
	"ts_updated_at": 1775826780,
	"ts_creation_date": 0,
	"ts_modification_date": 0,
	"files": {
		"pdf": "https://archive.orkl.eu/9d6f57a5a077306759512ecefc45185260e2fa4c.pdf",
		"text": "https://archive.orkl.eu/9d6f57a5a077306759512ecefc45185260e2fa4c.txt",
		"img": "https://archive.orkl.eu/9d6f57a5a077306759512ecefc45185260e2fa4c.jpg"
	}
}