CAPEC-444
Development Alteration
An adversary modifies a technology, product, or component during its development to acheive a negative impact once the system is deployed. The goal of the adversary is to modify the system in such a way that the negative impact can be leveraged when the system is later deployed. Development alteration attacks may include attacks that insert malicious logic into the system's software, modify or replace hardware components, and other attacks which negatively impact the system during development. These attacks generally require insider access to modify source code or to tamper with hardware components. The product is then delivered to the user where the negative impact can be leveraged at a later time.
On this page
Ask an AI about this attack pattern
Show the prompt
Explain the attack pattern CAPEC-444: Development Alteration: how it unfolds, what it needs and how to prevent and detect it in my systems. Use https://capec.mitre.org/data/definitions/444.html and https://cve.bz/cve/capec/444?via=ask-ai-copy, which lists recent CVEs with the weaknesses it exploits. Cite the sources.Opens a third-party assistant; its answer is its own, not cve.bz's. The prompt holds only this attack pattern's id and public links.
Prerequisites
Access to the system during the development phase to alter and/or modify software and hardware components. This access is often obtained via insider access or by leveraging another attack pattern to gain permissions that the adversary wouldn't normally have.
Consequences
| Impact | Affects | Note |
|---|---|---|
| Execute Unauthorized Commands | Authorization | |
| Unreliable Execution | Availability | |
| Alter Execution Logic | Integrity |
Mitigations
Assess software and software components during development and prior to deployment to ensure that they function as intended and without any malicious functionality.
Related attack patterns
- Part of
- CAPEC-438 Modification During Manufacture
- More specific patterns
- CAPEC-206 Signing Malicious Code
- CAPEC-443 Malicious Logic Inserted Into Product by Authorized Developer
- CAPEC-445 Malicious Logic Insertion into Product Software via Configuration Management Manipulation
- CAPEC-446 Malicious Logic Insertion into Product via Inclusion of Third-Party Component
- CAPEC-511 Infiltration of Software Development Environment
- CAPEC-516 Hardware Component Substitution During Baselining
- CAPEC-520 Counterfeit Hardware Component Inserted During Product Assembly
- CAPEC-532 Altered Installed BIOS
- CAPEC-537 Infiltration of Hardware Development Environment
- CAPEC-538 Open-Source Library Manipulation
- CAPEC-539 ASIC With Malicious Functionality
- CAPEC-670 Software Development Tools Maliciously Altered
- CAPEC-672 Malicious Code Implanted During Chip Programming
- CAPEC-673 Developer Signing Maliciously Altered Software
- CAPEC-678 System Build Data Maliciously Altered
MITRE's words, unchanged: CAPEC-444 at MITRE. CAPEC is Copyright © 2007–2026, The MITRE Corporation, used under the CAPEC terms of use: “The MITRE Corporation (MITRE) hereby grants you a non-exclusive, royalty-free license to use Common Attack Pattern Enumeration and Classification (CAPEC™) for research, development, and commercial purposes. Any copy you make for such purposes is authorized provided that you reproduce MITRE’s copyright designation and this license in any such copy.” CAPEC and the CAPEC logo are trademarks of The MITRE Corporation. Credits. All attack patterns.