CuraSec

tag: Ai-Assistant · 2 items

2026-09-22 · The Hacker News · source ↗ #ai-assistant#macos#post-exploitation
  • Engineer — Learn: The attack requires malware already present on the host, making this a post-exploitation primitive rather than an initial-access flaw. No patch details are provided yet; review AI assistant permission grants on macOS endpoints and consider restricting Muse accessibility access where it isn’t needed.
  • SOC/IR — Plan: Wardle’s PoC establishes a concrete post-compromise technique where an attacker redirects Muse microphone input by flipping a hidden setting; build a detection or hunt for unexpected modifications to Muse configuration files on managed Macs.
  • Leader — Learn: This illustrates how broad OS permissions granted to AI assistants can become an attacker tool after initial compromise — useful background for refining enterprise AI-assistant usage policies, but not an immediate action item without active exploitation evidence.
2026-07-10 · The Hacker News · source ↗ #vulnerability#ai-assistant#rce
  • Engineer — Plan: If OpenClaw is deployed in your environment, verify you are running a patched version addressing all three CVEs (GHSA-hjr6-g723-hmfm and siblings); no public PoC or KEV listing present, so patch within normal cycle but prioritize given CVSS 8.8 and the RCE/privilege-escalation chain.
  • SOC/IR — Learn: No published IOCs or active exploitation reported; the attack chain description (WhatsApp input → credential theft → privilege escalation → host RCE) is worth understanding to recognize behavioral indicators if OpenClaw is in scope, but no detection work is actionable today.
  • Leader — Skip