Back to Intelligence

CISA Nominee, Connected Car Exploits, and AI Model Risks: 2026 Threat Landscape Analysis

SA
Security Arsenal Team
November 14, 2026
9 min read

The threat landscape is fracturing into specialized, high-impact domains. While CISA undergoes leadership transition, nation-state actors are probing AI infrastructure—specifically OpenAI Codex and Microsoft model weights—for unauthorized access mechanisms that bypass traditional authentication. Simultaneously, the Baker Tilly data breach exposes the fragility of supply-chain trust, and connected car hacking has evolved from theoretical research to active exploitation of vehicular control systems.

This isn't a collection of isolated incidents. These stories represent a convergence: adversaries are targeting the software supply chain, AI development pipelines, and critical operational technology simultaneously. For SOC analysts and IR responders, this means the detection surface has expanded beyond traditional network perimeters into model repositories, automotive ECUs, and third-party vendor environments.

Technical Analysis

AI Infrastructure Under Siege

The warnings regarding OpenAI Codex and Microsoft model weight unauthorized access mechanisms signal a shift in adversary tradecraft. These aren't traditional network intrusions; they're supply-chain attacks targeting the AI development lifecycle.

Attack Vectors:

  • Codex Unauthorized Access: Attackers are exploiting misconfigured API permissions and overly permissive service accounts in CI/CD pipelines to inject malicious code suggestions or exfiltrate training data. The mechanism likely involves token theft or OAuth flow manipulation in developer environments.
  • Model Weight Exfiltration: Microsoft has identified risks where model weights—the trained parameters of large language models—are being targeted for theft. This isn't about stealing code; it's about stealing intellectual property and creating backdoored model variants for downstream attacks.

Exploitation Status: These are active campaigns, not theoretical vulnerabilities. Nation-state actors and sophisticated criminal groups are systematically scanning for exposed AI infrastructure, misconfigured model repositories, and developer endpoints with cached credentials.

Connected Car Hacking: From POC to Weaponization

Connected vehicle platforms have become a critical attack surface. Modern vehicles contain 100+ ECUs (Electronic Control Units) communicating over CAN bus, Ethernet, and wireless protocols. The current threat involves:

  • Remote Exploitation: Cellular and WiFi attack vectors allowing remote code execution on telematics control units
  • CAN Bus Injection: Malicious frames injected into the vehicle network to control brakes, steering, and acceleration
  • Supply-Chain Compromise: Third-party telematics providers and OTA (over-the-air) update mechanisms being weaponized

Affected Systems: Vehicles with always-on cellular connectivity, remote start capabilities, and integrated infotainment systems are highest risk. The attack surface includes the TCU (Telematics Control Unit), head unit, and gateway ECUs.

Baker Tilly Supply-Chain Breach

The Baker Tilly data breach represents a classic third-party risk scenario. Attackers compromised the accounting and advisory firm to access client data, demonstrating how professional services firms have become high-value targets for lateral movement into enterprise networks.

Impact: Client financial data, tax documents, and audit materials exposed. This creates a secondary risk—attackers using stolen audit findings to map client networks before launching targeted intrusions.

Detection & Response

Sigma Rules

YAML
---
title: OpenAI Codex API Unauthorized Access Attempt
id: 550d9a23-0f72-4e3a-a8c5-1d2f3b4c5d6e
status: experimental
description: Detects suspicious API calls to OpenAI Codex endpoints indicative of credential theft or token abuse.
references:
  - https://attack.mitre.org/techniques/T1552/
author: Security Arsenal
date: 2026/04/06
tags:
  - attack.credential_access
  - attack.t1552.001
logsource:
  category: proxy
  product: web
detection:
  selection:
    cs-host|contains:
      - 'api.openai.com'
    cs-uri|contains:
      - '/v1/engines'
      - '/v1/completions'
    cs-method: 'POST'
  condition: selection
falsepositives:
  - Legitimate development activity
level: medium
---
title: Microsoft Model Weight Repository Access
id: 7a3f1c82-9e4b-4d67-bc12-3e5a8f901234
status: experimental
description: Detects unauthorized access attempts to model weight storage or repositories.
references:
  - https://attack.mitre.org/techniques/T1530/
author: Security Arsenal
date: 2026/04/06
tags:
  - attack.collection
  - attack.t1530
logsource:
  category: file_event
  product: windows
detection:
  selection:
    TargetFilename|contains:
      - 'model.bin'
      - 'pytorch_model.bin'
      - 'tf_model.h5'
      - 'weights.pt'
    EventType: 'FileAccess'
  condition: selection
falsepositives:
  - Legitimate ML development
level: high
---
title: CAN Bus Injection via Diagnostic Port
id: 8b2f3c94-1a5d-4e78-9c23-4f6a7b8c9d0e
status: experimental
description: Detects suspicious diagnostic tool connections to vehicle networks.
references:
  - https://attack.mitre.org/techniques/T1547/
