Infringement
Account Sharing
Codebase Integrity Compromise
Data Loss
Delegated Execution via Artificial Intelligence Agents
Denial of Service
Disruption of Business Operations
Excessive Personal Use
Exfiltration via Email
Exfiltration via Media Capture
Exfiltration via Messaging Applications
Exfiltration via Other Network Medium
Exfiltration via Physical Medium
- Exfiltration via Bring Your Own Device (BYOD)
- Exfiltration via Disk Media
- Exfiltration via Floppy Disk
- Exfiltration via New Internal Drive
- Exfiltration via Physical Access to System Drive
- Exfiltration via Physical Documents
- Exfiltration via Target Disk Mode
- Exfiltration via USB Mass Storage Device
- Exfiltration via USB to Mobile Device
- Exfiltration via USB to USB Data Transfer
Exfiltration via Screen Sharing
Exfiltration via SMS/MMS
Exfiltration via Web Service
Harassment and Discrimination
Inappropriate Web Browsing
Installing Malicious Software
Installing Unapproved Software
Misappropriation of Funds
Non-Corporate Device
Providing Access to a Unauthorized Third Party
Public Statements Resulting in Brand Damage
Regulatory Non-Compliance
Sharing on AI Chatbot Platforms
Theft
Unauthorized Changes to IT Systems
Unauthorized Printing of Documents
Unauthorized VPN Client
Unlawfully Accessing Copyrighted Material
- ID: IF029.001
- Created: 21st March 2026
- Updated: 29th March 2026
- Contributor: The ITM Team
Malicious or Harmful Code Contribution
A subject introduces code into an organizational repository that is designed to cause harm, enable unauthorized access, degrade system integrity, or facilitate future exploitation. This includes the deliberate insertion of backdoors, data exfiltration mechanisms, logic bombs, or code that weakens existing security controls.
The activity occurs through legitimate development workflows such as commits, pull requests, or merges, often making it indistinguishable from normal development at the point of submission. The harmful nature of the code may be concealed within complex logic, triggered under specific conditions, or embedded within otherwise functional changes.
This behavior represents a direct violation of trust, where the subject leverages authorized access to introduce persistent or latent risk into systems. Impact may not be immediately visible and can manifest post-deployment, during specific runtime conditions, or when triggered intentionally.