{
	"id": "c133d29c-0f78-45d2-9beb-45f4690a4a8b",
	"created_at": "2026-04-06T01:30:57.300232Z",
	"updated_at": "2026-04-10T03:21:32.067465Z",
	"deleted_at": null,
	"sha1_hash": "ffad7536fd2e26baf270b8de42a2d29fa5e54e92",
	"title": "CAPEC-270: Modification of Registry Run Keys (Version 3.9)",
	"llm_title": "",
	"authors": "",
	"file_creation_date": "0001-01-01T00:00:00Z",
	"file_modification_date": "0001-01-01T00:00:00Z",
	"file_size": 47700,
	"plain_text": "CAPEC-270: Modification of Registry Run Keys (Version 3.9)\r\nArchived: 2026-04-06 01:09:15 UTC\r\nAttack Pattern ID: 270\r\nAbstraction: Detailed\r\n Description\r\nAn adversary adds a new entry to the \"run keys\" in the Windows registry so that an application of their choosing is executed\r\nwhen a user logs in. In this way, the adversary can get their executable to operate and run on the target system with the\r\nauthorized user's level of permissions. This attack is a good way for an adversary to run persistent spyware on a user's\r\nmachine, such as a keylogger.\r\n Likelihood Of Attack\r\nMedium\r\n Typical Severity\r\nMedium\r\n Relationships\r\nThis table shows the other attack patterns and high level categories that are related to this attack pattern. These\r\nrelationships are defined as ChildOf and ParentOf, and give insight to similar items that may exist at higher and lower levels\r\nof abstraction. In addition, relationships such as CanFollow, PeerOf, and CanAlsoBe are defined to show similar attack\r\npatterns that the user may want to explore.\r\nNature Type\r\nChildOf Standard Attack Pattern - A standard level attack pattern in CAPEC is focused on a specific methodology or technique used in an attac\r\nCanFollow Standard Attack Pattern - A standard level attack pattern in CAPEC is focused on a specific methodology or technique used in an attac\r\nCanPrecede Standard Attack Pattern - A standard level attack pattern in CAPEC is focused on a specific methodology or technique used in an attac\r\nCanPrecede Detailed Attack Pattern - A detailed level attack pattern in CAPEC provides a low level of detail, typically leveraging a specific techni\r\nCanPrecede Standard Attack Pattern - A standard level attack pattern in CAPEC is focused on a specific methodology or technique used in an attac\r\nThis table shows the views that this attack pattern belongs to and top level categories within that view.\r\nView Name Top Level Categories\r\nDomains of Attack Software\r\nMechanisms of Attack Manipulate System Resources\r\n Execution Flow\r\nExplore\r\n1. Determine target system: The adversary must first determine the system they wish to target. This attack only works\r\non Windows.\r\nhttps://capec.mitre.org/data/definitions/270.html\r\nPage 1 of 3\n\nExperiment\r\n1. Gain access to the system: The adversary needs to gain access to the system in some way so that they can modify\r\nthe Windows registry.\r\nTechniques\r\nGain physical access to a system either through shoulder surfing a password or accessing a system that is left\r\nunlocked.\r\nGain remote access to a system through a variety of means.\r\nExploit\r\n1. Modify Windows registry: The adversary will modify the Windows registry by adding a new entry to the \"run keys\"\r\nreferencing a desired program. This program will be run whenever the user logs in.\r\n Prerequisites\r\nThe adversary must have gained access to the target system via physical or logical means in order to carry out this attack.\r\n Consequences\r\nThis table specifies different individual consequences associated with the attack pattern. The Scope identifies the security\r\nproperty that is violated, while the Impact describes the negative technical impact that arises if an adversary succeeds in\r\ntheir attack. The Likelihood provides information about how likely the specific consequence is expected to be seen relative\r\nto the other consequences in the list. For example, there may be high likelihood that a pattern will be used to achieve a\r\ncertain impact, but a low likelihood that it will be exploited to achieve a different impact.\r\nScope Impact Likelihood\r\nIntegrity\r\nModify Data\r\nGain Privileges\r\n Mitigations\r\nIdentify programs that may be used to acquire process information and block them by using a software restriction policy or\r\ntools that restrict program execution by using a process allowlist.\r\n Example Instances\r\nAn adversary can place a malicious executable (RAT) on the target system and then configure it to automatically run\r\nwhen the user logs in to maintain persistence on the target system.\r\nThrough the modification of registry \"run keys\" the adversary can masquerade a malicious executable as a legitimate\r\nprogram.\r\n Taxonomy Mappings\r\nCAPEC mappings to ATT\u0026CK techniques leverage an inheritance model to streamline and minimize direct\r\nCAPEC/ATT\u0026CK mappings. Inheritance of a mapping is indicated by text stating that the parent CAPEC has relevant\r\nATT\u0026CK mappings. Note that the ATT\u0026CK Enterprise Framework does not use an inheritance model as part of the\r\nmapping to CAPEC.\r\nRelevant to the ATT\u0026CK taxonomy mapping (also see parent)\r\nEntry ID Entry Name\r\n1547.001 Boot or Logon Autostart Execution: Registry Run Keys / Start Folder\r\n1547.014 Boot or Logon Autostart Execution: Active\r\n Content History\r\nSubmissions\r\nSubmission\r\nDate\r\nSubmitter Organization\r\nhttps://capec.mitre.org/data/definitions/270.html\r\nPage 2 of 3\n\n2014-06-23\r\n(Version 2.6)\r\nCAPEC Content Team The MITRE Corporation\r\nModifications\r\nModification\r\nDate\r\nModifier Organization\r\n2015-11-09\r\n(Version 2.7)\r\nCAPEC Content Team The MITRE Corporation\r\nUpdated References\r\n2018-07-31\r\n(Version 2.12)\r\nCAPEC Content Team The MITRE Corporation\r\nUpdated Attack_Motivation-Consequences, Attack_Prerequisites, Description Summary, Examples-Instances, Solutions_and_Mitigations, Typical_Likelihood_of_Exploit, Typical_Severity\r\n2019-04-04\r\n(Version 3.1)\r\nCAPEC Content Team The MITRE Corporation\r\nUpdated Related_Weaknesses\r\n2020-07-30\r\n(Version 3.3)\r\nCAPEC Content Team The MITRE Corporation\r\nUpdated Description, Mitigations, Taxonomy_Mappings\r\n2021-10-21\r\n(Version 3.6)\r\nCAPEC Content Team The MITRE Corporation\r\nUpdated Description, Execution_Flow, Related_Attack_Patterns\r\n2022-09-29\r\n(Version 3.8)\r\nCAPEC Content Team The MITRE Corporation\r\nUpdated Taxonomy_Mappings\r\nMore information is available — Please select a different filter.\r\nSource: https://capec.mitre.org/data/definitions/270.html\r\nhttps://capec.mitre.org/data/definitions/270.html\r\nPage 3 of 3",
	"extraction_quality": 1,
	"language": "EN",
	"sources": [
		"MITRE"
	],
	"references": [
		"https://capec.mitre.org/data/definitions/270.html"
	],
	"report_names": [
		"270.html"
	],
	"threat_actors": [],
	"ts_created_at": 1775439057,
	"ts_updated_at": 1775791292,
	"ts_creation_date": 0,
	"ts_modification_date": 0,
	"files": {
		"pdf": "https://archive.orkl.eu/ffad7536fd2e26baf270b8de42a2d29fa5e54e92.pdf",
		"text": "https://archive.orkl.eu/ffad7536fd2e26baf270b8de42a2d29fa5e54e92.txt",
		"img": "https://archive.orkl.eu/ffad7536fd2e26baf270b8de42a2d29fa5e54e92.jpg"
	}
}