author: Security Arsenal
date: 2026/04/06
tags:
  - attack.persistence
  - attack.t1547
logsource:
  category: network_connection
  product: automotive
detection:
  selection:
    DestinationPort: 15765
    Protocol: 'ISO-TP'
  condition: selection
falsepositives:
  - Legitimate dealership diagnostics
level: medium

KQL (Microsoft Sentinel / Defender)

KQL — Microsoft Sentinel / Defender
// Hunt for suspicious API access to AI services
DeviceNetworkEvents
| where TimeGenerated > ago(7d)
| where RemoteUrl contains "api.openai.com" or RemoteUrl contains "azure.microsoft.com"
| where InitiatingProcessName in ("powershell.exe", "cmd.exe", "python.exe", "curl.exe")
| project TimeGenerated, DeviceName, InitiatingProcessName, RemoteUrl, RemotePort, InitiatingProcessCommandLine
| order by TimeGenerated desc

// Hunt for model file access
DeviceFileEvents
| where TimeGenerated > ago(7d)
| where FileName contains "model.bin" or FileName contains "weights.pt" or FileName contains "pytorch_model.bin"
| where FolderPath contains "AppData" or FolderPath contains "Temp" or FolderPath contains "Downloads"
| project TimeGenerated, DeviceName, FileName, FolderPath, InitiatingProcessName, SHA256
| order by TimeGenerated desc

// Hunt for automotive diagnostic tool connections (via network telemetry)
DeviceNetworkEvents
| where TimeGenerated > ago(7d)
| where RemotePort == 15765 or RemotePort == 13400
| where InitiatingProcessName notin ("svchost.exe", "System")
| project TimeGenerated, DeviceName, InitiatingProcessName, RemoteIP, RemotePort
| order by TimeGenerated desc

Velociraptor VQL

VQL — Velociraptor
-- Hunt for AI development tools accessing suspicious network endpoints
SELECT Pid, Name, CommandLine, Exe, Username, CreateTime, netstat() AS NetConnections
FROM pslist()
WHERE Name =~ '(python|powershell|cmd|curl)'
   AND CommandLine =~ 'openai|azure|api.openai.com'
   AND NetConnections.RemotePort =~ '443'

-- Hunt for model files in suspicious locations
SELECT FullPath, Size, Mtime, Ctime
FROM glob(globs='C:\\Users\\**\\AppData\\**\\model.bin')
WHERE Size > 1000000000

-- Hunt for automotive diagnostic tools
SELECT Pid, Name, CommandLine, Exe, Username
FROM pslist()
WHERE Name =~ '(canalyzer|canoe|vehicle|obd|uds|iso)'
   OR CommandLine =~ '15765|13400'

Remediation Script (PowerShell)

PowerShell
# AI Infrastructure Hardening Script
# Run on developer workstations and CI/CD servers

Write-Host "=== AI Infrastructure Security Hardening ===" -ForegroundColor Cyan

# 1. Audit OpenAI API keys and rotate if found in environment variables
Write-Host "[+] Checking for exposed OpenAI API keys..." -ForegroundColor Yellow
$envVars = Get-ChildItem Env: | Where-Object { $_.Value -match 'sk-[a-zA-Z0-9]{48}' }
if ($envVars) {
    Write-Host "[!] WARNING: OpenAI API keys detected in environment variables!" -ForegroundColor Red
    $envVars | ForEach-Object { Write-Host "  - $($_.Name)" -ForegroundColor Red }
    Write-Host "[!] ACTION REQUIRED: Rotate keys immediately and use Azure Key Vault or similar" -ForegroundColor Red
} else {
    Write-Host "[✓] No exposed API keys found in environment variables" -ForegroundColor Green
}

# 2. Audit local model repositories for unauthorized access
Write-Host "[+] Scanning for model weight files..." -ForegroundColor Yellow
$modelPaths = @(
    "$env:USERPROFILE\.cache\huggingface",
    "$env:USERPROFILE\.cache\torch",
    "C:\ProgramData\Microsoft\Azure\Models",
    "$env:USERPROFILE\AppData\Local\OpenAI"
)

foreach ($path in $modelPaths) {
    if (Test-Path $path) {
        $acl = Get-Acl $path
        $accessRules = $acl.Access | Where-Object { $_.IdentityReference -match 'Everyone|BUILTIN\Users' -and $_.FileSystemRights -match 'FullControl|Write' }
        if ($accessRules) {
            Write-Host "[!] WARNING: Overly permissive ACL on $path" -ForegroundColor Red
            $accessRules | ForEach-Object { Write-Host "  - $($_.IdentityReference): $($_.FileSystemRights)" -ForegroundColor Red }
            Write-Host "[!] ACTION: Restrict permissions to service accounts only" -ForegroundColor Red
        }
    }
}

