-
Unusual Process Modifying GenAI Configuration File
Oct 7, 2026 · Domain: Endpoint OS: macOS OS: Windows Use Case: Threat Detection Tactic: Defense Evasion Tactic: Persistence Data Source: Elastic Defend Resources: Investigation Guide Noise: Medium Performance: Normal Profile: Recommended Threat: Unauthorized AI Usage Rule Type: New Terms Platform: Windows Platform: macOS Domain: GenAI Mitre Atlas: AML.T0081 ·Detects unusual modification of GenAI tool configuration files. Adversaries may inject malicious MCP server configurations to hijack AI agents for persistence, C2, or data exfiltration. Attack vectors include malware or scripts directly poisoning config files, supply chain attacks via compromised dependencies, and prompt injection attacks that abuse the GenAI tool itself to modify its own configuration. Unauthorized MCP servers added to these configs execute arbitrary commands when the AI tool is next invoked.
Read More -
Detects the first successful creation of a Model Context Protocol (MCP) server integration name in an Anthropic organization within the rule history window. MCP servers add external data pathways into Claude and can expose organizational data to third-party infrastructure. This is a New Terms rule keyed on
organization.idandanthropic.audit.mcp_server_nameso the same connector name can still alert in another tenant, while routine re-creation of an already-seen name in the same organization does not.
Read More -
AWS Bedrock Agent Created by IAM User or Root
Oct 1, 2026 · Domain: Cloud Domain: GenAI Data Source: AWS Data Source: AWS CloudTrail Data Source: Amazon Web Services Data Source: AWS Bedrock Data Source: Amazon Bedrock Use Case: Threat Detection Tactic: Persistence Resources: Investigation Guide Noise: Unknown Performance: Fast Threat: Unauthorized AI Usage Rule Type: Custom Query (KQL) Platform: AWS Service: AWS Bedrock Service: AWS IAM Mitre Atlas: AML.T0081 Mitre Atlas: AML.T0103 ·Identifies AWS Bedrock Agent creation performed directly by an IAM user or the root account. Bedrock Agents are autonomous AI systems that execute multi-step tasks, invoke Lambda action groups to call external APIs, and query knowledge bases. Adversaries with access to an AWS account can create rogue agents configured to exfiltrate data via action group Lambda functions, pivot to other services, or act as a persistent AI-driven command-and-control channel. This rule is scoped to IAMUser and Root identity types — AssumedRole sessions (which represent automated CI/CD pipelines and SSO-federated engineers) are excluded to avoid global false positives from legitimate deployment automation that varies widely across customer environments.
Read More -
AWS Bedrock Agent or Action Group Manipulation
Oct 1, 2026 · Domain: Cloud Domain: GenAI Data Source: AWS Data Source: AWS CloudTrail Data Source: Amazon Web Services Data Source: AWS Bedrock Data Source: Amazon Bedrock Use Case: Threat Detection Resources: Investigation Guide Tactic: Persistence Noise: Unknown Performance: Fast Profile: Recommended Threat: Unauthorized AI Usage Rule Type: New Terms Platform: AWS Service: AWS Bedrock Mitre Atlas: AML.T0081 Mitre Atlas: AML.T0053 ·Detects modification of deployed Amazon Bedrock agents and their action groups, collaborators, or aliases via the Bedrock Agent control plane. Adversaries with access to an AWS account can tamper with an existing, trusted agent by altering its instructions (UpdateAgent), adding or changing action groups that wire the agent to Lambda functions or APIs (CreateAgentActionGroup, UpdateAgentActionGroup), attaching or modifying collaborators (AssociateAgentCollaborator, UpdateAgentCollaborator), or repointing an alias to a tampered version (CreateAgentAlias, UpdateAgentAlias). A PrepareAgent call is required to make a tampered configuration live. By implanting malicious behavior into an agent that legitimate users continue to invoke, an attacker can maintain durable access through a trusted component. Creation of brand-new agents (CreateAgent) is intentionally excluded as lower-signal activity.
Read More -
GenAI CLI Started with Unsafe Permission Bypass
Oct 1, 2026 · Domain: Endpoint OS: Linux OS: macOS OS: Windows Use Case: Threat Detection Tactic: Defense Evasion Data Source: Elastic Defend Resources: Investigation Guide Noise: High Performance: Normal Profile: Aggressive Threat: Unauthorized AI Usage Rule Type: Event Correlation (EQL) Platform: Windows Platform: Linux Platform: macOS Domain: GenAI Mitre Atlas: AML.T0081 Mitre Atlas: AML.T0053 ·Identifies GenAI agent CLIs started with permission-bypass or auto-approval flags that disable human-in-the-loop guardrails. These modes are intended for isolated sandboxes but are frequently misused on internet-connected developer workstations, allowing prompt injection, compromised dependencies, or malicious skills to execute commands, modify files, or reach sensitive paths without confirmation.
Read More