Skip to content
Threat Feed
Subscribe
critical advisory

Suspicious Activity Detection from GenAI Coding Utilities

This detection rule identifies suspicious endpoint activity, such as malicious file creation or shellcode execution, originating from or triggered by AI-assisted coding and assistant tools indicating potential supply chain or prompt injection abuse.

Modern AI-assisted development tools, including Cursor, Claude, Windsurf, Cody, Continue, and various automation bots like OpenClaw, Moltbot, and Clawdbot, have become vectors for supply-chain abuse and prompt injection attacks. Attackers leverage these utilities to execute malicious code, install rogue extensions, or run unauthorized skills that bypass traditional security controls.

Defenders must distinguish between legitimate developer workflows - such as package installs or build automation - and malicious activity. This higher-order detection logic monitors for Elastic Defend alerts (including behavioral, file, memory, or shellcode detections) where the alerted process or its direct parent is a recognized GenAI utility. By utilizing process ancestry tracking, the rule identifies descendant processes that may be performing unauthorized actions under the guise of AI-assisted development, allowing security operations teams to prioritize triage for incidents that likely involve prompt injection, malicious skills, or compromised AI supply chains.

Impact

Successful exploitation of GenAI utilities allows attackers to gain code execution in the developer environment, exfiltrate source code, harvest credentials stored within the editor, or deploy persistence mechanisms via malicious plugins or skills. These attacks threaten the integrity of software development pipelines by allowing unauthorized code to enter production environments.

Recommendation

  • Deploy the provided Elastic higher-order detection logic to identify malicious activity descending from AI-assisted coding tools.
  • Investigate high-risk alerts by reviewing process ancestry; specifically, look for entity_ids associated with GenAI parent processes.
  • Review installed extensions, skills, and recent conversation history for any GenAI tools involved in confirmed alerts to identify the source of prompt injection or malicious automation.
  • Restrict the ability of GenAI utilities to spawn shell interpreters or perform outbound network connections unless explicitly required for the development environment.

Immediate actions

Deploy the higher-order Elastic Defend rule to detect GenAI descendant process alerts.

Detection Engineering 48h

Threat Hunt

Identify all GenAI tools present in the environment via endpoint inventory.

T1195 high high confidence hunt now

Data: Process execution logs

Mitigations

Enforce code signing and extension verification policies for all development-related applications.

medium_term IT Operations

T1195.002

Detection coverage 1

Detect Suspicious Descendant Process from GenAI Utility

critical

Detects Elastic Defend alerts originating from common GenAI coding assistants or automated skill bots, suggesting supply-chain abuse or prompt injection.

sigma tactics: initial_access techniques: T1195.002 sources: process_creation

Detection queries are available on the platform. Get full rules →