# 3. Block suspicious outbound connections to AI APIs from non-dev processes
Write-Host "[+] Configuring Windows Firewall to restrict AI API access..." -ForegroundColor Yellow
$ruleName = "Block AI API from System Processes"
$existingRule = Get-NetFirewallRule -DisplayName $ruleName -ErrorAction SilentlyContinue

if (-not $existingRule) {
    New-NetFirewallRule -DisplayName $ruleName `n        -Direction Outbound `
        -RemoteAddress "api.openai.com","*.azure.com" `
        -Protocol TCP `
        -LocalPort 443 `
        -Action Block `
        -Program "C:\Windows\System32\svchost.exe","C:\Windows\System32\lsass.exe","C:\Windows\System32\csrss.exe" `
        -ErrorAction SilentlyContinue | Out-Null
    Write-Host "[✓] Firewall rule created: $ruleName" -ForegroundColor Green
} else {
    Write-Host "[✓] Firewall rule already exists" -ForegroundColor Green
}

# 4. Enable detailed logging for AI service access
Write-Host "[+] Enabling audit policy for API access..." -ForegroundColor Yellow
AuditPol /set /subcategory:"Filtering Platform Connection" /success:enable /failure:enable | Out-Null
AuditPol /set /subcategory:"Process Creation" /success:enable /failure:enable | Out-Null

# 5. Check for suspicious network connections to AI endpoints
Write-Host "[+] Checking active connections to AI services..." -ForegroundColor Yellow
$connections = Get-NetTCPConnection | Where-Object { 
    $_.RemoteAddress -match '13.107.246.|20.190.151.|40.126.32.' -and 
    $_.State -eq 'Established' -and 
    $_.OwningProcess -in (Get-Process | Where-Object { $_.Name -match 'svchost|lsass|csrss' }).Id
}

if ($connections) {
    Write-Host "[!] WARNING: Suspicious connections detected from system processes to AI endpoints!" -ForegroundColor Red
    $connections | ForEach-Object { 
        $proc = Get-Process -Id $_.OwningProcess -ErrorAction SilentlyContinue
        Write-Host "  - PID: $($_.OwningProcess) ($($proc.Name)) -> $($_.RemoteAddress):$($_.RemotePort)" -ForegroundColor Red
    }
    Write-Host "[!] ACTION: Investigate these processes immediately" -ForegroundColor Red
} else {
    Write-Host "[✓] No suspicious connections detected" -ForegroundColor Green
}

Write-Host "=== Hardening Complete ===" -ForegroundColor Cyan
Write-Host "Next Steps: Review logs in Event Viewer > Windows Logs > Security for Event ID 5156 (network connections)" -ForegroundColor Yellow

Remediation

AI Infrastructure Protection

  1. Credential Hygiene: Rotate all API keys for OpenAI, Azure, and other AI services immediately. Store keys in Azure Key Vault, HashiCorp Vault, or AWS Secrets Manager—never in environment variables or code repositories.

  2. Model Repository Hardening:

    • Implement RBAC (Role-Based Access Control) on all model storage
    • Enable encryption at rest for model weights
    • Deploy DLP (Data Loss Prevention) rules to detect model exfiltration
  3. Network Segmentation: Isolate AI development environments from production networks. Use dedicated VLANs and firewall rules to restrict API access to authorized service accounts only.

  4. Monitoring: Deploy the Sigma rules and KQL queries above to your SIEM. Alert on any API access from non-development processes or unexpected geographic locations.

Connected Vehicle Security

  1. TCU Hardening: Work with automotive vendors to ensure telematics control units are running the latest firmware. Many TCUs ship with default credentials or unpatched vulnerabilities.

  2. CAN Bus Monitoring: Deploy CAN bus intrusion detection systems (IDS) that can detect malicious frame injection. Solutions like Argus, Upstream, or Karamba can provide visibility.

  3. OTA Update Verification: Ensure over-the-air update mechanisms use code signing and secure boot. Validate update packages before installation.

  4. Diagnostic Port Security: Implement physical security controls for OBD-II ports. Consider disabling diagnostic ports when not in use or using authenticated access mechanisms.

Supply-Chain Risk Mitigation

  1. Third-Party Audits: Conduct security assessments of all vendors with access to sensitive data. Require SOC 2 Type II, ISO 27001, or equivalent certifications.

  2. Data Minimization: Limit the data shared with third parties to the minimum necessary. Use tokenization or anonymization where possible.

  3. Incident Response Planning: Include third-party breaches in your IR playbooks. Define communication protocols and legal obligations for supply-chain incidents.

  4. Contractual Protections: Ensure vendor contracts include security requirements, breach notification timelines, and liability clauses.

Related Resources

Security Arsenal Managed SOC Services AlertMonitor Platform Book a SOC Assessment soc-mdr Intel Hub

Is your security operations ready?

Get a free SOC assessment or see how AlertMonitor cuts through alert noise with automated triage.