{
  "attack_id": "temp-zagros-gemini-malware-dev-2025",
  "status": "catalog_recommendations_not_validated_coverage",
  "stages": [
    {
      "node_id": "step-1",
      "profile": "provider",
      "title": "Provider-side abuse investigation",
      "hypothesis": "A model-provider investigation correlates related accounts, repeated offensive requests and shared infrastructure or exposed operator sessions.",
      "visibility": "Provider / operator records",
      "telemetry": [
        "Provider-owned account / request audit",
        "Abuse-review findings and linked-account context",
        "Lawfully available exposed operator-session evidence"
      ],
      "investigate": [
        "Correlate accounts, request rates, infrastructure and source-described behavior in provider-owned records.",
        "For victim-side defense, pivot to the reported execution or access stage rather than trying to detect attacker-side prompts."
      ],
      "limitation": "Attacker-side planning is generally absent from victim SIEM logs. These templates require provider-owned audit data and do not identify AI use from a victim process alone.",
      "note": "The described development requests require provider-side records; a student-project pretext is not a reliable standalone signature.",
      "queries": {
        "sigma": "title: Hunt - Provider-side abuse investigation\nid: c8c1edc0-c79a-4644-a876-2c1a6cb9a438\nstatus: experimental\ndescription: A model-provider investigation correlates related accounts,\n  repeated offensive requests and shared infrastructure or exposed operator\n  sessions.\nauthor: MagicSword OpenAttacks catalog\ndate: 2026-10-23\nfalsepositives:\n  - Authorized activity matching this broad hunt; baseline and investigate\n    before alerting.\nlevel: low\nlogsource:\n  category: application\n  product: openattacks_audit\n  definition: Custom normalized audit schema; map EventType, Actor, Asset, Action,\n    Target and CorrelationId from the required source logs first.\ndetection:\n  selection:\n    EventType:\n      - model.request\n  condition: selection\n",
        "kql": "// SCHEMA TEMPLATE: create/map this custom table before use; not a built-in Sentinel table.\n// OpenAttacksAudit_CL: TimeGenerated(datetime), EventType/Actor/Asset/Action/Target/CorrelationId(string).\n// Selects candidates only. Apply the stage hypothesis and correlation steps before alerting.\nOpenAttacksAudit_CL\n| where TimeGenerated > ago(7d)\n| where EventType in (\"model.request\")\n| project TimeGenerated, EventType, Actor, Asset, Action, Target, CorrelationId\n| order by TimeGenerated desc",
        "spl": "sourcetype=\"openattacks:audit\"\nEventType IN (\"model.request\")\n| table _time EventType Actor Asset Action Target CorrelationId\n| sort - _time"
      },
      "query_scope": "Custom-schema candidates, not out-of-box detectors. Map your application / cloud / platform logs to EventType, Actor, Asset, Action, Target and CorrelationId. KQL uses a custom OpenAttacksAudit_CL table; SPL uses openattacks:audit. EventType values are proposed normalization names, not native vendor event names. Correlation and environment-specific alert logic remain to be built.",
      "query_kind": "custom_schema",
      "origin": "catalog_authored",
      "definition_url": "https://github.com/magicsword-io/openattacks/blob/main/detections/provider.yaml",
      "query_downloads": {
        "sigma": "/api/detections/provider.sigma.yml",
        "kql": "/api/detections/provider.kql",
        "spl": "/api/detections/provider.spl"
      },
      "validation": "draft",
      "evidence": [
        "https://cloud.google.com/blog/topics/threat-intelligence/threat-actor-usage-of-ai-tools/"
      ],
      "reviewed": "2026-11-04",
      "upstream_matches": []
    },
    {
      "node_id": "step-2",
      "profile": "provider",
      "title": "Provider-side abuse investigation",
      "hypothesis": "A model-provider investigation correlates related accounts, repeated offensive requests and shared infrastructure or exposed operator sessions.",
      "visibility": "Provider / operator records",
      "telemetry": [
        "Provider-owned account / request audit",
        "Abuse-review findings and linked-account context",
        "Lawfully available exposed operator-session evidence"
      ],
      "investigate": [
        "Correlate accounts, request rates, infrastructure and source-described behavior in provider-owned records.",
        "For victim-side defense, pivot to the reported execution or access stage rather than trying to detect attacker-side prompts."
      ],
      "limitation": "Attacker-side planning is generally absent from victim SIEM logs. These templates require provider-owned audit data and do not identify AI use from a victim process alone.",
      "queries": {
        "sigma": "title: Hunt - Provider-side abuse investigation\nid: c8c1edc0-c79a-4644-a876-2c1a6cb9a438\nstatus: experimental\ndescription: A model-provider investigation correlates related accounts,\n  repeated offensive requests and shared infrastructure or exposed operator\n  sessions.\nauthor: MagicSword OpenAttacks catalog\ndate: 2026-10-23\nfalsepositives:\n  - Authorized activity matching this broad hunt; baseline and investigate\n    before alerting.\nlevel: low\nlogsource:\n  category: application\n  product: openattacks_audit\n  definition: Custom normalized audit schema; map EventType, Actor, Asset, Action,\n    Target and CorrelationId from the required source logs first.\ndetection:\n  selection:\n    EventType:\n      - model.request\n  condition: selection\n",
        "kql": "// SCHEMA TEMPLATE: create/map this custom table before use; not a built-in Sentinel table.\n// OpenAttacksAudit_CL: TimeGenerated(datetime), EventType/Actor/Asset/Action/Target/CorrelationId(string).\n// Selects candidates only. Apply the stage hypothesis and correlation steps before alerting.\nOpenAttacksAudit_CL\n| where TimeGenerated > ago(7d)\n| where EventType in (\"model.request\")\n| project TimeGenerated, EventType, Actor, Asset, Action, Target, CorrelationId\n| order by TimeGenerated desc",
        "spl": "sourcetype=\"openattacks:audit\"\nEventType IN (\"model.request\")\n| table _time EventType Actor Asset Action Target CorrelationId\n| sort - _time"
      },
      "query_scope": "Custom-schema candidates, not out-of-box detectors. Map your application / cloud / platform logs to EventType, Actor, Asset, Action, Target and CorrelationId. KQL uses a custom OpenAttacksAudit_CL table; SPL uses openattacks:audit. EventType values are proposed normalization names, not native vendor event names. Correlation and environment-specific alert logic remain to be built.",
      "query_kind": "custom_schema",
      "origin": "catalog_authored",
      "definition_url": "https://github.com/magicsword-io/openattacks/blob/main/detections/provider.yaml",
      "query_downloads": {
        "sigma": "/api/detections/provider.sigma.yml",
        "kql": "/api/detections/provider.kql",
        "spl": "/api/detections/provider.spl"
      },
      "validation": "draft",
      "evidence": [
        "https://cloud.google.com/blog/topics/threat-intelligence/threat-actor-usage-of-ai-tools/"
      ],
      "reviewed": "2026-10-23",
      "upstream_matches": []
    },
    {
      "node_id": "step-3",
      "profile": "provider",
      "title": "Provider-side abuse investigation",
      "hypothesis": "A model-provider investigation correlates related accounts, repeated offensive requests and shared infrastructure or exposed operator sessions.",
      "visibility": "Provider / operator records",
      "telemetry": [
        "Provider-owned account / request audit",
        "Abuse-review findings and linked-account context",
        "Lawfully available exposed operator-session evidence"
      ],
      "investigate": [
        "Correlate accounts, request rates, infrastructure and source-described behavior in provider-owned records.",
        "For victim-side defense, pivot to the reported execution or access stage rather than trying to detect attacker-side prompts."
      ],
      "limitation": "Attacker-side planning is generally absent from victim SIEM logs. These templates require provider-owned audit data and do not identify AI use from a victim process alone.",
      "queries": {
        "sigma": "title: Hunt - Provider-side abuse investigation\nid: c8c1edc0-c79a-4644-a876-2c1a6cb9a438\nstatus: experimental\ndescription: A model-provider investigation correlates related accounts,\n  repeated offensive requests and shared infrastructure or exposed operator\n  sessions.\nauthor: MagicSword OpenAttacks catalog\ndate: 2026-10-23\nfalsepositives:\n  - Authorized activity matching this broad hunt; baseline and investigate\n    before alerting.\nlevel: low\nlogsource:\n  category: application\n  product: openattacks_audit\n  definition: Custom normalized audit schema; map EventType, Actor, Asset, Action,\n    Target and CorrelationId from the required source logs first.\ndetection:\n  selection:\n    EventType:\n      - model.request\n  condition: selection\n",
        "kql": "// SCHEMA TEMPLATE: create/map this custom table before use; not a built-in Sentinel table.\n// OpenAttacksAudit_CL: TimeGenerated(datetime), EventType/Actor/Asset/Action/Target/CorrelationId(string).\n// Selects candidates only. Apply the stage hypothesis and correlation steps before alerting.\nOpenAttacksAudit_CL\n| where TimeGenerated > ago(7d)\n| where EventType in (\"model.request\")\n| project TimeGenerated, EventType, Actor, Asset, Action, Target, CorrelationId\n| order by TimeGenerated desc",
        "spl": "sourcetype=\"openattacks:audit\"\nEventType IN (\"model.request\")\n| table _time EventType Actor Asset Action Target CorrelationId\n| sort - _time"
      },
      "query_scope": "Custom-schema candidates, not out-of-box detectors. Map your application / cloud / platform logs to EventType, Actor, Asset, Action, Target and CorrelationId. KQL uses a custom OpenAttacksAudit_CL table; SPL uses openattacks:audit. EventType values are proposed normalization names, not native vendor event names. Correlation and environment-specific alert logic remain to be built.",
      "query_kind": "custom_schema",
      "origin": "catalog_authored",
      "definition_url": "https://github.com/magicsword-io/openattacks/blob/main/detections/provider.yaml",
      "query_downloads": {
        "sigma": "/api/detections/provider.sigma.yml",
        "kql": "/api/detections/provider.kql",
        "spl": "/api/detections/provider.spl"
      },
      "validation": "draft",
      "evidence": [
        "https://cloud.google.com/blog/topics/threat-intelligence/threat-actor-usage-of-ai-tools/"
      ],
      "reviewed": "2026-10-23",
      "upstream_matches": []
    },
    {
      "node_id": "step-4",
      "profile": "provider",
      "title": "Provider-side abuse investigation",
      "hypothesis": "A model-provider investigation correlates related accounts, repeated offensive requests and shared infrastructure or exposed operator sessions.",
      "visibility": "Provider / operator records",
      "telemetry": [
        "Provider-owned account / request audit",
        "Abuse-review findings and linked-account context",
        "Lawfully available exposed operator-session evidence"
      ],
      "investigate": [
        "Correlate accounts, request rates, infrastructure and source-described behavior in provider-owned records.",
        "For victim-side defense, pivot to the reported execution or access stage rather than trying to detect attacker-side prompts."
      ],
      "limitation": "Attacker-side planning is generally absent from victim SIEM logs. These templates require provider-owned audit data and do not identify AI use from a victim process alone.",
      "queries": {
        "sigma": "title: Hunt - Provider-side abuse investigation\nid: c8c1edc0-c79a-4644-a876-2c1a6cb9a438\nstatus: experimental\ndescription: A model-provider investigation correlates related accounts,\n  repeated offensive requests and shared infrastructure or exposed operator\n  sessions.\nauthor: MagicSword OpenAttacks catalog\ndate: 2026-10-23\nfalsepositives:\n  - Authorized activity matching this broad hunt; baseline and investigate\n    before alerting.\nlevel: low\nlogsource:\n  category: application\n  product: openattacks_audit\n  definition: Custom normalized audit schema; map EventType, Actor, Asset, Action,\n    Target and CorrelationId from the required source logs first.\ndetection:\n  selection:\n    EventType:\n      - model.request\n  condition: selection\n",
        "kql": "// SCHEMA TEMPLATE: create/map this custom table before use; not a built-in Sentinel table.\n// OpenAttacksAudit_CL: TimeGenerated(datetime), EventType/Actor/Asset/Action/Target/CorrelationId(string).\n// Selects candidates only. Apply the stage hypothesis and correlation steps before alerting.\nOpenAttacksAudit_CL\n| where TimeGenerated > ago(7d)\n| where EventType in (\"model.request\")\n| project TimeGenerated, EventType, Actor, Asset, Action, Target, CorrelationId\n| order by TimeGenerated desc",
        "spl": "sourcetype=\"openattacks:audit\"\nEventType IN (\"model.request\")\n| table _time EventType Actor Asset Action Target CorrelationId\n| sort - _time"
      },
      "query_scope": "Custom-schema candidates, not out-of-box detectors. Map your application / cloud / platform logs to EventType, Actor, Asset, Action, Target and CorrelationId. KQL uses a custom OpenAttacksAudit_CL table; SPL uses openattacks:audit. EventType values are proposed normalization names, not native vendor event names. Correlation and environment-specific alert logic remain to be built.",
      "query_kind": "custom_schema",
      "origin": "catalog_authored",
      "definition_url": "https://github.com/magicsword-io/openattacks/blob/main/detections/provider.yaml",
      "query_downloads": {
        "sigma": "/api/detections/provider.sigma.yml",
        "kql": "/api/detections/provider.kql",
        "spl": "/api/detections/provider.spl"
      },
      "validation": "draft",
      "evidence": [
        "https://cloud.google.com/blog/topics/threat-intelligence/threat-actor-usage-of-ai-tools/"
      ],
      "reviewed": "2026-10-23",
      "upstream_matches": []
    }
  ],
  "attack_flow": {
    "nodes": [
      {
        "id": "step-1",
        "title": "Actor seeks custom malware assistance",
        "description": "Requests use student-project pretexts.",
        "kind": "access",
        "source_urls": [
          "https://cloud.google.com/blog/topics/threat-intelligence/threat-actor-usage-of-ai-tools/"
        ]
      },
      {
        "id": "step-2",
        "title": "Gemini helps develop code",
        "description": "Reported tasks include web shells and a Python C2.",
        "kind": "ai",
        "source_urls": [
          "https://cloud.google.com/blog/topics/threat-intelligence/threat-actor-usage-of-ai-tools/"
        ]
      },
      {
        "id": "step-3",
        "title": "Actor pastes operational details",
        "description": "Submitted code contains a hard-coded C2 domain and encryption key.",
        "kind": "execution",
        "source_urls": [
          "https://cloud.google.com/blog/topics/threat-intelligence/threat-actor-usage-of-ai-tools/"
        ]
      },
      {
        "id": "step-4",
        "title": "Operational exposure aids disruption",
        "description": "The research describes an OPSEC failure, rather than disclosing a complete downstream victim chain.",
        "kind": "impact",
        "source_urls": [
          "https://cloud.google.com/blog/topics/threat-intelligence/threat-actor-usage-of-ai-tools/"
        ]
      }
    ],
    "edges": [
      {
        "source": "step-1",
        "target": "step-2"
      },
      {
        "source": "step-2",
        "target": "step-3"
      },
      {
        "source": "step-3",
        "target": "step-4"
      }
    ]
  }
}